-
Suggestion
-
Resolution: Timed out
-
None
-
0
-
We have this:
- BuildA is triggered on the repository.
- BuildA triggers BuildB on success.
- BuildA time << BuildB time.
BuildA triggers BuildB. BuildA runs again before BuildB passes. BuildB will not be run again after it completes meaning it will not see the changes that triggered BuildA the second time.
It would be nice if bamboo kept a note that BuildA completed while BuildB was running and run BuildB again after it finishes.
Maybe this could be a property on the dependency between BuildA and BuildB. In JIRA we would not need the repository version to be kept, we just want the build to kick off again (though keeping the repository version would be nice).
[BAM-4320] Build trigger forgotten when dependent build currently running.
Resolution | New: Timed out [ 10 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | New: bamboo-bugs-grooming |
Workflow | Original: JAC Suggestion Workflow [ 3017213 ] | New: JAC Suggestion Workflow 3 [ 3596854 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2698360 ] | New: JAC Suggestion Workflow [ 3017213 ] |
UIS | New: 0 |
Backlog Order (Obsolete) | Original: 9860000000 | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Not Being Considered [ 11776 ] | New: Gathering Interest [ 11772 ] |
Status | Original: Gathering Interest [ 11772 ] | New: Not Being Considered [ 11776 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1408050 ] | New: Confluence Workflow - Public Facing v4 [ 2698360 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 607926 ] | New: Bamboo Workflow 2016 v1 [ 1408050 ] |