It would be very useful if a build stored the SCM build identifier (i.e. SVN revision, CVS date, P4 revision) that a given build was checked out with.
This could then be used by
- anyone wishing to recreate a given build
- an integration server to build and deploy the software when the build succeed (our environment is complex, and the servers doing CI are not in the same location as the integration servers which live in our datacentre). While we could cobble together
This is related to my commentary on BAM-61; although reading that is not mandatory to understand my request.
[BAM-604] API access to the SCM repository's build identifier for a given build
Workflow | Original: JAC Suggestion Workflow [ 3018534 ] | New: JAC Suggestion Workflow 3 [ 3598064 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2698158 ] | New: JAC Suggestion Workflow [ 3018534 ] |
Assignee | Original: edwin [ edwin@atlassian.com ] | |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1407231 ] | New: Confluence Workflow - Public Facing v4 [ 2698158 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 607710 ] | New: Bamboo Workflow 2016 v1 [ 1407231 ] |
Workflow | Original: Bamboo Workflow 2014 [ 596285 ] | New: Bamboo Workflow 2014 v2 [ 607710 ] |
Workflow | Original: Bamboo Workflow 2010 [ 204076 ] | New: Bamboo Workflow 2014 [ 596285 ] |
Workflow | Original: reviewflow [ 197313 ] | New: Bamboo Workflow 2010 [ 204076 ] |
Workflow | Original: Feature Request Workflow [ 168480 ] | New: reviewflow [ 197313 ] |
Workflow | Original: reviewflow [ 164561 ] | New: Feature Request Workflow [ 168480 ] |