In our org using Bamboo as a CI tool. This Bamboo is integrated with Salesforce.com. We have QA, Develop and Master branch. We are using JIRA, Bitbucket and Bamboo for our deployment.
Whenever a developer makes change in a branch created from Develop branch. Then he pushes the code to git using source tree. Then run bamboo build which is used to merge the changes from Individual branch to QA branch as well as move the changes to qa environment. Here is our challenge. When the individual branch runs all the components runs for deployment. Almost we have 8000 components and all the components are deploying to qa environment.
Question : Is this possible only modified components deployed in qa? if it is possible then how to do it in Bamboo.
Harven,
Is it possible to break down the 8k components into separate build plans and repositories??
When you commit and push a change to a repository, any builds associated with that repository (depending on triggers) will build. And if you have deployments configured to automatically deploy based on successful builds, all of those tasks will also get deployed. Which is what it sounds like is happening.
If you separate the components into separate build plans and different repositories (or assign those build plans to specific branches). You will be able to configure Bamboo to only build/deploy from just the one change which was made.
We do have an open feature request for this here:
Please be sure to watch it, and vote on it, so that you're notified if this is implemented in a future release. For your reference, you can find our policy on how we prioritize feature and improvement requests at this page:
BAM-17005: Add ability to update deployment with only changed artifacts
You can also add a comment to the feature request to explain your specific use-case to the developers.
I have also added a link to this post so that the developers can reference it if necessary.
Thank you, Robert Watson Dev Tools Support | Atlassian
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.