youngmon/atlassian-qna huggingface dataset:
SKUs / Product list
Asked by Frances James - ASM Technologies:

Would anyone be prepared to share the (as comprehensive as possible) Atlassian product listing, please? I know there aren't any SKUs per se but I mean, for example:

Product solution, cloud/server/DC, no. of users, price (USD) etc. (Price doesn't need to be on there, especially if it's out of date!)

I need to update/clean up the Atlassian SKUs / product list for our in-house system, from which our quotes are formed, orders confirmed \& invoices produced. I'm just looking to save time...Can anyone help please?

Thank you.

Fran


Answers:
author: Armin Meyer (Seibert - Coderay)
body: Hi there,

I am also looking for a product list of all Atlassian Products with their actual prices and product keys. Looking up prices on the website is far from convenient. There are so many price variants that it's just not possible to have a complete product list with prices in sync with the actual prices.

I am looking for an API Endpoint to get the product list similar to the available marketplace products. For Marketplace products one can use <https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-feedbacks-distribution-get>

Would be great if there was an API for atlassian products.

Cheers

Armin


author: Daniel Eads
body: Hi Frances,

We do have some pricing tables in our licensing FAQ that will speed things along for you. Here's links to the individual product FAQs (courtesy of the [Purchasing and Licensing FAQ](https://www.atlassian.com/licensing/purchase-licensing#pricinganddiscounts-1))

