• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 3.0
    • Triggers
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Should be able to have builds that are scheduled via a cron "build strategy" execute only if changes where found in the repository. This way you could ensure that builds start e.g. at the full hour only (8:00, 9:00 etc), so when you commit code you don't have to wonder (or bother to check...) if you just missed a build or how soon to expect feedback from Bamboo. This is even more important if builds are done even less frequently.

            [BAM-2496] Conditional, cron-based scheduling

            jens added a comment -

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

            jens added a comment - Bamboo 3.0 allows to poll your VCS based on a cron schedule. The build will only be executed when there are changes to the source.

            This functionality could be added by adding a schedule to the agent. Then the build would be deployed only of there was a change and it would be deployed the next time the agent ran.

            This would solve my problem with a report build that swamps the build server. As it stands I can run it when there is a change or I can run it at night when no one else is using the server. What I really want is to run it at night when there is a change. Give me a CronAgent (or something similar) and we will all be happy.

            Jon Strayer added a comment - This functionality could be added by adding a schedule to the agent. Then the build would be deployed only of there was a change and it would be deployed the next time the agent ran. This would solve my problem with a report build that swamps the build server. As it stands I can run it when there is a change or I can run it at night when no one else is using the server. What I really want is to run it at night when there is a change. Give me a CronAgent (or something similar) and we will all be happy.

            Thomas Loy added a comment -

            I need this or BAM-1631 or BAM-1734. 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. I should have some sort of checkbox in the build plan that says something like "Build only if there are changes since the last build".

            Thomas Loy added a comment - I need this or BAM-1631 or BAM-1734 . 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. I should have some sort of checkbox in the build plan that says something like "Build only if there are changes since the last build".

              bmccoy bmccoy
              ac6f1baaae63 Eric Jain
              Votes:
              11 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: