youngmon/atlassian-qna huggingface dataset:
Password Reset Issue with BambooHR Account
Asked by haneryyy:

Facing trouble resetting my BambooHR account password. Followed the standard recovery steps, but no success. Any advice?


Answers:
author: Martyna Wojtas
body: Hi [@haneryyy](/t5/user/viewprofilepage/user-id/5336180)

if you mean [BambooHR](https://www.bamboohr.com/pl-pages/hr-software/?s_kwcid=AL!18332!3!462966873598!e!!g!!bamboohr&utm_campaign=BAMB-DG-SER+PRO-2022EG&utm_medium=cpc&utm_source=google&utm_content=blank&utm_term=blank&CampaignID=11075736231&AdGroupID=107784956839&AdID=462966873598&AdPosition=&Target=&TargetID=kwd-36107328090&MatchType=e&ClickID=Cj0KCQiA35urBhDCARIsAOU7Qwk1L2jR5BlBU0eKzuqARBYfnOw1pj6bXcRelV365Fs2XymXpm9gqZUaAk0REALw_wcB&Network=g&Device=c&Keyword=bamboohr&AdExtensionID=&_bt=462966873598&_bk=bamboohr&_bm=e&_bn=g&_bg=107784956839&gad_source=1&gclid=Cj0KCQiA35urBhDCARIsAOU7Qwk1L2jR5BlBU0eKzuqARBYfnOw1pj6bXcRelV365Fs2XymXpm9gqZUaAk0REALw_wcB) - it's not an Atlassian product, so I'm afraid we won't be able to help.

Best regards

Martyna

Product Manager for Bamboo DC


author: Shashank Kumar
body: Hello haneryyy,

Welcome to Atlassian community.

If you are on Bamboo version **6.6** or higher, you can follow this page to use a recover_admin account <https://confluence.atlassian.com/bamboo/lockout-recovery-process-952624910.html>

If not let me know your Bamboo version and we'll see if there is any other alternatives available.

Regards,

Shashank Kumar

**\*\*please don't forget to Accept the answer if your query was answered\*\***
Ephemeral agent : configure access to kubectl
Asked by Antoine Ameline:

Hi, I use bamboo server and with the last 9.4, I'd like to use the ephemeral agent concept.

My bamboo test server is running on a VM Debian 10 (only terminal)

Following documentation (cf. <https://confluence.atlassian.com/bamboo/enabling-ephemeral-agent-support-1236444140.html>), I tried to configure access to my k8s cluster :

\* adding kubectl on my bamboo server (VM debian) =\> ok

\* adding my config file under \[my install\]/server/shared =\> ok

\* configuring access to the config file in bamboo administration screen =\> not ok

Our cluster access is manager with OIDC (keycloack) and Iv'e got this error message :

*** ** * ** ***

*error: unknown command "oidc-login" for "kubectl" Unable to connect to the server: getting credentials: exec: executable kubectl failed with exit code 1*

*** ** * ** ***

How can I configure bamboo to pass oidc authentication ?


Answers:
author: Eduardo Alvarenga
body: Hello [@Antoine Ameline](/t5/user/viewprofilepage/user-id/4754343)

Based on your description, it appears that your Kubernetes configuration requires the ***oidc-login*** command to be available. Copy that file to the Bamboo Server and try again.

Sincerely,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**


author: Antoine Ameline
body: Hello [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410) ,

Sorry for my late answer, I was on other subjects.

So, for me, installing the oidc-login was not a solution. Problem with this tool, is that it's requiring the browser to authenticate against keycloack.

In my case, my bamboo server is indstalled on debian terminal server.

After some tests, I finally choose a solution with a service account with a long life token. As my bamboo server is not exposed, it's not a security problem

Thanks for your help

I set the post as resolved
dc app performance toolkit setup error
Asked by Eldan Vaknin:

I'm trying to run the app performance toolkit according to this [guide.](https://developer.atlassian.com/platform/marketplace/dc-apps-performance-toolkit-user-guide-bamboo/#instancesetup)

It seems to work up to the point of creating the cluster and then it fails in creating an EKS Node Group.  
I use an admin account for my AWS, and checked specifically that I have full access permissions for EKS, but the error looks like a permissions error.  

Has anyone encountered anything like this?  

Error: creating EKS Node Group (atlas-bamboo-build2secure-cluster:appNode-m5_2xlarge-20231126084423785900000011): InvalidRequestException: You are not authorized to launch instances with this launch template.


Answers:
author: Khushboo Gupta
body: Hello [@Eldan Vaknin](/t5/user/viewprofilepage/user-id/5328292)

Welcome to the Atlassian Community!

Based on the error message you've shared, it appears the issue is with launching instances using a specified launch template, rather than with EKS (Elastic Kubernetes Service) permissions directly. This can happen due to a few reasons, even if you're using an admin account. Here are steps and aspects to check and potentially rectify the problem:

* Even though you're using an admin account, it's worth double-checking the IAM policies attached to your user or role. Specifically, ensure that the permissions include actions related to EC2 instances and launch templates.

* The error specifically mentions an issue with the launch template.
  * Verify that the IAM role or user has permissions to use the specified launch template.
  * Ensure the launch template referred to by your EKS Node Group actually exists.
* If the launch template specifies a custom AMI (Amazon Machine Image), ensure that your account has the permissions to use this AMI.

Incase the everything seems to be correctly configured, Check AWS CloudTrail logs for the failed operation. And Try manually creating an instance using the problematic launch template via the AWS CLI or AWS Management Console. This can help isolate whether the issue is with the launch template itself or the way EKS is attempting to use it.

Hope it helps!

Regards,

Khushboo Gupta
How to call Bamboo REST API from Jira Cloud Automation via Application Tunnel
Asked by Pieter Wouter Hartog:

I'm excited about Bamboo's support for Application Tunnels since 9.3. Should avoid a lot of setup and connection headaches.

One thing that doesn't work for me yet: doing a web request from Jira Cloud Automation to my local Bamboo server via the Application Tunnel.

The application URL from the tunnel looks something like this:

```
http://e<lots of numbers and letters>592.self-hosted.atlassian.com
```

In my Jira Cloud Automation rules I have a web request action that looks something like this:  

```
http://e<lots of numbers and letters>592.self-hosted.atlassian.com/rest/api/latest/queue/WT-BB?bamboo.triggerReason.jiraProjectKey=BPTB&bamboo.triggerReason.jiraVersion=BB-REL-005&bamboo.triggerReason.jiraVersionId=10083&bamboo.triggerReason.jiraProjectName=... and more variables
```

But my jira cloud automation rule basically errors and a build was never queued in Bamboo. This is the error in the Jira Automation audit log:

```
Web request was sent, but timed out after 30 seconds on the remote host so the result is unknown (but most likely successful).
```

How is this supposed to work with Application Tunnels?


Answers:
author: Pieter Wouter Hartog
body: See the same discussion on the Jira Cloud forum: [https://community.atlassian.com/t5/Jira-Software-questions/Jira-Automation-Web-Request-through-Application-Tunnel/qaq-p/2541275?utm_source=dm\&utm_medium=unpaid-social\&utm_campaign=P:online\*O:community\*I:social_share\*](https://community.atlassian.com/t5/Jira-Software-questions/Jira-Automation-Web-Request-through-Application-Tunnel/qaq-p/2541275?utm_source=dm&utm_medium=unpaid-social&utm_campaign=P:online*O:community*I:social_share*)

No real answers though, except for 'most likely this doesn't work'.


author: Emanuele Mariani
body: This solution not work, please vote this issue:

[\[AUTO-1122\] Allow Jira Automation to Send Web Request through an Application Tunnel - Create and track feature requests for Atlassian products.](https://jira.atlassian.com/browse/AUTO-1122)


Tags: application-link

automation

jira-cloud

server
Disable a build stage/job using bamboo api
Asked by vikeshk:

Hi, Is it possible to disable a build plan job using bamboo api?  

Gone through below page but didnt find a relevant api.  
<https://developer.atlassian.com/server/bamboo/rest/api-group-api>


Answers:
author: Eduardo Alvarenga
body: Hey [@vikeshk](/t5/user/viewprofilepage/user-id/5365844)

Welcome to **Atlassian Community**!

If you want to disable a Job, send an HTTP **DELETE** request to

*

  ```
  /rest/api/latest/plan/PROJ-PLAN-JOB/enable
  ```

E.g.

*

  ```
  curl -L -X DELETE -u admin:admin 'https://bamboo.mydomain.net/rest/api/latest/plan/PROJ-PLAN-JOB/enable'
  ```

If you want to enable it again, please send an HTTP **POST** to the same endpoint.

Sincerely,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**

comments: author: vikeshk
body: Thank you [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410) for the quick response

Actually, I am trying to disable the build job for specific build number.

if a build plan has job1 and job2, In job 1, I have a script to check if job 2 needs to run or not and would like to make an api call to disable job2 of the specific plan instance(using build number).  

other approach i tried, is to use dynamic Deactivation task(in job2) but its unable to read injected variable created in job1 and condition returning evaluated as null.

<br />

please let me know if there is any approach to achieve this. Thank you!
Can Bamboo DataCenter run well in a container?
Asked by gabriel_silva:

Hi

I'm planning the migration of a neglected Bamboo server, as well as its ongoing support.

Our current setup consists of a large EC2 instance running Bamboo Server 7.2 with no remote agents; all builds and deployments are managed by 15 virtual agents. (I guess main driver for this migration end-of-life of Bamboo Server).

<br />

Ideally, I would like to deploy it on a Kubernetes Cluster, but that's not feasible within my company's current infrastructure. Moreover, I am required to training our engineers to support this new architecture. So, I am focusing on more incremental improvements to start with.  

I believe that simplifying the process by using containers should alleviate concerns about future upgrade ... So ...

Here's the approach I am considering - Please keep in mind that I must follow this upgrade path: 7.2.x ? 8.0.12 ? 9.4.x.  

1 - Containerize Bamboo DataCenter 8 and start the container with Docker, mapping the old Bamboo folders to the container.  

2 - After the migration to Bamboo 8 is complete, I will repeat this step for Bamboo 9.  

3 - Initially, I plan to keep it running with the same virtual agents. Then, in the following week, I will introduce a remote agent and gradually phase out the virtual agents.  

4 - Train the people :)  

Just looking for some advise. Are there any concerns with running the server and agents in a container? Also, assuming the host server has sufficient resources, do you anticipate any stability issues?  

<br />

Thanks  


Answers:
author: haneryyy
body: Your migration plan seems sound. Containerizing Bamboo Data Center is a good approach, and using Docker to map old Bamboo folders can simplify the process. Running the server and agents in containers is generally feasible, but it's essential to ensure the host server has sufficient resources for stability. Be attentive during the migration to Bamboo 8 and then Bamboo 9, ensuring a smooth transition. Introducing a remote agent gradually and phasing out virtual agents is a practical strategy. Lastly, training your team is key to successfully adopting and supporting the new architecture. Overall, your incremental approach and focus on containers align well with best practices for a Bamboo upgrade.

Best of luck with your migration!

comments: author: gabriel_silva
body: Thanks for the feedback haneryyy.
Upgrading to 9.2.7 still shows 9.2.4 in the Footer
Asked by brian_schrader:

I have upgraded from 9.2.4 to 9.2.7 to mitigate the critical security vulnerability I was notified about. However after doing the upgrade twice and verifying the installer version (9.2.7) I still see 9.2.4 in the footer and I am unsure if the upgrade worked. However it seems to have completed successfully each time and I'm at a loss for how to verify the version number other than the footer.


Answers:
author: haneryyy
body: Hello Brian,

If you've upgraded Confluence to version 9.2.7 but still see version 9.2.4 in the footer, try the following steps to troubleshoot and ensure the correct version is displayed:

**Clear Browser Cache:**   
Clear your browser cache to ensure that the updated version information is loaded.

**Verify Database Schema:**   
Confirm that the database schema upgrade completed successfully. Check the Confluence logs for any errors during the upgrade process.

**Check Installation Directory:**

Navigate to your Confluence installation directory and look for the confluence-version.properties file. Open it and confirm that the version mentioned matches 9.2.7.

**Restart Confluence:**

Restart the Confluence service to ensure that all changes take effect.

**Browser Incognito/Private Mode:**

Try accessing Confluence in incognito/private mode to rule out any cached data affecting the version display.

**Verify Application Information:**

In the Confluence administration console, go to "General Configuration" \> "Administration" \> "System Information." Check if the displayed version matches 9.2.7.

++***If, after performing these steps, you still encounter version display issues, it's advisable to reach out to Atlassian Support or consult the Atlassian Community for further assistance.***++


Tags: server
Is there a way to change the plan name using REST API?
Asked by leegyu86:

I would like to change the name of the plan created with clone.

Is there a way to set the PlanKey-BuildKey using REST API instead of clicking and changing it one by one?


Answers:
author: Shashank Kumar
body: Hello leegyu86,

Welcome to Atlassian community.

There is no REST API for renaming a plan. However, if you were to manage your plans using Bamboo Specs, plans can easily be renamed within the code and changes can be automatically detected. This makes rolling out bulk changes a little easier but requires some setup to migrate to this way of managing plans initially. This is the functionality that Bamboo has decided upon for allow for scaling out and automating changes to plans, rather than via REST. I've included documentation below about it if you are interested:

* [Bamboo Specs - Bamboo Server - Atlassian Documentation](https://confluence.atlassian.com/bamboo/bamboo-specs-894743906.html)

Regards,

Shashank Kumar

**\*\*please don't forget to Accept the answer if your query was answered\*\***
Problem deploying the docker job
Asked by ghalia sidi amemou:

hello,

The problem is when we run the plan manually in Bamboo, the build is successfully finalized, but when we run it scheduled, the build fails.

```
Error response from daemon: network with name m2mhubit_net already existsdocker: Error response from daemon: Conflict. The container name "/m2mhubit_redis" is already in use by container "5e8b04b118871c955bc11fe3991b63c08d873b409fa60b5a57b4cadcd9f0373e". You have to remove (or rename) that container to be able to reuse that name.See 'docker run --help'.docker: Error response from daemon: Conflict. The container name "/m2mhubit_m2mhub" is already in use by container "78b0a66e9aa8b2fe22af8faa3f9409b6736ef42f942f054df51c346497069080". You have to remove (or rename) that container to be able to reuse that name.See 'docker run --help'.Error while starting containers for integration tests
```

<br />

We have checked the trigger configuration, but we still have the same problem.


Answers:
author: Khushboo Gupta
body: Hello [@ghalia sidi amemou](/t5/user/viewprofilepage/user-id/5184672) ,

Welcome to Atlassian community.

The error message "response from daemon: network with name m2mhubit_net already exist" suggests that the build plan is trying to create a Docker network that already exists.

* Check the scripts in your build plan. If you have a command to create a Docker network, you could modify it to check if the network exists before trying to create it.
* Add a Cleanup Task: Add a task at the end of your build plan to remove the Docker network after the build is complete. This would ensure that the network doesn't exist when the next build starts.
* Or, you can add a script that will stop and remove the Docker container before starting a new one. Here's a sample script that you can use:  

  ```
  docker stop m2mhubit_redis || true && docker rm m2mhubit_redis || true
  ```

  This script will first try to stop the container. If the container is not currently running (which would cause the \`docker stop\` command to fail), it will ignore the error and proceed to the next command (\`docker rm\`). This will remove the container if it exists. If the container does not exist (which would cause the \`docker rm\` command to fail), it again ignores the error.

  You can add this script to the beginning of your build plan in Bamboo. This will ensure that any existing or running Docker container with the same name is removed before a new one is started, thereby avoiding the conflict error.

Let me know if this helps!

Regards,

Khushboo Gupta

**\*please don't forget to Accept the answer if your query was answered\*\***


Tags: docker
When can we create a SLSA provenance with bamboo
Asked by Emirhan Do?andemir:

Hi Team,

I wanna to ask when can we a slsa provenance with bamboo server. Software supply chain security practices is so critical for us but bamboo does not have any feature.


Answers:
author: Kian Stack Mumo Systems
body: [@Emirhan Do?andemir](/t5/user/viewprofilepage/user-id/5359825),

I'm not seeing any open issues in the Bamboo project related to this. Maybe you could raise a feature request?
How to disable automatic branch cleanup with bamboo yaml specs?
Asked by pBogey:

I have a plan where the branch settings are defined as:  

```
branches: &branch_settings
  create: for-new-branch
  delete:
    after-deleted-days: 3
    after-inactive-days: 90
  link-to-jira: true
```

And I want to override this for certain branches and disable the automatic cleanup. I have tried:  

```
branch-overrides:
  - ^(whatever.*)$:
      branches:
        << : *branch_settings
        delete: never
```

But this doesn't work.

From the UI I can uncheck a checkbox (Clean up plan branch automatically) in the specific plan branch configuration, but I don't know how to define it in the yaml spec and I didn't find it in the documentation.

![Untitled.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/290509i7C88EDED4AB5D8ED/image-size/large?v=v2&px=999 "Untitled.jpg")

Any suggestions? Thanks.


Answers:
author: Shashank Kumar
body: Hello pBogey,

Welcome to Atlassian community.

You can use the below examples to disable the expiry for branches using YAML specs

```
branch-overrides:  -    integration-branch:      branch-config:        disable-expiry: false  -    feature/.*:      branch-config:        disable-expiry: false
```

In this example I am overriding the branch properties for two branches one with a name of integration-branch and another any branch starting with the name of feature, you can probably modify this to meet your requirement.

**\*\*please don't forget to Accept the answer if your query was answered\*\***

Regards,

Shashank Kumar

comments: author: pBogey
body: That did the trick, thanks a lot. Seems it is documented as well, but I missed it.
Data Centre: Trying to get Docker Server and Agent talking to each other
Asked by Rafe G:

I'm trialing Bamboo Data Centre - intentionally doing it inside of docker so that I can do comparisons against other products.... However I'm struggling to get this running, wondering if anyone has any ideas.

I've tried this on several different hosts, ie I've changed the location of the server and the agent machines to different hosts with exactly the same results. Worth noting that I am running these on different hosts.

Following on from the instructions on

<https://hub.docker.com/r/atlassian/bamboo-agent-base>


Answers:
author: Eduardo Alvarenga
body: Hello [@Rafe G](/t5/user/viewprofilepage/user-id/4413482)

The error message is not really clear about what's going on with your system, but that's an indicator that the Agent can't communicate with the Bamboo server.

As the Atlassian Community is a public forum and the troubleshooting of this issue may expose personal information from your system, I recommend you raise a ticket with Atlassian at <https://support.atlassian.com/contact> so our team can help you with this matter privately.

Sincerely,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**
Failure at upgrade from 9.2.4 to 9.2.7 LTS
Asked by Patrick Zenner:

I want to upgrade our Bamboo Server from version 9.2.4 to 9.2.7. LTS but it stays on 9.2.4

I did the following steps:

- Copy .tar.gz to Server and unpack it with bamboo-user

- Backup /conf/server.xml

- stop Bamboo bamboo_9.2.4/bin/stop-bamboo.sh

- Backup /var/opt/bamboo/bamboo.cfg.xml

- DB Dump (Postgres)

- Edit bamboo-init.properties bamboo.home=/var/opt/bamboo

- Start Bamboo bamboo_9.2.7/bin/start-bamboo.sh

- Bamboo starts again but it shows 9.2.4

What am I doing wrong?


Answers:
author: brian_schrader
body: I am also having this issue. I am running Bamboo Server on Windows and there is only one instance of Bamboo running and the footer of the page still says 9.2.4. I have retried the upgrade several times and confirmed that the installer says 9.2.7.

What is going on?


author: Alexey Chystoprudov
body: Make sure previous Bamboo instance was stopped.

Check logs in $bamboo.home/logs

comments: author: brian_schrader
body: I do not believe this is the solution as I noted in my comment I see the same thing.
DB Query to get list of active plans
Asked by Rajat Roy:

I want to extract some data like list of active plans used in last 6 months . {#toc-hId--412535379}
---------------------------------------------------------------------------------------------------

Can you help me with a DB Query to get this details ? {#toc-hId-2074977454}
---------------------------------------------------------------------------


Answers:
author: Eduardo Alvarenga
body: Hello **Rajat**,

Try this KB article:

* [How to query the database for build plans that have not been run](https://confluence.atlassian.com/bamkb/how-to-query-the-database-for-build-plans-that-have-not-been-run-942853255.html)

Cheers,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**