Key: |
QB-650
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Won't Fix
|
Priority: |
Major
|
Assignee: |
Robin Shen
|
Reporter: |
Roger Perkins
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 28/Sep/10 09:57 AM
Updated: 28/Sep/10 12:49 PM
|
|
Component/s: |
None
|
Affects Version/s: |
3.0.7
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
We have assets that are checked back into our perforce repository as a result of some builds. All the commits are by the same "automated" user account and it would be ideal to be able to filter out commits made by this user so they don't trigger needless CI when the build machine next checks for changes. Right now I can only easily check for changes to excluse based on file path (which could get overly complex for this scenario).
For the occasions where you might want slight variations on the default options provided, it would also be really nice to have some way to see what the equivelant script for the default options would be so that it could be copied and modified into a custom script by the user.
|
Description
|
We have assets that are checked back into our perforce repository as a result of some builds. All the commits are by the same "automated" user account and it would be ideal to be able to filter out commits made by this user so they don't trigger needless CI when the build machine next checks for changes. Right now I can only easily check for changes to excluse based on file path (which could get overly complex for this scenario).
For the occasions where you might want slight variations on the default options provided, it would also be really nice to have some way to see what the equivelant script for the default options would be so that it could be copied and modified into a custom script by the user. |
Show » |
No work has yet been logged on this issue.
|
|