* [Atlassian Cloud](https://www.atlassian.com/licensing/cloud/ordering#overview-1)
* [Jira Core](https://www.atlassian.com/licensing/jira-core)
* [Jira Service Desk](https://www.atlassian.com/licensing/jira-service-desk)
* [Jira Software](https://www.atlassian.com/licensing/jira-software)
* [Portfolio for J](https://www.atlassian.com/licensing/jira-portfolio)[ira](http://www.atlassian.com/licensing/jira-portfolio)
* [Confluence](https://www.atlassian.com/licensing/confluence)
* [Team Calendars for Confluence](https://www.atlassian.com/licensing/team-calendars)
* [Bamboo](https://www.atlassian.com/licensing/bamboo)
* [Crucible](https://www.atlassian.com/licensing/crucible)
* [F](https://www.atlassian.com/licensing/fisheye)[isheye](http://www.atlassian.com/licensing/fisheye)
* [Bitbucket](https://www.atlassian.com/licensing/bitbucket-server)

On each one of those individual product pages, you'll find matrixes for the Cloud/Server pricing tiers.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/33204i34E2CF6A676631AA/image-dimensions/475x381?v=v2 "image.png")

*Example from the Bitbucket FAQ*

Hope that helps!

Cheers,  
Daniel

comments: author: Frances James - ASM Technologies
body: Thank you Daniel. If anyone were to have merged all these into one spreadsheet, that'd be gratefully received!
Can't get bamboo to checkout source code repository
Asked by Mark McWiggins:

I have bamboo configured and running on Ubuntu ... I'm just trying a simple test to get it to checkout a Git repository and run a script.

I can't get it to do the source code checkout even though the order looks right in the plan:

* Source code checkout
* Script

The error I get is "the working directory \<directoryPath\> must exist before executing the process" ... I know, but I can't get it to check out the source!

There must be something simple I'm missing; help please?


Answers:
author: Gerhard Forster
body: Hello,

when you installed Bamboo and created a build plan, you should automatically have a working directory. You could check this, for example, by adding a Scrip task to your build plan and put there:

```
echo ${bamboo.working.directory}
```

It should show something like: \~/*bamboo-agent-home/xml-data/build-dir/* \<*your* *JOB_KEY*\> The working directory is where code is checked out and worked with when the job runs.

If the above echo command shows a valid and the correct path for you, I'd assume that your Source Code Checkout task has something wrong in its configuration.

Otherwise, I can only imagine that you have defined *working.directory* as a global or a plan level variable - so it substitutes the Bamboo one.

Hope this helps.

Cheers, Gerhard
Writing Bamboo Plugin for Test Runners and Parsers
Asked by Ryan Strope:

I'm looking for someone to give me some guidance or point me to some good resources in creating Bamboo plugins that SPECIFICALLY target the Testing section of a Build Plan.

I can see looking through my Bamboo settings that the pre-packaged Plugins have modules for Test Runners, and Test Parsers e.g. NUnit, MSTest, VSTest etc so clearly there is a set of Standards, practices and algorithms for creating test runners and parsers just like there is for creating standard do some action modules as described in the many how to create a \[Insert Atlassian product here\] Plugin.

I've already played around and created a few standard plugins but I can't figure out what to do to make a plugin show up under the Testing selection of Build Plan The ultimate goal of course to have my unit and integration test results show up in the Test Results tab.

Little background on me

I'm primarily a C# Developer, and an intermediate to advanced PowerShell developer, but I can also hold my own in VBA, VBScript when necessary. I've done a lot of work in C, C++ but that was 10 plus years since i last seriously picked up those languages. As for Java I've only ever dabbled in it so i'm definitely in unfamiliar waters especially coming from a tightly integrated user friendly build environment like Visual Studio to how Java Builds are put together and managed (been playing with Eclipse to some measure of success i.e the plugins I had mentioned creating above)

So the question is where can I find out more about making my own test runners and parsers to use in my Bamboo Builds.

Thanks in advance for any help, advice or pointing me in the right direction


Answers:
author: Gonchik Tsymzhitov
body: Hi!

If you want to start write plugins (apps) -\> let's check this docs:

<https://developer.atlassian.com/server/bamboo/>

Also, you can review source code different plugins e.g.

<https://bitbucket.org/iuliushutuleac/bamboo-logparser-plugin>

About your use case, I am parsing generic logs into Junit report. Hence everything starting to universal.

Cheers,

Gonchik Tsymzhitov

comments: author: Ryan Strope
body: I've already been through the documentation on the community and as many places as i could find them including building a few of my own plugins what i can't find though is how to get the tasks parts of my plugins to go into the proper Task Type as shown below

![Bamboo Tasks.png](https://community.atlassian.com/t5/image/serverpage/image-id/33055i245B1AA749E51B56/image-size/large?v=v2&px=999 "Bamboo Tasks.png")I need them to show up here and there is nothing out there that clearly spells out what makes something a Builder, a Test parser or runner, source control, etc


author: Gonchik Tsymzhitov
body: Hi [@Ryan Strope](/t5/user/viewprofilepage/user-id/1937434)!

Please, put in your atlassian-plugin.xml

in taskType scope add this parameter:

```
<category name="test"/>?
```

Cheers,

Gonchik Tsymzhitov


Tags: app

test
commit and pushing code from a plan
Asked by Patrick Gibbons:

I work for Charles Schwab and I've run into an interesting issue. If I clone via the git command line, checkout the development branch, touch a file, add the file, commit the file and then do 'git push -u', I see the change in bitbucket on the development branch after doing a pull from another machine cloned with the development branch, both at work and on the web. If I clone via a plan in bamboo by selecting a clone task, and then try that same sequence above from a second task in the plan, from my home edition of bamboo here, git complains with the error:

"21-Sep-2018 13:38:38 Since Git 2.0, Git defaults to the more conservative 'simple'  
21-Sep-2018 13:38:38 behavior, which only pushes the current branch to the corresponding  
21-Sep-2018 13:38:38 remote branch that 'git pull' uses to update the current branch.  
21-Sep-2018 13:38:38  
21-Sep-2018 13:38:38 See 'git help config' and search for 'push.default' for further information.  
21-Sep-2018 13:38:38 (the 'simple' mode was introduced in Git 1.7.11. Use the similar mode  
21-Sep-2018 13:38:38 'current' instead of 'simple' if you sometimes use older versions of Git)  
21-Sep-2018 13:38:38  
21-Sep-2018 13:38:38 remote: error: refusing to update checked out branch: refs/heads/master  
21-Sep-2018 13:38:38 remote: error: By default, updating the current branch in a non-bare repository  
21-Sep-2018 13:38:38 remote: error: is denied, because it will make the index and work tree inconsistent  
21-Sep-2018 13:38:38 remote: error: with what you pushed, and will require 'git reset --hard' to match

if I do the same push sequence using bamboo from a task at work, however, the change appears in the log to work:

development -\> development

but if I do the pull from another machine thereafter, no change pulls down. Maybe I'm taking the wrong approach here, but I want to trigger a job that pushes directly to development to update the R package version whenever the development branch moves down via a PR. I was attempting to add my private rsa key to bamboo, but I'm getting a host-key error that the bitbucket cloud endpoint is not trusted, not sure how to make bamboo trust the cert of bitbucket in the cloud. My goal was to clone via a bash script using the command line, from the cloud, and try a push that way to investigate whether it's something with the way the clone is being created via bamboo's custom task. Can you please advise? Sorry for being so long winded.


Answers:
author: Patrick Gibbons
body: If I run the following sequence from a bash shell, test.sh, I get the expected results:

#!/bin/bash  
git config push.default matching  
git branch -a  
git branch --track development origin/development  
git checkout development  
git branch -a  
cd test  
ls  
touch sample123.txt  
git add sample123.txt  
git commit -m "add sample 123"  
git push -u

If I add the above sequence to a script within a bamboo script, however, the log appears to show a successful outcome, but the file never gets pushed, please advise
Trouble after install BamBoo in Amazon Linux AMI
Asked by thaolt8:

![image.png](/t5/image/serverpage/image-id/32970i57D603217E8457AA/image-dimensions/842x311?v=v2 "image.png")


Answers:
author: Foong
body: Is this a new Bamboo installation or it is configured to use existing Bamboo database?

If new Bamboo installation, delete the database and Bamboo Home to reinstall Bamboo again.

If want to connect to old Bamboo database, copy the entire Bamboo Home from old Bamboo instance to this server and then configure Bamboo to use this copied Bamboo Home.
Can I pass multi customRevision on "/queue rest api"?
Asked by JongBum Lee:

Dear All

My Bamboo plan has more than one SVN Repository.

Is it possible to pass the customRevision value per repository to the "/queue rest api"?

? "/queue rest api" specification has only one customRevision.

Help me..

Best Regards


Answers:
author: Gerhard Forster
body: Hi, I found this Atlassian Cummunity post: \[<https://community.atlassian.com/t5/Bamboo-questions/Is-there-a-way-to-specify-a-revision-number-to-update-to-when-a/qaq-p/380844>\].

It provides this as a solution (example revision number 63781):

```
curl -X POST  http://{bambooBaseURL}/ajax/runParametrisedManualBuild.action?os_authType=basic&amp;planKey=MYCHANGSETBUILD&amp;customRevision=63781
```

You may give it a try. Hope it makes the trick for you!

Cheers, Gerhard

comments: author: JongBum Lee
body: Thank you for your kind reply.

My problem is that one plan has more than one REPO and I want to pass the REVISION for each REPO through the "/ QUEUE REST API".

a plan - a1 repo

- a2 repo

- a3 repo

I want set a1, a2, a3 customRevision.

Is it possible in the way you told me?


author: Gerhard Forster
body: I don't believe it'll work like that, but just for one SVN repo.

I found another Atlassian Community post that comes up with another idea which I give more chance to work as you need it. Base is to not utilize a Bamboo "Source Checkout Task" but instead a "Script Task" to retrieve SVN sources.

From there you might do the below, 3 times, for repo a1, a2 and a3 respectively:

```
targetRevisionX=${bamboo.repository.revision.number}
svn co repoUrl -r $targetRevisionX
```

You'd need to think about thing like authentication of your repoUrl that you get automatically by use of the "Source Checkout Task", just as a heads up.

The Community article is here: <https://community.atlassian.com/t5/Bamboo-questions/Is-there-a-way-to-specify-a-revision-number-to-update-to-when-a/qaq-p/380844>

Hope this helps you better!


author: Gerhard Forster
body: Sorry, same post, but further down. Too close to weekend ;-)
Is there a way to get bamboo build reports to include data about plan branch buils
Asked by David_Mills:

The Bamboo Build Activity report only presents data about the default branch. Is there a way to get it to include plan branches as well?


Answers:
author: Gerhard Forster
body: Hello,

from Bamboo UI there seems to be no chance doing this. Its options are outlined here: <https://confluence.atlassian.com/bamboo/reporting-289276962.html>

However, Bamboo's REST API should offer a way, namely this:

**/rest/api/latest/plan.json?expand=plans.plan.branches.branch.latestResult**

The *branch.latestResult* node contains the build results for every branch of the plan (except for master), which means you can use this call to get branch results and then use **/rest/api/lastest/result.json** for the master branch build results.

Hope this gets you further.

Cheers, Gerhard

comments: author: Ed Cardinal
body: Thanks, this was incredibly helpful. I took over an older system where no one used the master branch - only development, go figure :) and needed to know when the last builds occurred for each branch to see which were active and which were abandoned. I still need to post-process but this is a great start.
Bamboo gets stuck 'Loading...' and 'Searching...'
Asked by CTL ENG Tools:

Bamboo is getting stuck 'Loading...' the Requirements for the default job of plans and 'Searching...' for users and groups on the Global permissions page. The workaround has been to restart Bamboo, but this is not a long-term solution so I would like to know if there is another alternative long-term solution to this problem. If there is, can you please share? Thank you!![ETC-280-2.png](/t5/image/serverpage/image-id/32879i22AE0A789510532E/image-size/large?v=v2&px=999 "ETC-280-2.png")![ETC-280-1.png](/t5/image/serverpage/image-id/32878iEA22999AC84C9632/image-size/large?v=v2&px=999 "ETC-280-1.png")


Answers:
author: Gerhard Forster
body: Impossible to conclude anything here without having more data!

If this occurred more than once, it's best to open a Bamboo support ticket and directly attach your Bamboo Support Zip to it, capturing this incident.

It likely contains error messages in the logs allowing troubleshooting your issue.

Thanks, Gerhard
where do gradle repo gets created in bamboo instance?
Asked by poovaivadivelan:

I want to replace few jars with customized ones in gradle repo, after i complete build with gralde. I am not able to find out where .gradle folder will be created in Bamboo instance.


Answers:
author: Gonchik Tsymzhitov
body: Hi!

Generally, It will create in your bamboo plan working directory.

But you use variables for flexible managing it

Cheers,

Gonchik Tsymzhitov


Tags: gradle
Bamboo inline powershell encoding broken
Asked by Thomas:

Hello,

After upgrading from 6.1 to 6.6 execution of inline PowerShell scripts seems to have had their encoding broken.

The system encoding was Cp1252 and this was the encoding of the PowerShell interpreter. However the encoding of the resulting script file from the Bamboo inline script appears to be in UTF-8 and as such the execution of the script will result in failure.

I've tried to change the system encoding (according to: <https://confluence.atlassian.com/bamboo/configuring-your-system-properties-289277345.html>) but this did not solve the problem described.

I've checked the bamboo database (\`Microsoft SQL Server 2014 - 12.0.2000.8 (X64) Feb 20 2014 20:04:26 Copyright (c) Microsoft Corporation Express Edition (64-bit) on Windows NT 6.3 \<X64\> (Build 9600: ) (Hypervisor)\`) where the majority of the tables and columns seems to have \` collation_name = Finnish_Swedish_CS_AS\` which seems fine to me.

If possible I guess I would like to force same encoding for interpreter and script file.

Thankful for any advice.

Thomas


Answers:
author: Thomas
body: No answer was found, we migrated our inline scripts to files where we could specify encoding.


Tags: encoding

inline

ms-sql

powershell

utf
Bamboo spec commits and build number
Asked by Kavi Manohar:

I have a bitbucket repo where I store 5 different plans under bamboo-specs folder and everytime I change something on plan1 java code and commit it, the bamboo builder number gets increased for all the build plans with the label 'Specs Configuration Updated'

Is there a way not to increase the build number?


Answers:
author: Gerhard Forster
body: Actually no. **If you run a build, your build number gets automatically increased.** Even if a run build with a number lower than current is deleted, this number would not be used for any following build - I played this locally.

++Basically I see two options to change build numbers, which are++:

1. Add an **offset to higher build numbers** (please see this Atlassian Community link: [Can I edit the Bamboo build number?](https://community.atlassian.com/t5/Bamboo-questions/Can-I-edit-the-Bamboo-build-number/qaq-p/219743)).
2. **Reset build number per plan** by cloning the plan in question (please find details in the following KB: [Unable to change the current build number in Bamboo](https://confluence.atlassian.com/bamkb/unable-to-change-the-current-build-number-in-bamboo-759858218.html), section "Workaround")

Cheers, Gerhard
(Newb question) Does Bamboo some type of "Script Console" to mange/maintain large number of builds?
Asked by Landon Cooper:

I need to manage over 200 builds and would like to use some central scripting tool to custom query maintenance issues. Any information you can provide would be greatly appreciated!


Answers:
author: Gerhard Forster
body: I'd suggest use of Bamboo Java Specs for your purpose.

Find attached the following documents for familiarizing you with this topic:

* Example for Bamboo Java Specs containing great extra links - <https://confluence.atlassian.com/bamboo/tutorial-create-a-simple-plan-with-bamboo-java-specs-894743911.html>
* Bamboo Java (and YAML) Specs Reference showing all it offers - <https://docs.atlassian.com/bamboo-specs-docs/6.6.3/>

Should be a great starting-point for you. Hope this helps.

Cheers, Gerhard
How to queue deployment jobs for multiple environments at once
Asked by Vincent Deschenes:

Hi,

Our application is single tenant. This lead to many application server instances as every client has its own.

We have one bamboo "Environment" per application server instance.

These are regrouped under "Deployment projects".

How can we ask Bamboo to deploy a given release to all the environments of a "Deployment Project" without having to click each of them one by one ?

I am not asking how to run multiple jobs in parallel, I know the answer is more agents.

What I want is to "queue" all the jobs with one click.

I was looking for a deploy button at the deployment project level but can not find it.

Thanks !


Answers:
author: Marcin Gardias
body: You can workaround this problem using "After successful deployment" trigger:

- create a dummy environment, named for example 'All servers', make it do nothing (for instance single script task with nothing but 'exit 0' in it)

- add After successful deployment trigger to all other environments and point to 'All servers' environment

Now whenever you deploy 'All servers', all the other environments will be triggered.

BTW: if you manage a big number of deployment environments perhaps you should consider using Bamboo Specs.

comments: author: Vincent Deschenes
body: Thanks, I did not knew about Bamboo Specs.

A limitation of the trigger solution is that it does not allow to select the release, it will create a release from the last built.

But this could work in most cases.

Thanks!


author: Marcin Gardias
body: \>A limitation of the trigger solution is that it does not allow to select the release, it will create a release from the last built.

Actually, no, in case of this trigger, he same release that was deployed to 'parent' env is deployed to 'child' env. So you would create release once, when deploying the dummy environment and the it should propagate to all envs.


author: Vincent Deschenes
body: OK thanks,

it is this text in the trigger form which confused me:

> Set triggers to specify how and when the deployment will be triggered automatically. When a deployment is automatically triggered, a new release is created from the latest successful build result of the linked plan.


author: Jaya kumar
body: [@Marcin Gardias](/t5/user/viewprofilepage/user-id/781649) So this setup will run environment parallel or sequentially ?


author: Marcin Gardias
body: Depends on number of available agents, but, in principle, it will be parallel.


author: Jaya kumar
body: [@Marcin Gardias](/t5/user/viewprofilepage/user-id/781649) Is there possible to run sequentially? If so, please share the details.


Tags: bulk-edit

deployment

multiple
Convert Build Definitions into Bamboo Build Plans
Asked by Volodymyr Havryliuk:

Hello, community. Is there any tool or way to convert TFS 2010 build definitions to Bamboo build plans? Thank you in advance.


Answers:
author: Gerhard Forster
body: Hi Volodymyr,

I googled around for you and found the WEB page below that is not match the exact TFS version, but sketches a possibly good idea - <https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/visual-studio-build?view=vsts>

**Apparenty you can export a MSBuild definition to YAML format.**

How this combines with Bamboo? **Bamboo supports Specs describing plan configuration in YAML** leading to have corresponding plans created or updated automatically within Bamboo.

Please find our Bamboo YAML Specs Reference here: <https://docs.atlassian.com/bamboo-specs-docs/6.6.3/specs-yaml.html#introduction>

In the this document, you'll find **"MSBuild" as *Executable capabilies*defining external programs which can be called from out of Bamboo YAML Specs** .

Please note that Bamboo YAML Specs offer just a subset of the capabilities provided by Bamboo's Java Specs. Please refer to the above reference document to figure out if YAML Specs for Bamboo offers enough for your build plans.

Hope this helps.

Cheers, Gerhard


Tags: bamboo-administration

developer