nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bamboo Specs YAML Features

Mark Kewley

I was able to get up and running creating a more complicated build plan with plugins (per-build-container) using the Java spec format.

However, Java is not something that most of us want to use at my company for configuration as code. We would like to use YAML as it's significantly easier to ramp up non software engineers (aka Ops team). I was going over they very limited documentation (Confluence/Docs). Is there more documentation or is YAML not quite as feature rich as Java?

Are there plans to have it be equivalent to the Java method? This will most likely be a dealbreaker for us, we've been using Bamboo/Bitbucket for years but we need a better CI/CD process like what Bitbucket pipelines offers but not as insecure.

Accepted answers

All comments

Grzegorz Lewandowski

Hello,

Thank you for contacting us. Java and YAML Specs are a little bit different in terms of it's base assumptions:

* Java is more powerful but the learning curve is a little bit higher (although it doesn't use any sophisticated language features so a person proficient in other programming language should handle that)
* YAML is simple and the learning curve is much smaller, although the price is in the tool completeness. Allowing to configure every available Bamboo config option in YAML would make the YAML really complex and hard to handle.

That's we implemented YAML with very limited set of options which we believe are the most crucial ones for CI/CD. solution Obviously we know some features are still missing therefore we're open for suggestions to understand what should be implemented.

What features BitBucket Pipelines offers that are crucial for you but Bamboo YAML Specs are missing?

Best regards,

Grzegorz Lewandowski

Mark Kewley

The problem with Java is though it opens the door to anything that can be run on a JVM which just means more potential languages to support. I agree it's simple to use but that's because I'm already proficient with Java. Teaching this to an Ops team is not something we would like to do.

Anything the Java feature has that the YAML does not is considered missing to me. One example is the ability to configure custom plugin support for the build agents. A complex YAML file is much easier to maintain for an Ops team over java.

Benjamin Kett

Grzegorz,

If I'm an operations person who's never written in Java before and the first thing I encounter on your tool is that requires me to learn an entirely new, strongly typed language and how to do Object Oriented Programming, I check out. No matter how someone who is a programmer thinks Java is accessible, it's complete nonsense to someone who has never defined a method or a class before.

What features do I want from your company's other CI tool in Bamboo YAML-specs? All of them. I want multiple build steps. I want the ability to pull multiple different container images, define scripts, etc. I want to be able to understand what my build is doing without having to translate Java to English.

Right now YAML specs does 1/10th of the job that your company already offers in YAML via Bitbucket Pipelines. I want to not have to go to my operations team and tell them "Well yeah, you'll have to write/update a Class to construct our build process. See? CI is easy!"

Ant no point would I call the Bitbucket Pipelines YAML "Overly complex". It describes my builds in an extremely declarative way: perfect for operations to understand and debug. Hand them an imperative-driven Java Class and a stacktrace from the JVM? Goes straight back to the developers for all issues and I'm back to where I am now: Developers doing a lot of stuff that is not developing, which is what CI/CD is supposed to mitigate.

Thanks,

Ben

Omar Herrera

Victor Debone_qkmjhv

I'm answering to keep this answer updated

We've just released Bamboo 6.9, which includes a fresh version of YAML Specs, version 2.0. This version includes a big expansion on YAML features, you can check more details here.

Omar Herrera

Thanks @Victor Debone

Romain Senechal

@Victor Debone Does it support Per Build Container in YAML spec ? cf https://bitbucket.org/atlassian/per-build-container/issues/23/documentation-for-perbuildcontainer-in

Victor Debone_qkmjhv

Thanks for reaching out @Romain Senechal.

Plugin configuration is not possible in the moment with YAML Specs.

We are tracking this feature here BAM-19841. I will add your comment as additional feedback for it.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

spec

yaml