Bamboo Integration Guide

Steps:

  1. Download Bamboo
  2. Go to the Atlassian Bamboo download page to download the version that is suitable for your Windows system.
  3. Check the compatibility for your supported platform here.
  4. Install Bamboo for your Windows 11
  5. Once the Bamboo zip file is downloaded, extract it to your desired directory, for example, C:\Atlassian\
  6. Bamboo requires Java to run. Make sure your system hasJDK 17installed.
  7. After installing JDK 17, set the JAVA_HOME environment variable to the path of your JDK 17.
  8. Configure Bamboo
  9. Open the extracted folder and navigate to this path: <Bamboo installation folder>/Atlassian-bamboo/WEB-INF/classes/ and open the bamboo-init.properties file.
  10. 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
  11. Open a command prompt as an Administrator in the Bamboo installation directory (C:\Atlassian)
  12. Start Bamboo using the following command

    bin\start-bamboo.bat
  13. Access Bamboo from a browser by going to http://localhost:8085
  14. Set up Bamboo on the web portal now
  15. You will be asked for a license.

    Bamboo License Key
  16. You have to copy your Server ID.
  17. 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.
  18. This will generate your License.

    Bamboo Trial License
  19. Paste this license on the Bamboo Dashboard and click on “Continue.”

    Bamboo License
  20. Configure the Instance with the necessary details.

    Instance Configuration
  21. 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.
  22. After configuring the Database, complete the setup in the Web UI by configuring an Administrator Account (admin username, password, and email).
  23. Install Bamboo agents
  24. Download the Remote Agent Jar from the Agents section inside Build Resources.
  25. 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.

    Remote Agent
  26. After that, you'll be prompted to approve the agent.

    Approve Agent
  27. Check the agent's status and capabilities after clicking on the Agent.

    Agent Summary
  28. Create and configure a new Bamboo Plan
  29. Navigate to the Dashboard and click on Create > Create Plan.

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

    Plan Creation
  31. You will be required to provide a Repository Host. (We're going to sign an already compiled file, so we chose “None”).

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

    Agent Environment
  33. Search and select “Script” for this job.

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

    Script Location
  35. 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

    click on “Save”.

    Script Body
  36. After the task has been created successfully, click on “Create”.

    Task Creation
  37. You can see the Plan details now.

    Plan Details
  38. Then click on “Run Plan” in the Run dropdown.

    Run Plan
  39. You can see that your job has been successful.

    Job Successful
  40. Check the signature details in the executable file's properties.

    Signature Details