Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


moving all builds one branch to another

We have a Bamboo which is executing all the builds under branch "develop".
Now we created another branch from "develop" called "v1.0.1" which is a plan branch under bamboo.

Now when a user commits the code under "develop" the builds get triggered and similarly for "v1.0.1".

But we also updated the develop branch version (v1.0.2), but kept the branch name same as "develop".

When a user commits under 1.0.1 build number start from 1
When a user commits under Develop build number start from 300 (as there was other builds before we updated the version).

Now the ask over here is::
Is there a way I can move all the previous builds from develop (before we branched) till 299 under plan branch (v1.0.1)?

1 answer

0 votes
Jeyanthan I
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 13, 2020

Hi Pankaj,

Is there a way I can move all the previous builds from develop (before we branched) till 299 under plan branch (v1.0.1)?

All the builds are tagged to the respective Plan branches. Thus, it is not possible to move builds to a different plan branch.

However, what I can suggest you is to reconfigure your 'develop' branch to point to different plan branch, so that the existing builds remain intact and you can continue to use the same build history.

To do this, you'll just have to navigate to the respective plan branch, then go to Repositories tab and update the name of the branch.

Let's know if it works for you.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events