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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,703
Community Members
 
Community Events
176
Community Groups

Versioning of stages

Hi,

is it possible to version stages in Bamboo? We adjust our stages and jobs contionously and if I would like to build a project from a year ago I would like to use the stage that was active at that point in time and not the current active one.

Any ideas?

 

Thanks!

2 answers

2 votes

You might want to have a look at Bamboo Specs, which provide configuration as code for your build and deployment projects, thereby enabling you to commit your stages and jobs to version control alongside your source code. There are two approaches conceptually:

  1. Store your Specs in a separate repository and execute them on demand - this is usually used for managing administrative cross-project concerns etc.
  2. Store your Specs together with you code, aka repository-stored specs (RSS) - this allows you to keep your project configuration together with the code and automatically publish any code changes [...] and makes it easy to revert to a particular moment in time

Your use case seems to primarily suggest the latter approach, though as usual, how you implement your particular requirements depends on the specifics of your scenario.

Please note that there are two variations, and at this point Bamboo Specs (Java) is considerably more feature complete than Bamboo Specs (YAML) (this conceptual gap seems to be about to be narrowed in a near future release though).

Thanks a lot! That's exactly what I was looking for. At the same time, our source control system is Perforce. Does that mean I can't use this feature or does it just mean I have to use one of the supported systems along with my actual repository?

Starting from version 6.5, you will be able to use Bamboo Specs Java and YAML with the following repositories: 

  • Bitbucket Cloud
  • Git
  • GitHub

You can always use Bamboo Specs standalone with one of the supported systems as per option 1, but this indeed sounds like you may be unable to use option 2 at this point (repository-stored specs), because it requires a supported repository type for the fluent integration.

That being said, Perforce seems to have a Git facade, so you may be able to use that if your Perforce configuration provides this feature. I'm neither familiar with Perforce nor the inner workings of the Bamboo Specs integration though, thus cannot properly judge this in any way.

Like Sebastian_R likes this

That helped me a lot. Thanks for your insights!

1 vote

Hi Sebastian,

I opened a suggestion ticket based on this request, please find it below:

Thank you.

best,
Gabriel Ribeiro

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events