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

Pushed code that triggers the build but PlanSpec nothing happens Bamboo Spec Plan


I´ve setup a project to work with Bambo specs (6.3.1) but when pushing the code the plan does not reflect the changes i did on the code. What i did:

I have followed all the steps in the tutorials, so i double checked and everything seems apparently ok. My integration is between Bamboo and Bitbucket so it should be event smoother 

1- Created a linked repository with all the configs as they should be.

2 - I have a branch and a plan that point to this repository.

3 - Pushed code to ( e.g. changed the plan description and nothing happens).


Thanks in advance,

Tiago Domingues


1 answer

1 vote
Gabriel Ribeiro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 06, 2018

Hi Tiago,

I have some questions that may help you troubleshoot this:

  • Are you sure that the repository has access to the project you're trying to edit/add plans?
  • Are you respecting the default specs project folder structure (repo.git/bamboo-specs/)?
  • Are you sure you have Maven 3.2 (or higher) installed on the Bamboo server machine?
  • Could you please double check if the "Process Bamboo Specs in Docker" option is enabled in Cog icon>Overview>Security Settings, if yes, do you have Docker installed on the Bamboo server machine?
  • Could you please look for the [RepositoryStoredSpecsServiceImpl] class in Bamboo logs (bamboo-home/logs/atlassian-bamboo.log) and see if there are any error messages there?

Let us know if the questions helped you.


@Gabriel Ribeiro thanks for the great reply. The configs were all good but i was not respecting the default structure for the project. I thought we could integrate it with my existing pom from our main project. Is there a way to override this or we should use separation of concerns ?



Gabriel Ribeiro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 09, 2018

Hi Tiago,

I'm afraid that it will not be possible for now. It's a requirement to have the specs project (including the pom.xml file) in the bamboo-specs directory, under the repository root, Bamboo need this "separation of concerns" to distinguish specs project from other projects that you may have in the same repo.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events