-
Suggestion
-
Resolution: Fixed
-
None
-
2
-
We have been running Bamboo for a few months now, adding more and projects all the time. Among other build plans, each project has a full nighty build which is build at 04:00am. However we only want this plan to be triggered only when changes have been made to the repository. Currently there is no option to do this.
Note that polling the repository at 24h interval is not an option as this does not ensure the build is started at 04:00am or any other specific desired time of the day.
[BAM-1704] New Build Strategy: Polling the repository at a fixed time
Gregory Bonk
added a comment - this is something we're looking for when it comes to building Sonar reports. We want the build plan to poll the repository once a day @ a time we can set, and only build if there are changes. I believe this is the right feature issue for this
Gregory Bonk
added a comment - this is something we're looking for when it comes to building Sonar reports. We want the build plan to poll the repository once a day @ a time we can set, and only build if there are changes. I believe this is the right feature issue for this 
Thomas Loy
added a comment - I need this or BAM-1631. 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.
Thomas Loy
added a comment - I need this or BAM-1631 . 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. We're considering migrating from Luntbuild (which has this feature). Not having it is a deal breaker at the moment, since we don't have the server resources to run the nightly build for no reason.
As Greg pointed out, CruiseControl has option on scheduled build to require modifications.
This one issue may well determine whether we purchase Bamboo, because we have 265 active projects, and having every one of those build even when there is no change is simply unacceptable.
Our company would definitely see this as an improvement to the product.
We are currently hesitant to setup a scheduled build as we are using the tagger plugin which always tags on a successful build.
We don't want to clutter our tag list with builds that had no changes.
This would be useful for a periodic metrics build (sonar, maven site, etc). No need to generate new metrics unless the code has changed.
Greg Baysden
added a comment - Even CruiseControl has this feature, why not Bamboo? 
Stefan Hansel
added a comment - My vote for it.
We'd like to have regular builds at specific times of the day. But if nothing changed they should not take too much resources from the buildserver to have more resources for manual builds.
Stefan Hansel
added a comment - My vote for it.
We'd like to have regular builds at specific times of the day. But if nothing changed they should not take too much resources from the buildserver to have more resources for manual builds. 
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.