triggering
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
- 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
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications
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 Sep 28, 2017
Related content
- Javascript Error when accessing Issues link in Project Navigation after Upgrade
- JVM Segfault (SIGSEGV) After Plugin Initialisation
- SIGSEGV Segmentation Fault JVM Crash
- Uncaught QuotaExceededError displays in browser using Jira server
- Character Encoding Issues when using JASIG CAS Authenticator
- JIRA Agile error during page load - curl already exists
- How to fetch the Team name from the comments by using Regex
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Error "Field with id' xxx' and name 'Team' does not support operation 'add' Supported operation(s) are: 'set'" on Jira Align Connector
- Configure the look and feel of Jira applications
Powered by Confluence and Scroll Viewport.