If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 21/Jul/17 01:34 PM
Updated: 20/Jan/18 12:54 AM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Dear all,
I noticed this in the "Shelved changes" variable : " If not specified, all shelved changes of above user will be merged. Note that you may specify other user's shelved changes here,"
It's a behavior we would like to skip in certain cases.
What we do is keep a pool of computers we update on a regular basis when no developper are requestion a test build to validate their modifications.
So far it works great I just use the same repository to sync whith no shelved passed... but lately I just realised some changelist were unshelved (juste because the build machine account add some shelved files).
Could we have an option to bypass this behavior ? so we can just sync without getting any shelve files ?
Thanks a lot !
Ben
|
Description
|
Dear all,
I noticed this in the "Shelved changes" variable : " If not specified, all shelved changes of above user will be merged. Note that you may specify other user's shelved changes here,"
It's a behavior we would like to skip in certain cases.
What we do is keep a pool of computers we update on a regular basis when no developper are requestion a test build to validate their modifications.
So far it works great I just use the same repository to sync whith no shelved passed... but lately I just realised some changelist were unshelved (juste because the build machine account add some shelved files).
Could we have an option to bypass this behavior ? so we can just sync without getting any shelve files ?
Thanks a lot !
Ben |
Show » |
|