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; } } }

Is there additional training/examples/support for setting up and running Bamboo Specs?

Jason Templeman

Having a lot of issue getting this running and not finding many resources online. I need to get this working quickly and look for and help I can get. Not using Docker so in the process of getting “Process Bamboo Specs in Docker” disabled by our IT department but still need to know the best way to setup our environment. We have 60+ plans and would like to have 1 repository contain all the Bamboo Spec's Java files.

I was able to create a new project and plan but haven't been able to create a new plan in our existing project.

Accepted answers

Jeyanthan I

Hi Jason,

I was able to create a new project and plan but haven't been able to create a new plan in our existing project.

Creating a Specs plan under a project should be pretty straight forward. This guide will help you understand how to create plans with Bamboo Java Specs - Create a simple plan with Bamboo Java Specs.

As you already have existing data with plans and deployments and you wanted to move them to RSS, I encourage you to export your existing Bamboo configs to Specs by following this documentation

This will speed up your learning process and as make your migration experience seamless. It’s a perfect starting point if you don’t know much about Bamboo Specs or configuration-as-code in general. In the code generated during export, you’ll see how the structure of Bamboo is represented by various dedicated Java classes and method calls.

More details on this can be found in this blog post:

How to win at CI with configuration-as-code and Bamboo Specs - Atlassian Blog

Documentation reference for both YAML Specs and Bamboo Java Specs, please refer the below reference.

Java Specs and YAML - Reference

Hope that helps.

Cheers,
Jey

All comments

Jeyanthan I

Hi Jason,

I was able to create a new project and plan but haven't been able to create a new plan in our existing project.

Creating a Specs plan under a project should be pretty straight forward. This guide will help you understand how to create plans with Bamboo Java Specs - Create a simple plan with Bamboo Java Specs.

As you already have existing data with plans and deployments and you wanted to move them to RSS, I encourage you to export your existing Bamboo configs to Specs by following this documentation

More details on this can be found in this blog post:

How to win at CI with configuration-as-code and Bamboo Specs - Atlassian Blog

Documentation reference for both YAML Specs and Bamboo Java Specs, please refer the below reference.

Java Specs and YAML - Reference

Hope that helps.

Cheers,
Jey

Jason Templeman

Thanks for the feedback. Let me continue by saying I am not a developer but I do know the Bamboo UI fairly well as well as Bitbucket and git. I'm not familiar with Java but will cross that bridge once I can the exported plans working. I'm also not part of IT do I don't have access to the Bamboo Server.

Edited response...

Is there a page that states the requirements to get Specs operational? By default it users Docker which was not available. I had that disabled and not I'm getting an error not being able to reach https://repo.maven.apache.org/maven2. I've asked them to add the proxy to the XML file. Each time I hit a snag I loose a full day of production. Is there anything else I should expect?

I was able to kind of/sort of get something working (changed source code in Bitbucket and got email stating there was a Specs failure due to issue above). This is a simple tutorial plan the just creates a plan and adds a "Hello World" job task.

I still cannot find any suggestion as to how a specs repo should be configured. All I see is the add a bamboo-specs folder to the project. Seeing how I want all our Specs in on repo would I expect something like this?

bamboo-specs
|
- plan1
- src
- main
- java
- project
- PlanSpec.java
- plan2
- src
- main
- java
- project
- PlanSpec.java

or

bamboo-specs
|
- src
- main
- java
- plan1
- PlanSpec.java
-plan2
- PlanSpec.java

Jeyanthan I

Hi @Jason Templeman

Let me continue by saying I am not a developer but I do know the Bamboo UI fairly well as well as Bitbucket and git. I'm not familiar with Java but will cross that bridge once I can the exported plans working

In that case, I suggest you to check if YAML specs is easier for you to implement.

Seeing how I want all our Specs in on repo would I expect something like this?

Your latter interpretation is almost correct. They should all be in one folder 'bamboo-specs'.
Then, within each, we can have a file per project, with each having the @BambooSpecannotation above the class declaration. For instance, it should look like this:

specsrepo/bamboo-specs/src/main/java
| => tree
.
└── tutorial
    ├── PlanSpec.java
    └── PlanSpec2.java

Each of the PlanSpec.java files contains the code for a separate build plan of the same project or a different project.

This Bamboo specs - Troubleshooting FAQs might help.

Should you have any further queries, feel free to contact Support (if you have the appropriate license) or here.

Jeyanthan I

Added to my previous comment, I thought this java property might come handy while debugging issues with your Specs code. It adds verbose logging to your atlassian-bamboo.log:

"-Dbamboo.specs.log.level=DEBUG" in <Bamboo-install>/bin/setenv.sh under JVM_SUPPORT_RECOMMENDED_ARGS.

You would need to restart Bamboo to apply this change.

Welcome!

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

Quick Links

Find more posts tagged with

bamboo

spec