This is indeed exciting news! Looking forward to 4.3. Thank you James and the entire Bamboo team!

Hi folks,

We are super excited to announce that this feature is available in Bamboo 4.3 (due out in the next few weeks).

Thank you everyone who has provided their use cases and feedback.

Cheers,
James Dumay
Product Manager

It looks like this is still outstanding. This was actually a negative point when choosing Bamboo over Jenkins, which won due to the jira integration.
I would love to see arbitrary triggers associated with any given build.

I am thrilled to see some activity on this enchantment request. Managing essentially two identical plans, for every project we have, has become quite burdensome.

The differences between our two plan types is minor. Our "continuous" plan polls the repository at regular intervals, while our "daily" or "integration" plan kicks off once a day (even if there is no code changes), forces a clean checkout, and passes in an extra build parameter indicating a daily build. It would be spectacular if we could just have one plan handling both the continuous and daily clean build needs. Thanks!

Thanks Jens, but scheduled VCS polling doesn't solve the whole problem.
What we need is the possibility to trigger a build when there any changes in VCS and perform daily "integration" builds even if there is no changes in project itself, but because project dependencies might be updated (imagine that updated project dependencies are fetched from 3'rd party Maven repository, etc...).

In Bamboo 3.0 it will be possible to poll your VCS based on a cron schedule. The build will only be executed when there are changes to the source.

I realise that the improvements don't exactly match the requirements of the original issue. However, 3.0 will solve the problems that were mentioned in a number of comments on this ticket.

Please implement this feature. Coming from an open source product that has had multiple triggers for a long time, I automatically assumed that Bamboo would be able to do this.

I need this or BAM-1704. We are former Anthill Pro Users and it also had this facility. I currently do automatic QA build and deploys 2 times in a 24 hour period and automatic development build and deploys once a day. One of our applications is having a problem now because it increments and internal version number with every deployment. That app is starting to get "out of range" errors because of the number of deployments that are happening. I really want to do once or twice a day build and deploys only if there is a code change. Basically, my cron or time based build needs a checkbox that says something like "Build only if there are code changes since the last build"

We're also very interested in this feature. We want to trigger a Plan A build from Plan B every time Plan B is called, but Plan A should only build if there are changes in the source.

It really makes sense to have time and code changed based build plans.

Code changed strategy is used when - guess what - code changes in our project (projects).
But since also other libraries / artefacts are used - it would be nice to run build once a day (at night for example), to see if there is any change in those libraries that needs to be taken care of.

Also such mixed build triggering will be very useful in projects that are not under heavy development and where changes are not so frequent (let's say every few days / or on new change request). In such situation time based build will be used for checking for changes in external dependencies.

I'm really for this change!