youngmon/atlassian-qna huggingface dataset:
Create plugin for Bamboo version 7.1.3 instead of default 6.8.0
Asked by castus:

How I create a plugin for Bamboo version 7.1.3 instead of default 6.8.0?

When I run \`atlas-create-bamboo-plugin\` it says \`using stable product version: 6.8.0\`. My company's Bamboo is 7.1.3 and I want to develop my plugin for that version.

I changed pom.xml and plugin.iml file but with no result. When I run \`atlas-run\` I see Bamboo 6.8.0 on localhost.

Please help


Answers:
author: Gonchik Tsymzhitov
body: So did you changed to the \<bamboo.version\>7.1.0\</bamboo.version\> in pom.xml?

Then you can run with next parameters

```
atlas-run --product bamboo  --version 7.1.3
```

comments: author: castus
body: Yes, my pom looks like this

```
<properties>
    <bamboo.version>7.1.3</bamboo.version>
    <bamboo.data.version>7.1.3</bamboo.data.version>
    <amps.version>8.0.2</amps.version>
    <plugin.testrunner.version>2.0.1</plugin.testrunner.version>
    <atlassian.spring.scanner.version>1.2.13</atlassian.spring.scanner.version>
    <!-- This property ensures consistency between the key in atlassian-plugin.xml and the OSGi bundle's key. -->
    <atlassian.plugin.key>${project.groupId}.${project.artifactId}</atlassian.plugin.key>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
</properties>
```

I used also

```
atlas-run --product bamboo  --version 7.1.3
```

but still, my Bamboo runs in 6.8.0, look at the screenshot

![Firefox_2021-01-08 10-04-23@2x.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/124650iBDFAA742B8F98616/image-dimensions/354x232?v=v2 "Firefox_2021-01-08 10-04-23@2x.jpg")

Is this a bug?


author: castus
body: Solved: I needed to run \`atlas-clean\` because something was cached.


author: Gonchik Tsymzhitov
body: Excellent


Tags: bamboo-development

development
Remote events not pushed from Bitbucket to Bamboo
Asked by Maciej Zientarski:

I am trying to link Bamboo and Bitbucket in order to get Bamboo react on pull requests.

I have:

* Bitbucket 6.10.0 self-hosted
* Bamboo 6.10.6 self-hosted

I am checking the "System information" page in Bamboo to see if I receive any events from Bitbucket. Even though "Remote events status=working" "Last received event" column remains empty. I am trying to trigger some event by creating and editing pull requests.

Observations:

* I can see Bitbucket is periodically querying GET /rest/remote-event-consumer/1/capabilities of Bamboo
* Bamboo returns capabilities like "stash-pullrequest-opened-remote-event" or "stash-pullrequest-updated-remote-event"

What could be missing? Why does Bamboo not receive any events? I have re-established the links between the applications. Nothing has changed.


Answers:
author: Gonchik Tsymzhitov
body: Hi!

Could you verify 2 place please?

1. SSL configuration on tomcat side

* <https://confluence.atlassian.com/bamboo/securing-bamboo-with-tomcat-using-ssl-391087422.html>
* <https://confluence.atlassian.com/kb/securing-your-atlassian-applications-with-apache-using-ssl-838284349.html>

2. Base URL and confguration on revers proxy if you have.

<https://jira.atlassian.com/browse/BAM-17579>


author: Maciej Zientarski
body: OK. I have some more info:

The Bamboo endpoint GET /rest/capabilities returns several links. My Bamboo is hosted with SSL and all the links have https prefix. This is OK.

However the endpoint GET /rest/remote-event-consumer/1/capabilities returns all links with http. This makes Bitbucket complain:

```
java.lang.IllegalArgumentException: Request url 'http://bamboo.my.org/rest/remote-event-consumer/latest/events/stash-branch-changed-remote-event' isn't in the same origin as the rpc url 'https://bamboo.my.org'
```

Any Idea how to fix the URLs in the GET /rest/remote-event-consumer/1/capabilities response?


Tags: bitbucket-server

event

pull-request
using dotnet 3.1 on task script
Asked by Gerardo Cornejo:

Install dotnet 3.1 sdk on bamboo server, but when using command in script task it doesn't recognize it.

Your help please!!!!


Answers:
author: Gerardo Cornejo
body: Sorry, the problem was the user with whom I installed the dotnet, it is different from bamboo.

comments: author: Gonchik Tsymzhitov
body: Thanks for feedback
Ability to add specific notifications on Plan Branch Failure?
Asked by Benjamin Caffrey:

Hi all,

Feels like this should be a common use case - we have a Bamboo build plan for one of our repositories. Currently, we have a notification that all failures will alert a Slack channel we own.

I want to differentiate failures on certain significant git branches (for instance, develop or master). These branches should result in additional or different Slack notifications.

Unfortunately, it seems that I'm unable to do this. Here is the screen I currently see:

![d986dde3-2e7a-4883-ac6c-0ad34a2af851.png](/t5/image/serverpage/image-id/124364iD7FA73FC37A838A0/image-size/large?v=v2&px=999 "d986dde3-2e7a-4883-ac6c-0ad34a2af851.png")


Answers:
author: Gonchik Tsymzhitov
body: Hi [@Benjamin Caffrey](/t5/user/viewprofilepage/user-id/4213201) !

This is one possible way to notify

<https://confluence.atlassian.com/bamkb/using-slack-for-bamboo-notifications-940217744.html>
Reuse same yaml specs in multiple repositories
Asked by cmanzur:

Hi, I'm using Atlassian Bamboo 7.1.1.  
I'm creating pipelines as a code using YAML.  
I have one git repository with a YAML specs to reuse in multiples pipelines. Let's call this repo: **common-specs**   
Then, I have a repository per microservice.

My idea is to have one **bamboo-specs/bamboo.ym**\` in each microservice repo like this:

```
# Microservice 1 repository:

