[#CIB-1457] 57563: Submitting a personal build should not force a sync of user's client

Pulse

57563: Submitting a personal build should not force a sync of user's client

Created: 01/May/08 08:58 AM Updated: 25/Jun/09 12:44 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

2.1.4

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Description

« Hide

Currently, 'pulse personal' does a 'p4 sync' before submitting the build. The user may not want to or be able to sync his client to top-of-trunk (due to bugs at top-of-trunk).

Currently, the only workaround is to create a duplicate clientspec on the user's machine which covers only the files which are to be patched, and then run pulse personal from there.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Daniel Ostermeier - 01/May/08 10:19 AM

Quote from email:
My 2 minute analysis of this is that I can't think of any blocker. It should be possible as a new flag to the pulse personal command (also configurable via the config file).

[ Permlink | « Hide ]

jason - 05/Dec/08 05:36 PM

This is annoying, you should at least be able to tell Pulse you know what you are doing instead of having an enforced sync making it high priority.

[ Permlink | « Hide ]

TQ Berg - 16/Feb/09 02:03 PM

It would be nice if you could specify the client root in the config file -- which would be used when creating the duplicate clientspec.

[ Permlink | « Hide ]

jason - 17/Feb/09 09:22 AM

Hi TQ,

The true solution to this problem will not involve a duplicate client spec. If we stop Pulse from always syncing, the duplicate isn't required to maintain the state of your original client.

[ Permlink | « Hide ]

jason - 25/Jun/09 12:44 PM

Implemented in change 6066. Now the personal build client asks you if you would like to build against:

- the latest revision at the time of the request
- your working revision (actually a best guess)
- a floating revision (latest when the build starts)
- the last known good revision (from the latest successful build at request time)
- a custom revision (entered by the user)

After choosing the revision, where it makes sense you are also asked if you would like to update to the revision first before creating a patch file. Both the revision choice and the decision to update or not can also be specified on the command line, or in your config.