Bamboo TutorialIntroduction Installation Creating projects and plans Cloning (Copying) a build plan Configuring visible projects in Bamboo Editing build plan Changing the plan name Disable plan Delete the build plan Configuring stages, Jobs and Tasks Configuring build plan repositories Adding Scheduled build trigger Adding Repository polling trigger Adding new branch Running a branch Branch actions in Bamboo Configuring build plan permissions Configuring build notifications Expiry of the build history Passing parameters and variables to the build Adding Maven build plan Adding Gradle build plan in Bamboo Adding MSBuild task in Bamboo Adding MSTest task Linux shell build Windows batch command build Windows Powershell build Running the build plans manually build history build logs Bamboo Reports Authors Page in Bamboo Executing Selenium tests in Bamboo Creating and viewing artifacts Running customized build plan Build queue in Bamboo Agents Global Variables User Management Server Capabilities Linked Repositories Group Management Global Permissions Add-ons Management Email server Server address License Information in Bamboo Bamboo System Information Bamboo Audit log Import/Export build plans in Bamboo Build History clean up Bulk edit plan permissions Move build plan in Bamboo Delete build plans Bulk actions in Bamboo Adding deployment project to build plan in Bamboo Web application deployment to tomcat using Bamboo
Repository polling trigger in bambooRepository polling trigger allows us to run the build when source code in the repository changes. Bamboo polls the repository periodically or at specific time and if there are new changes in the repository, build is triggered. As shown in below image, Bamboo will poll the Visual studio repository after every 180 seconds. If changes are detected, build is triggered.
Complex problems, Simple Solutions