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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to preserve results and logs after changes in the plan configuration?

We fail to find build results from older builds after we manipulate the plan confuration.

We have a buid plan with three stage, let's call them:

  • Checkout Build
  • Test
  • Publish

Now we decide to Build and Test in one step, so we change the plan to:

  • Checkout Build Test
  • Publish

Observed Behaviour
All the result and logs from the previosuly existing stage "Checkout Build" are not accessible anymore. The stage still appears on the result view of previous builds, but no jobs of them are displayed.

Expected behaviour
All results and logs of the build jobs are always accessible, independently from the previous and current configurations.

How can we preserve all build results and all the log files which are produced during the build process, even if the plan configuration has changed?

1 answer

1 accepted

3 votes
Answer accepted
Marcin Gardias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 21, 2020

You need to upgrade to Bamboo 6.10.

Thanx for the hint. The update did it.

Just out of curiosity: Was that recognized as a bug or a missing feature?

Marcin Gardias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 03, 2020 • edited

Does it matter? ;)

This is something we realized is necessary to support plan branches better (see: for instance) and it was simpler and made a lot of sense to implement it for all cases where plan configuration stored in DB doesn't match the results.

So, you can say, it started as a (seemingly unrelated) bug and the we realized the best way to fix the bug is to add a missing feature as well.

Like Steffen Opel _Utoolity_ likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events