Bamboo Specs Runner

Bamboo Specs Runner is an archived command-line tool for Atlassian Bamboo that applies plan and deployment configurations from YAML specification files,…

  • Development
  • Infrastructure
  • Tools & Utilities
Bamboo Specs Runner is an archived command-line tool for Atlassian Bamboo that applies plan and deployment configurations from YAML specification files, letting DevOps teams manage CI/CD setup as code.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

27/100 Low

Maintained
0GitHub repository is archived
Popular
2212 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
304 GB minimum RAM
Security check
85no serious findings, tests
GitHub stars
12
Open issues
0
Last commit
2022-11-18
License
Apache-2.0
Activity
stale

Checked 15 days ago - source: GitHub (reecetech/bamboo-specs)

Resources & Compatibility

Minimum requirements: 4 GB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set the home path, then start Bamboo Edit 'bamboo-init.properties' with the correct home directory path, then run ./bin/start-bamboo.sh from the Bamboo folder. This starts the server and keeps your settings and build data in one place you can back up. source
  • Give each project a short unique key When creating a Bamboo project, set a Project Name and a short unique Project Key such as TP. The key is the compact code used by build plans and specs, so if it is missing or not unique, related builds may not connect correctly. source
  • Before running Before running, create a .credentials file with the Bamboo username and password, and keep it out of version control. source
  • Credentials and Authentication Create a .credentials file containing the Bamboo username and password used by the runner, and do not commit that file to version control. source
  • Credentials and authentication Before running, create a .credentials file containing your Bamboo username and password (username= / password=) and do not commit it to a repository. source
  • Building and running Build with 'mvn package', then run the generated jar, passing your YAML spec files (e.g. permissions.yaml, plan.yaml, deployment-project.yaml) as arguments. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can I use a custom Docker image for repository-stored Specs in Bamboo?

Yes, you can customize Docker images for the Bamboo Specs runner and configure Bamboo to use your own image for processing repository-stored Specs.

What project setting can prevent build plans and Specs from connecting correctly?

Each Bamboo project needs a short, unique Project Key. That key is used by build plans and Specs, so a missing or non-unique key can prevent related builds from connecting correctly.

How can I keep Bamboo settings and build data in a single backup path?

Edit bamboo-init.properties with the correct home directory path, then run ./bin/start-bamboo.sh from the Bamboo folder. This keeps the settings and build data in one place you can back up.

When might a Kotlin Bamboo spec not be detected by bamboo-specs-runner?

A Kotlin plan spec may not be detected even when the same setup works in Java. The forum Q&A targets that detection problem.

Answers sourced from community.atlassian.com, confluence.atlassian.com, confluence.atlassian.com, support.atlassian.com

Community

Collected 48 days ago - public community threads