You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
in a Git repo there are already YAML specs that get automatically published via Bamboo Specs Scan. These specs are doing a job related to the application code, but not building the app.
Now I'm creating new Java Specs to build and deploy the actual app code. These specs should not be deployed automatically but on demand by the developers.
Both Specs are stored now in the same directory. And I'm wondering which Specs will now be applied - Java, YAMl or both?
Is it possible to ensure, that the YAML Specs will be applied as before and the Java Specs will not be applied automatically?
Hello @Michael,
As stated on the Bamboo YAML Specs page:
Bamboo always looks for YAML Specs first. If it doesn't find YAML Specs, Bamboo tries to find and process Java Specs.
Best regards,
Eduardo Alvarenga
Atlassian Support APAC
--please don't forget to Accept the answer if the reply is helpful--
What you can do is to store your Java Specs in a location that Bamboo won't scan, i.e. in a folder _not_ named bamboo-specs.
You'll still be able to publish those specs running Maven (mvn -Ppublish-specs)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.