I would like to have the build script behave differently if the build was scheduled vs triggered by a checkin vs triggered by another build. The most pressing need for me is to run more tests on the scheduled build.
[BAM-13030] provide trigger reason in a bamboo property
| Resolution | New: Done [ 17 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Fix Version/s | New: 9.3.0 [ 104112 ] |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Status | Original: Gathering Interest [ 11772 ] | New: In Progress [ 3 ] |
| Assignee | New: Mateusz Szmal [ 851f15845f55 ] |
| Remote Link |
New:
This issue links to "+core+ Dogfooding › Test Git Branch Detection › feature- |
Our use case is the same as other comments, with the plan behaving differently depending on the trigger reason for a build.
ie If the build was bitbucker server commit or a scheduled build triggered
The plan variable bamboo.ManualBuildTriggerReason.userName already exists.
If a trigger type variable was made available, scripts could then be written to handle the various trigger types scenarios
eg
bamboo.BuildTrigger.type= Scheduled
bamboo.BuildTrigger.type=BitbuckerServerRepository
etc
| UIS | Original: 1 | New: 0 |
Differentiating builds was exactly why I developed this: However, I am not using Bamboo at the moment - And not actively maintaining this project either (I did the plugin on my own time, when I worked in consultancy... ).
The code, however, is really not that complex, so should be easy to customize for any needs 
Hello,
As a part of the 9.3 release, there will be a variable added (`bamboo.triggerReason.key`) that will be present in both the plan and deployment contexts (so it will be also accessible as a Task condition).
This variable will point out the key of the trigger reason e.g. `com.atlassian.bamboo.plugin.system.triggerReason:ManualBuildTriggerReason`.
Bamboo Development Team