-
Suggestion
-
Resolution: Fixed
-
None
-
None
We use dependencies as a work-around for not having multiple build triggers.
(1)
In this case there is no need for a "builder" script. Since Bamboo requires one, we run a bogus shell command like 'echo'. That is a minor problem but it's an annoyance. If Bamboo will not support multiple build triggers, we need the builder to be optional.
(2)
There is no need to pull source. Bamboo requires source repository info to be provided. So we pull in a small part of our subversion repo for no reason other than to make Bamboo happy.
There should be separate tabs for "Source Repository" and "Triggers." I understand they are related, but triggers should not require a source repository depending on the type of trigger desired.
- is related to
-
BAM-9310 Allow stages an tasks to have their own 'Build Strategy' (trigger to run the goal)
- Closed
[BAM-8031] Changes needed for workaround for lack of multiple triggers
Workflow | Original: JAC Suggestion Workflow [ 3018957 ] | New: JAC Suggestion Workflow 3 [ 3598472 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2699047 ] | New: JAC Suggestion Workflow [ 3018957 ] |
Backlog Order (Obsolete) | Original: 10830000000 | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1408676 ] | New: Confluence Workflow - Public Facing v4 [ 2699047 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 609347 ] | New: Bamboo Workflow 2016 v1 [ 1408676 ] |
Workflow | Original: Bamboo Workflow 2014 [ 601333 ] | New: Bamboo Workflow 2014 v2 [ 609347 ] |
Workflow | Original: Bamboo Workflow 2010 [ 278688 ] | New: Bamboo Workflow 2014 [ 601333 ] |
Fix Version/s | New: 4.3 [ 26590 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Multiple Build Triggers feature is part of upcoming 4.3 release.