reason
Glossary
- activity log
- agent
- agent-specific capability
- artifact
- authors in Bamboo
- build
- build activity
- build duration
- build log
- build queue
- build result
- build telemetry
- capability
- child
- committer
- custom capability
- default repository
- elastic agent
- elastic Bamboo
- elastic block store
- elastic image
- elastic instance
- executable
- favorites
- global permission
- job
- label
- local agent
- parent
- permission
- plan
- plan permission
- projects in Bamboo
- queue
- reason
- remote agent
- remote agent supervisor
- requirement
- shared capability
- stage
- Stock images
- task
- triggering
- watcher
On this page
Related content
- Edit the parent of an issue with your keyboard
- Inherit all parent attributes
- Epic- You can't edit the parent of the issue. Not able to edit/add parent from the existing task
- Parent link is empty in issue search results
- Upcoming changes: 'epic-link' replaced with 'parent'
- How to Branch into Epic's Parent in Automation for JIRA Cloud using JQL and perform actions on the parent issue.
- Automation rule to fetch the parent's parent issue key on the current issue
- Link work item to a parent in your plan
- The Parent Links custom field is unusable
- Fixing Parent Links after Jira migration
A build's reason is the way in which the build was triggered.
Triggering in Bamboo allows plan builds to be started automatically. Bamboo has the following trigger methods:
- Polling the repository for changes — Bamboo polls the source repository for changes, either periodically or according to a schedule. This ensures that a plan build only runs when code has changed in the plan's source repository.
- Repository triggers the build when changes are committed — Requires that your source repository is configured to fire an event to Bamboo. This has the advantage of placing minimal load on your Bamboo server.
- Cron-based scheduling — Builds are run according to a schedule, regardless of whether any code changes have occurred. This can allow a team to structure the day according to a predictable schedule.
- Single daily build — The build is run at a specified time every day.
For more information, see Triggering builds.
Last modified on Apr 24, 2018
Related content
- Edit the parent of an issue with your keyboard
- Inherit all parent attributes
- Epic- You can't edit the parent of the issue. Not able to edit/add parent from the existing task
- Parent link is empty in issue search results
- Upcoming changes: 'epic-link' replaced with 'parent'
- How to Branch into Epic's Parent in Automation for JIRA Cloud using JQL and perform actions on the parent issue.
- Automation rule to fetch the parent's parent issue key on the current issue
- Link work item to a parent in your plan
- The Parent Links custom field is unusable
- Fixing Parent Links after Jira migration
Powered by Confluence and Scroll Viewport.