-
Suggestion
-
Resolution: Fixed
-
None
This solves part of BAM-560, I think.
We need dependencies of our libraries to be ordered so the acceptance tests for the library are run before triggering the actual product builds. See AtlassianUser build on keg for example. Triggering the products off the acceptance tests doesn't usually make sense. You also want to manage project dependencies in one place.
- is related to
-
BAM-560 Dependencies should handle more complex cases
- Closed
[BAM-781] Support ordering of build dependencies
Workflow | Original: JAC Suggestion Workflow [ 3016268 ] | New: JAC Suggestion Workflow 3 [ 3595912 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2703262 ] | New: JAC Suggestion Workflow [ 3016268 ] |
Backlog Order (Obsolete) | Original: 1420000000 | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1415751 ] | New: Confluence Workflow - Public Facing v4 [ 2703262 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 618830 ] | New: Bamboo Workflow 2016 v1 [ 1415751 ] |
Workflow | Original: Bamboo Workflow 2014 [ 605020 ] | New: Bamboo Workflow 2014 v2 [ 618830 ] |
Workflow | Original: Bamboo Workflow 2010 [ 202685 ] | New: Bamboo Workflow 2014 [ 605020 ] |
Workflow | Original: reviewflow [ 196883 ] | New: Bamboo Workflow 2010 [ 202685 ] |
Workflow | Original: Feature Request Workflow [ 168681 ] | New: reviewflow [ 196883 ] |
Component/s | New: Infrastructure [ 11240 ] | |
Component/s | Original: Internal Tasks [ 11811 ] |