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

How to configure Build expiry with YAML Specs

As the title says, we are desperately looking for a way to configure the retention policy for a build through YAML Specs.

The build itself works fine, but we cannot fine any information on how to configure the build expiry. Docs in this regard is extremely sparse:

"Miscellaneous plugins are used for various additional functionalities for plans and jobs like Build expiry [...] You can configure these plugins from the Other tab in the web interface." - which you cannot, if you are using Specs. The documentation is simply wrong.
"Some miscellaneous plugins work only on the job level while other work only on the plan level. When you choose a plugin, make sure you’re configuring it on the right level.
In case a plugin doesn’t have a dedicated builder, you can use AllOtherPluginsConfiguration to provide configuration for such plugins as a workaround. Refer to plugin documentation to obtain a list of valid keys. Note that keys imported with AllOtherPluginsConfiguration are not validated."

The only example provided is:

Build binaries:
    clean-working-dir: true

The corresponding Java-Specs (for which the docs contain an example for build expiry...) would suggest the following structure:

        duration: 1
        period: days


That only leads to:

Bamboo YAML import failed: Document structure is incorrect: Found following unused properties: plan / AllOtherPluginsConfiguration


Bamboo YAML import failed: Document structure is incorrect: Found following unused properties: AllOtherPluginsConfiguration


3 answers

I don't think it's possible yet.  The hint is when you set build expiry, then export as yaml, the diff is this comment:



# Some plugin configurations are not supported by YAML Specs


would be great to get an answer to this one

Welp, looks like if you're running 8.1.x, then you're in good shape.  This is a new feature on Bamboo 8.1.x, though, as it doesn't exist on 8.0.x.  It's even called out (sort of) in the release notes:

Improved feature parity between Java and YAML Bamboo Specs

We’ve added more features to the plan and deployments configuration with YAML Specs: other plugins, trigger repositories and trigger conditions, artifact handlers and plan dependencies.

Which is encouraging.  In fact, looking at the latest YAML specs docs, looks like the following is a "thing":

version: 2
concurrent-build-plugin: 5
useCustomArtifactHandlers: false
duration: 5
enabled: true
expiryTypeResult: true
maximumBuildsToKeep: 1
period: days

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events