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

run bamboo job of an old commit using original bamboo spec as specified in the bamboo-specs/ folder

Jeroen De Vlieger June 11, 2019



It seems like I can not rerun a build of a historic commit using the bamboo java spec as it was specified in that commit. Instead it every bamboo job seems to use the current plan definitions.


I.e. lets say you have a repo with the following commits
1) initial import of project which includes a bamboo java spec under bamboo-specs/

2) develop features and commit changes

3) change the java spec under bamboo-specs/ 

4) implement a new features and commit changes

after step (3) it seems that all commits from step (2) are now build using the java spec defined in step (3)

Instead what I want is to be able to rerun a commit from step (2) using the java spec which was defined in step(1) and all commits from step(4) should use the java spec from step(3).


Is this not possible? Is there config flag to make it behave like that.

Every commit contains the bamboo configuration under the bamboo-specs/ folder. And yet every new bamboo job appears to disregard the bamboo-specs/ folder and just runs the plan as it is currently configured. Even if I try to rerun  a year old commit that has a different bamboo configuration in its bamboo-specs/ folder.


with kind regards,

Jeroen De Vlieger


1 answer

1 vote
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 13, 2019

Hello @Jeroen De Vlieger

It was a reasonable assumption about the way Bamboo would rerun old builds, but at the moment such behavior is not available. Specs is the first step to allow this in the future but we can't promise when this will be done.

I created a bug and filed a feature request when checking the scenario you described:


You can reestablish the old configuration by deploying it again to the server. The steps would be:

  1. Check out the specs repository in the revision that represents the configuration you want.
  2. Redeploy the configuration from your terminal using the command below:
    mvn -Ppublish-specs

Keep in mind that you will need to redo the steps above to set back the build configuration to the latest one again. It will allow new builds to run with the right configuration.

I hope that helps you to move forward.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events