CodeSign Secure Documentation
  • Overview
    • About CodeSign Secure
    • Getting Started
    • Documentation Guide
    • Portal Overview
    • Troubleshooting
      • FAQ
    • Glossary
  • Reference Guide
    • Header Bar
      • CodeSign Secure Documentation
      • Swagger API
      • Profile Section
    • Dashboard
      • Key Performance Indicators
      • Issued Certificates
      • Signatures Generated
      • HSM Health Check
    • Keys and Certificates
      • Key and Certificate Lifecycle
    • App Management
    • Signing Requests
      • Approval Workflows
    • Signing Tools
    • Reports
      • Signing Request Report
      • Audit Trail
      • Certificate Report
      • Client Report
    • Logs
    • System Setup
      • Identity Store
      • Backup
      • User
      • Roles and Permissions
      • Email
      • Signing Projects
      • SSL/TLS Management
      • Environment
      • Plugins
  • Setup & Architecture
    • Identity and Access Control
    • Architecture and Concepts
    • Installation
      • Windows
        • Installing the Server
        • Ports and Protocols
        • High Availability and Backup
        • Upgrades and Compatibility
    • Security
      • Security Hardening Checklist
      • Client Authentication
      • Designing Signing Policies
  • Release Notes
    • Releases for 2026
      • v3.2.1
    • Releases for 2025
      • v3.2.0
    • Releases for 2024
      • v3.1.0
  • API Reference
    • Getting Started
    • Authorizing Requests
    • Securing API Access
    • Request and Response Conventions
    • Endpoint Reference
      • Signing
      • Signing Requests
      • Certificates
      • Applications and Environments
      • User Management
      • Permissions
      • Email
      • System Setup
      • Reports
      • Dashboard
      • License
  • Integration Guides
    • Signing Capabilities
      • Supported Formats and Platforms
      • Timestamping
      • Windows Signing - SignTool
        • Signing
        • Macro Signing
      • Apple Signing
      • AppX & MSIX Signing
      • Visual Studio ClickOnce
      • Jar Signing
      • Sign HLK/HCK using CodeSign Secure
      • NuGet Signing
      • Mage Signing
      • Sign OVA/OVF using Encryption Consulting’s Utility Tool
      • Utility Tool for code signing
      • Container Signing
      • PKCS11 Wrapper
        • APK Signing
        • OpenSSL Signing
        • XML Signing
        • JSign Tool Signing
        • Jarsigner Signing
        • GPG2, Debian & RPM Signing
      • Reproducible Build
        • Automated Hash Validation
        • Reproducible Build Process Flow
        • Pipeline Script Components
        • Hash Validation
    • CI/CD Integration
      • GitHub Actions
      • Jenkins
      • GitLab
      • Azure DevOps
      • TeamCity
      • Bamboo
      • Securing CI/CD Credentials

Bamboo – Atlassian CI/CD Pipeline

  1. Download Bamboo

    • Go to the Atlassian Bamboo download page to download the version that is suitable for your Windows system.

    • Check the compatibility for your supported platform here.

  2. Install Bamboo for your Windows 11

    • Once the Bamboo zip file is downloaded, extract it to your desired directory, for example, C:\Atlassian\

    • Bamboo requires Java to run. Make sure your system has JDK 17 installed.

    • After installing JDK 17, set the JAVA_HOME environment variable to the path of your JDK 17.

  3. Configure Bamboo

    • Open the extracted folder and navigate to this path: <Bamboo installation folder>/Atlassian-bamboo/WEB-INF/classes/ and open the bamboo-init.properties file.

    • In this file, insert the property “bamboo.home”, with an absolute path to your Bamboo home directory (for example, C:\Atlassian\Bamboo). Your file should look like this: bamboo.home=C:\Atlassian\Bamboo

    • Open a command prompt as an Administrator in the Bamboo installation directory (C:\Atlassian)

    • Start Bamboo using the following command: bin\start-bamboo.bat

    • Access Bamboo from a browser by going to http://localhost:8085

  4. Setup Bamboo on the web portal now

    • You will be asked for a license.

      Bamboo License

    • You have to copy your Server ID.

    • Go to the license evaluation site and select your product as Bamboo. After that, enter the necessary details, and then the Server ID is copied above.

      This will generate your License.

      Bamboo License Generation

    • Paste this license on the Bamboo Dashboard and click on “Continue.”

      Bamboo License Copy on Dashboard

    • Configure the Instance with the necessary details.

      Bamboo Configurations

    • Bamboo requires a database to store build data. You can use PostgreSQL, MySQL, or any supported database. By default, Bamboo will offer to use an embedded HSQL database, but for production use, it’s better to configure an external one (like PostgreSQL or MySQL). In our case, we are using an H2-embedded database; you can follow this guide.

    • After configuring the Database, complete the setup in the Web UI, by configuring an Administrator Account (admin username, password, and email).

  5. Install Bamboo agents

    • Download the Remote Agent Jar from the Agents section inside Build Resources.

    • In the Agents tab, you’ll see a list of both local and remote agents that are connected to Bamboo. If you don’t see any agent, click on the “Install Remote Agent” button.

      Bamboo Administration

    • After that, you’ll be prompted to approve the agent.

      Bamboo Approve Agent

    • Check the agent’s status and capabilities after clicking on the Agent.

      Bamboo Agent Status

  6. Create and configure a new Bamboo Plan

    • Navigate to the Dashboard and click on Create > Create Plan.

      Bamboo Create Plan

    • Configure the plan by selecting its Project name, Plan name, and Plan key (Bamboo will auto-generate this key based on the Plan name).

      Bamboo Plan Details

    • You will be required to provide a Repository Host. (we’re going to sign an already compiled file, so we chose “None”).

      Bamboo Repository Host

    • Choose the environment you want to run this Job (Agent Environment) and then click on “Add Task.”

      Bamboo Agent Environment

    • Search and select “Script” for this job.

      Bamboo Script Setting

    • For the script location, select “Inline” and the Interpreter as “Shell” for this job.

      Bamboo Script Setting

    • In the script body, paste the signtool command you want to run ("C:\Program Files (x86)\Windows Kits\10\bin\10.0.26100.0\x86\signtool.exe" sign /csp "Encryption Consulting Key Storage Provider" /kc DemoCertificate /fd SHA256 /f "C:\demo files\Signing Certificates\DemoCertificate.crt" /tr http://timestamp.digicert.com /td SHA256 "C:\demo files\Test Files\TestFile1.exe") and click on “Save”.

      Bamboo Script Signing command

    • After the task has been created successfully, click on “Create”.

      Bamboo Success

    • You can see the Plan details now.

      Bamboo View Plan Details

    • Then click on “Run Plan” in the Run dropdown.

      Bamboo Run Pipeline

    • You can see that your job has been successful.

      Bamboo Pipeline Job Success

    • Check the signature details in the executable file’s properties.

      Checking File Signature

On this Page:
Support Privacy Policy Terms of Service

Copyright Encryption Consulting LLC. All rights reserved.