---
version: 2
# ...
Build job: !include 'common/build-job.yml'
```

Where **build-job.yml** file comes from the **common-specs** repo.

So, I tried using git submodules (in each microservice repo) but I can't make it work.

I create a Linked repository and then I a **Specs Scan** and bamboo show:

```
Cloning into /path/to/submodules ...
Permission denied (publickey)
fatal: could note read from remote repository
```

When bamboo tries to clone the git submodule.

Notes:  
- I'm using bamboo "linked repositories" using native GIT with my SSH shared credentials (created by me before).  
- I enabled submodules.  
- The SSH key is the right one! I can clone it on my local.  
- Just in case: I also put the same SSH key (**id_rsa** ) on the bamboo "Agent" and modified the **\~/.ssh/config** to use it.

I think the problem is that bamboo is not running this SCAN on the agent. It's running in the bamboo server. Am I alright? In that case, why is not bamboo able to clone the submodule? I'm using the same credentials in the repository and in the submodule.


Answers:
author: Gonchik Tsymzhitov
body: Hi [@cmanzur](/t5/user/viewprofilepage/user-id/4210006) ,

will it help if you add task script to git pull the sub module ?

Looks like that workaround will meet your requirements


Tags: spec

yaml
Is Bamboo going away? IF so, When?
Asked by kerry borden:

Read an end-of life article saying server/on prem applications will no longer be developed in Q1 2021 with an EOL in 2024. Since Bamboo is on-prem only, is this product being retired?


Answers:
author: Daniel Ebers
body: Hi [@kerry borden](/t5/user/viewprofilepage/user-id/626213)

just to be precise on wording.  

Bamboo ("Bamboo Server as you know it today") will go away as all Server products will be End Of Life as of February 2024.

This does \*not\* mean Bamboo itself (speaking of its functionality that it was created for) will go away. It will have a "replacement" - Bamboo Data Center.

Watching the roadmap will surely give more information as time passes by.  
[https://www.atlassian.com/roadmap/data-center?product=bamboo\&](https://www.atlassian.com/roadmap/data-center?product=bamboo&)

Cheers,  
Daniel


author: Edwin Kyalangalilwa
body: Yes, in favor of Bamboo Data Center ([Data Center Roadmap](https://www.atlassian.com/roadmap/data-center)) and [Bitbucket pipelines](https://bitbucket.org/product/features/pipelines). All server applications are being retired.

comments: author: yogesh_devi
body: Can [Bitbucket pipelines](https://bitbucket.org/product/features/pipelines). be used with on-premise bitbucket Datacenter ?


author: Daniel Ebers
body: Hi [@yogesh_devi](/t5/user/viewprofilepage/user-id/737128)

no - there was a Suggestion with Atlassian - but it was closed some time ago:

* **Bitbucket Pipelines for Bitbucket Server**   
  <https://jira.atlassian.com/browse/BSERV-9245>

The recommendation of Atlassian to use in an on-premise setup is Bamboo.

<br />

Regards,  
Daniel
Difference between build duration and processing_duration
Asked by Charlie Misonne:

The Bamboo database has a table called **buildresultsummary** listing all build executions.

There are 2 columns related to build duration but I'm not sure of their actual meaning:

* duration
* processing_duration

I assume both are in milliseconds.

processing_duration seems to be the value that Bamboo shows on the user interface as *duration*but I'm not sure.

Sometimes duration is greater than processing_duration but it can also be the other way around.

My purpose is to find out how many hours my agents have been building in the past year.  
Which value should I use? Or should I take the sum of both?

Here are the queries I currenlty have:

```
select sum(processing_duration) from buildresultsummary
where build_date >= '01-01-20'
and build_date < '01-01-21'
and build_type = 'CHAIN'
order by build_date desc;
```

```
select sum(duration) from buildresultsummary
where build_date >= '01-01-20'
and build_date < '01-01-21'
and build_type = 'CHAIN'
order by build_date desc;
```


Answers:
author: Alessandro Lombardo
body: Hi , pay attention to this bug about the calculation of duration

<https://jira.atlassian.com/browse/BAM-21817>

Vote it please because i think that could affect also your actual work


author: Alessandro Lombardo
body: [@Charlie Misonne](/t5/user/viewprofilepage/user-id/502263)

If you do a query at CHAIN level, I think that to know how long your agents were busy building, you may use the **processing_duration** field, that is the net time the agent were busy+job queue, because if in your plan you have some JOBS to trigger manually, **duration** field considers also the time you get to trigger manually that job.

You should sum all duration or processing duration but with build_type= BUILD, so you don't count the queue time. You can connect buildresultsummary to agents with

**join** queue q **on** q.queue_id = buildresultsummary.build_agent_id

and aggregate on Agent level

Cheers,

Alessandro


author: Jeyanthan I
body: Further to our discussion internally, just to close the loop,
> processing_duration seems to be the value that Bamboo shows on the user interface as *duration* but I'm not sure.

You are right. *processing_duration* column is the one you see in the build result summary page in Bamboo UI.
> My purpose is to find out how many hours my agents have been building in the past year.  
> Which value should I use? Or should I take the sum of both?

If you want to know how long your agents were busy building, you may use the **duration** field.

* The **duration** is the total time jobs within the stage took to complete.
* The **processingDuration** is the total job execution time + time spent in queue.

  When a build is scheduled, it first gets into a build queue and then gets assigned to an available agent, thus it can take some time between build scheduling and the actual build.

Hope that helps.

Cheers,  
Jey
Bamboo Deploy : SSH Task fails with errors
Asked by Praveen Racharla:

Hi All,

I am trying to execute a shell script on my remote server using Bamboo SSH Task but it's getting errors as below :

SSH task :

#!/bin/bash

cd testdir/  
./testscript.sh input1

Above command executes fine if I manually run them by logging into remote machine.

|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
| 05-Jan-2021 13:29:15 | ./testscript.sh: line 165: sqlplus: command not found                                                                                              |
| 05-Jan-2021 13:29:15 | head: cannot open \`/tmp/tmp.RfYpQS6fq8/servers-test.txt' for reading: No such file or directory                                                   |
| 05-Jan-2021 13:29:15 | tail: cannot open \`/tmp/tmp.RfYpQS6fq8/servers-test.txt' for reading: No such file or directory                                                   |
| 05-Jan-2021 13:29:15 | cat: /tmp/tmp.RfYpQS6fq8/system-test.txt: No such file or directory                                                                                |
| 05-Jan-2021 13:29:15 | cat: /tmp/tmp.RfYpQS6fq8/core-test.txt: No such file or directory                                                                                  |
| 05-Jan-2021 13:29:15 | cat: cat: /tmp/tmp.RfYpQS6fq8/standalone-test.txt/tmp/tmp.RfYpQS6fq8/standalone_web-test.txt: No such file or directory: No such file or directory |
| 05-Jan-2021 13:29:15 |                                                                                                                                                    |
| 05-Jan-2021 13:29:15 | cat: /tmp/tmp.RfYpQS6fq8/resourcegen-test.txt: No such file or directory                                                                           |
| 05-Jan-2021 13:29:15 | cat: /tmp/tmp.RfYpQS6fq8/resourcegen_web-test.txt: No such file or directory                                                                       |


Answers:
author: Praveen Racharla
body: It's resolve , the problem was environment variables not getting loaded with SSH task, so externally mentioned.

source \~/.bash_profile
Bamboo deployment fails with message" Unable to download artifact "
Asked by yogesh_devi:

Hello experts,

I am running Atlassian Bamboo ( version 7.1.1 build 70117 - 23 Jul 20) .

I created a deployment plan to deploy artifacts on our release server.

When I run my deployment plan I get an error as follows

31-Dec-2020 09:50:17 Finished task 'Clean working directory task' with result: Success  
31-Dec-2020 09:50:17 Starting task 'Download release contents' of type 'com.atlassian.bamboo.plugins.bamboo-artifact-downloader-plugin:artifactdownloadertask'  
31-Dec-2020 09:50:17 Preparing to download plan result UCA-YOG-515 artifact: Non required shared artifact: \[Debian Packages\], pattern: \[\*.deb\] anchored at: \[uca-core/debian_packages\]  
31-Dec-2020 09:50:17 Unable to download artifact Non required shared artifact: \[Debian Packages\], pattern: \[\*.deb\] anchored at: \[my-project/debian_packages\]  
31-Dec-2020 09:50:17 Task configuration:  
31-Dec-2020 09:50:17 artifactName_0 -\> \[Debian Packages\]  
31-Dec-2020 09:50:17 artifactId_0 -\> \[XXXXX\]  
31-Dec-2020 09:50:17 sourcePlanKey -\> \[MY-PLAN\]  
31-Dec-2020 09:50:17 localPath_0 -\> \[\]  
31-Dec-2020 09:50:17 Task runtime configuration:  
31-Dec-2020 09:50:17 runtimeArtifactIds_0 -\> \[0\]  
31-Dec-2020 09:50:17 artifactName_0 -\> \[Debian Packages\]  
31-Dec-2020 09:50:17 artifactId_0 -\> \[XXXXX\]  
31-Dec-2020 09:50:17 resultKey -\> \[MY-PLAN-515\]  
31-Dec-2020 09:50:17 artifactLocation_0 -\> \[my-projec/debian_packages\]  
31-Dec-2020 09:50:17 localPath_0 -\> \[\]  
31-Dec-2020 09:50:17 artifactPattern_0 -\> \[\*.deb\]  
31-Dec-2020 09:50:17 Finished task 'Download release contents' with result: Error

On my Bamboo build plan I see that "Duplicate Entries" exist for the artifact "Debian Packages" in the build result, I see two rows - first one grayed out and another one that is a valid - I wonder if that is the reason for this failure - I posted a separate question for that issue


Answers:
author: Gonchik Tsymzhitov
body: Hi!

as I see it's duplicate of

<https://community.atlassian.com/t5/Bamboo-questions/Bamboo-Duplicate-entries-for-produced-artifacts/qaq-p/1567472#M29569>
Bamboo Duplicate entries for produced artifacts
Asked by yogesh_devi:

Hello,

I recently migrated [Atlassian Bamboo](http://www.atlassian.com/software/bamboo/) (version 7.1.1 build 70117 - 23 Jul 20 ) to a new server . We now see that in all our build plans - the shared artifacts have two entries in Bamboo.

One entry is grayed onether is a valid hyperlink to the artifacts.

I checked in the directory on Bamboo server that is denoted as "artifact location" which is "/var/atlassian/bamboo/artifacts/plan-136085508/shared/build-00512/" . I see that there is a single set of artifacts actually generated.

I tried deleting and recreating the artifacts by editing build plan but this problem does not go away .

And addition to incorrect display another unwanted fallout of this seems to be that my Bamboo Deployment plan is failing with following message

"Unable to download artifact Non required shared artifact: \[Debian Packages\], pattern: \[\*.deb\] anchored at: \[uca-core/debian_packages\]"

Does anyone knows how to deal with this ? Your suggestions are welcome

Please let me know if I need to provide any additional input

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

See attached picture


Answers:
author: yogesh_devi
body: This problem was finally resolved ( or should I call worked around :-) ) with help from [@ijeyanthan](/t5/user/viewprofilepage/user-id/577222) of Atlassian support . In Bamboo settings go to Artifact Handlers page ( the Cogwheel --\> Overview --\> Artifact Handlers ) . In the "Artifact Handlers" page there are checkboxes for making choices relating to artifact handlers . Among these the checkboxes for "Agent Local Handlers" were checked in my set-up (for both shared and non shared artifacts) . This choice was causing a duplicate line with a dead hyperlink for every artifact. Unchecking the "Agent local artifact handler" check-boxes fixed the problem for me.

So to me it seems like there could be a problem in "Agent local artifact handler" functionality - but I don't care much about the artifact handlers being agent local and am happy with not using them to get rid of the duplicate entries .

![BambooArtifactSettings.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/124918i71674A705AB35B9E/image-dimensions/480x194?v=v2 "BambooArtifactSettings.jpg")


author: Gonchik Tsymzhitov
body: Hi!

I have the same situation.

Planning to upgrade to latest and see

<https://confluence.atlassian.com/bamboo/bamboo-7-2-release-notes-1026526751.html>

One interesting point,it's affected only for old artifacts to me. how about you?

<https://jira.atlassian.com/browse/BAM-18489>

comments: author: yogesh_devi
body: Hi [@Gonchik Tsymzhitov](/t5/user/viewprofilepage/user-id/726117) thanks for your comment. In my case this problem affects the freshly generated artifacts as well.

Do keep me posted if upgrade fixes it on your setup; so I may attempt an upgrade on my set-up as well
How to delete Bamboo environment from deployment project?
Asked by James Brown:

I would like to automate the deletion of environments from Bamboo Deployment projects.  
Is it possible to do this through the rest api?


Answers:
author: Soumyadeep Mandal
body: Hi [@James Brown](/t5/user/viewprofilepage/user-id/721095) ,

Please read \& follow this documentation <https://docs.atlassian.com/atlassian-bamboo/REST/5.13.1/>
I can't connect bitbucket linked repositories
Asked by ???-A:

hi atlassian Community

504 gateway time out error occurs when connecting linked repositories of bitbucket from bamboo. The bamboo and bitbucket are located behind the ALB on the AWS.   

What kind of permission should I give?  
thanks for your help.

![??? 4.png](https://community.atlassian.com/t5/image/serverpage/image-id/123653i9F69D1583813A909/image-dimensions/416x207?v=v2 "??? 4.png")


Answers:
author: Soumyadeep Mandal
body: Hi [@???-A](/t5/user/viewprofilepage/user-id/3910732) ,

Please read and follow these documentations <https://docs.aws.amazon.com/dtconsole/latest/userguide/connections-create-bitbucket.html>

<https://forums.aws.amazon.com/thread.jspa?messageID=917334>

comments: author: ???-A
body: thanks your answer. :\> but it is a different matter.  
My problem was caused by the bamboo server version. not cloud ver.

504 issue has been resolved, but the above problem still occurs.  
thank you.
Connection to authentication server failed on Crowd 2.7
Asked by Timothy Klim:

After fresh crowd install I got "Connection to authentication server failed. Please review the logs for more information. " and this output <https://gist.github.com/TimothyKlim/f3087c012d02552de06f>

I'm trying to run crowd on Solaris with Oracle JRE 7.


Answers:
author: Zul NS _Atlassian_
body: Are you pointing Crowd to an existing Crowd Home directory? How did you get the error? During installation? While accessing from the application that integrated with Crowd?


Tags: crowd-administration
Crowd CSV import File Location Linux
Asked by Christopher Anderlik:

Hi.

I am trying to import Users in crowd 2.2.2 with CSV-import.

This is documentation for it:

<https://confluence.atlassian.com/display/CROWD/Importing+Users+from+CSV+Files>

File-Location:

The CSV files must be on the local drive (e.g. C:) of the Crowd server.

But it is not possible for me to locate the user file on a Linux-Server!

I gave full permissions to the files. I tried absolute and relative path. Buth crowd cannot find the files.

What am I doing wrong??

![](../../upfiles/Window-3.jpg)  


Answers:
author: joe
body: \> What am I doing wrong??

You have an extra space at the end of the filename, shown betwen the final 'v' and the end quotation mark. Delete it and try again.


author: Christopher Anderlik
body: OMG - this is really painful.

I am soo sorry - you are right - thank you very much!

I tried 20 different ways but was not able to see the blank at the end......

THANK YOU for opening eyes ;-)


Tags: csv

import
Migrated Crowd from PROD to Dev server, Dev apps secondary admin auth goes to PROD crowd
Asked by Tom:

Weird problem here -- back in the spring, I migrated my PROD Crowd to a Dev server and pointed my Dev apps to the Dev Crowd. All worked except for secondary admin auth, which I worked around in Dev Confluence (see [https://answers.atlassian.com/questions/168573/cannot-authenticate-to-crowd-as-administrator-in-confluence?page=1](/questions/168573/cannot-authenticate-to-crowd-as-administrator-in-confluence?page=1)). Same thing happens with Dev Jira now, and I discovered that in the PROD Crowd catalina.out file whenever I tried to get into Dev Jira administration (for example, to re-index), when I got to the secondary authorization, I get "Client with address "10.10.21.60" \[my Dev Jira box\] is forbidden from making requests to the application, {2}" message (and in my Dev Jira browser, I get the "Oops!" page with stack trace. So somewhere my Dev Jira (and Confluence) are pointing back at PROD Crowd. I'm guessing there is something amiss with the DEV Crowd config. Ideas?


Answers:
author: BernardoA
body: As Andrew explaine before you can cchekc and add your DEv Jira IP Address going to Application tab \> select the directory \> Remote Addresses.


author: Andrew_Sheedy
body: Have you added your DEV Jira to the list of allowed remote addresses in your DEV Crowd for the application?


Tags: crowd-administration