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,718
Community Members
 
Community Events
176
Community Groups

Adding dependencies in bamboo java specs

Edited

Is there a way to get around this requirement for bamboo java specs?

  • it's sufficient to compile your project with bamboo-specs and bamboo-specs-api dependencies only - don't add extra dependencies

 We have a large number of repositories.  Each repository has bamboo specs stored with it.  However, many tasks defined in those plans are common.

As such, I'd like to create a utility helper class and put all of the job tasks within that utility.    That utility class can then be versioned and published to a nexus repository -- which could then be used as a dependency within each bamboo spec plan.....

Right now, there doesn't seem to be a way to do this -- and I would have to have copies of the utility class in every single repository .... which makes one of the major points of moving the plan into code not very useful.... since I still have to edit every single plan in order to fix a bug in one of the common tasks.

Any help is appreciated.

1 answer

1 accepted

1 vote
Answer accepted

Hi Chris,

Did you try to set the dependencies at the BAMBOO_INSTALL/atlassian-bamboo/WEB-INF/classes/bamboo-specs-pom.xml file?

thanks

I figured this out.  I did edit the above file, in order to add a <repositories> section in there to point to our own nexus server.  However, when I did this, I had <snapshots><enabled>false</enabled></snapshots> my utility class was currently building snapshot versions only.  This ended up being the problem.

The <dependency> information seems to work properly in the project itself and I did not need to modify the 2 default dependencies in the bamboo-specs-pom.xml file.

Looks like the bullet in your product documentation is wrong, since it does work with additional maven dependencies.

How do you handle updates made in the utility? Do you have a trigger that all repositories update their specs?

It's not the best, but once the utility gets re-published to nexus, then you have to go back through all the repositories and trigger a publish-specs (mvn -Ppublish-specs).

I just created a script that will do this, and made it a plan in bamboo itself... so after a new utility version is published, you just go execute the "update all plans" plan which basically just iterates through all the repositories, does a shallow clone of each, goes into the bamboo-specs directory and runs mvn -Ppublish-specs

Hello @Gabriel Ribeiro

We are facing the same problem. I have one question about that file.

Are the changes persisted during bamboo updates?

 

Regards,

Hugo

Hello @Chris Johnston , 

What do you mean exactly with this ? 

which basically just iterates through all the repositories

I'm interested in having something like this, but I cannot get a proper way of managing this. Is this something you just scripted or implemented along with Java specs ?

Thank you,

Andrea

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events