-
Suggestion
-
Resolution: Fixed
-
None
-
None
One strategy could be to always pull one revision at a time.
Another strategy could be to pull one revision at a time but only up to some threshold (i.e. - if you are within 3 revisions of current). Beyond that threshold, maybe a 'catch-up' (pull current) makes sense.
Another strategy could be to pull up to x changesets/revisions at a time (to put a hard limit on the number of changesets integrated in each build).
What is considered excessive might be flexible depending on server resources available to you and the time it takes your projects to build.
N.B. This issue was first discussed in the forums http://forums.atlassian.com/thread.jspa?messageID=257246130
[BAM-1126] Bamboo should bulid each revision till the latest revision when performing builds, so that user can figure out which commit broke the build
Workflow | Original: JAC Suggestion Workflow [ 3015949 ] | New: JAC Suggestion Workflow 3 [ 3602160 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2702525 ] | New: JAC Suggestion Workflow [ 3015949 ] |
Backlog Order (Obsolete) | Original: 29220000000 | |
Assignee | Original: MarkC [ mark@atlassian.com ] | |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1408928 ] | New: Confluence Workflow - Public Facing v4 [ 2702525 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 609856 ] | New: Bamboo Workflow 2016 v1 [ 1408928 ] |
Workflow | Original: Bamboo Workflow 2014 [ 604303 ] | New: Bamboo Workflow 2014 v2 [ 609856 ] |
Workflow | Original: Bamboo Workflow 2010 [ 202842 ] | New: Bamboo Workflow 2014 [ 604303 ] |
Assignee | New: MarkC [ mark@atlassian.com ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: reviewflow [ 196928 ] | New: Bamboo Workflow 2010 [ 202842 ] |
Workflow | Original: Feature Request Workflow [ 168725 ] | New: reviewflow [ 196928 ] |