I'm implementing continuous integration using Bamboo. So I have bamboo poll our SVN repository and build as needed. Then on a certain time interval (e.g. an hour) I have the latest build deployed to a dev environment using a schedule trigger. The problem is that even if there is only one actual build per day, Bamboo creates a new release each time it deploys. By the time I run a build from dev to stage to production there is really no way to match the release numbers. Is there a way to prevent it from creating a new release unless there has been a new build?
We do something similar for nightly tests. What I did is setup the tests as a manual stage and have another plan with a scheduled trigger fired them off with API calls.
I explain here, and thanks to @Eric Fusciardifor the update, how to use the api to retrive deployment information and how to fire off a deployment. With that you can write your own logic and control them however you want and trigger your logic from another Bamboo plan or any scheduler.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mike, I'm facing the same issue, just curious, which direction did you end up going with in order to work around this issue? Thanks, I'd appreciate your comment.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1. Set your build to be triggered by SVN commits
2. Then, set your trigger for the deployment project
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This would cause a deployment whenever the build happened, which is not what I want.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess I misunderstood your predicament.
Can you explain why you need to do this "I have the latest build deployed to a dev environment using a schedule trigger"? Seems unnecessary to deploy when there is no change.
As far as deployment automation, it would only make sense to auto deploy to dev and staging, never to uat or production.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is unnecessary to deploy when there is no change. That's the problem. I want to deploy on a schedule, provided that there have been changes. But in bamboo if I set a schedule trigger for deployment it creates a new release and deploys - even when there were not any changes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.