When a new plan is cloned from the branch, the new plan is enabled by default and new build will be kicked off. But, the new build will be kicked off with the details from the cloned branch. This will be a problem since we don't want builds with the old branch repositories.
Previously, we had an option to disable the branch when we were cloning it. This helped us to edit the repository information or the variables. Looks like, it is removed with the recent update.
Can anyone suggest on how to disable the plan when we are cloning the old plan?
Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events