youngmon/atlassian-qna huggingface dataset:
Does bamboo agent support simultaneous/parallel builds?
Asked by deepthi bhat:

My objective is to build multiple plans using a single remote agent at the same time. At present, build gets queued until the previous build using is completed, to run the next build. Does bamboo support this kind of parallel builds as is available in jenkins slave?


Answers:
author: rsperafico
body: Hello [@deepthi bhat](/t5/user/viewprofilepage/user-id/1174171),

Remote agents do not run multiple jobs at the same time, even if you enable concurrent builds. The feature my colleague mentioned ([Configuring concurrent builds](https://confluence.atlassian.com/bamboo/configuring-concurrent-builds-289277193.html "Configuring concurrent builds")) enables you to run the same Job in multiple agents, instead.

Kind regards,

Rafael

comments: author: DiMarco
body: Is this purely to ensure users have to pay more for additional remote agents or is there a technical reason concurrent builds are not supported?


author: Kari Harju
body: Need an answer to this as well.

Setting up and maintaining agents that only build one plan at a time makes no sense.   
I have a 5 agent system setup with some serious power on each to get quick feedback build running as fast as possible and for this at least 4 plans / agent is simply a must-have feature.


author: robhit
body: Hi Deepthi,

How about using Bamboo Concurrent Build Feature?

\* <https://confluence.atlassian.com/bamboo/configuring-concurrent-builds-289277193.html>

Thanks!

comments: author: DiMarco
body: I find this answer troubling. The user is clearly implying multiple plans concurrently building on the same agent. Your link has nothing to do with his question aside from the work concurrent. It only works for the same plan on different remote agents, as Rafael stated below.  

Please take the time to read the question before posting a reply on behalf of Atlassian.


Tags: build

concurrent

remote-agent
Bitbucket app password login fails
Asked by Erik Dahl:

Hi,

I have just set up bamboo on our server behind a apache http reverse proxy.

Everything is set up as atlassian tutorials shows.

Now it works, except i cannot connect to bitbucket cloud git repository.

I get the exact error outlined in this post:

<https://confluence.atlassian.com/bamkb/failed-to-load-data-from-bitbucket-403-forbidden-attempting-to-create-a-bitbucket-cloud-repository-in-bamboo-fails-869183268.html>

I have done exactly as suggested in that page. And my server.xml file is exactly as it should be. But still the same error.

How to proceed?


Answers:
author: Edwin Kyalangalilwa
body: Hi Erik,

You may be missing the Bitbucket SSL cert in your Bamboo JVM. Try the SSLPoke on this page and see whether it can connect successfully.

<https://confluence.atlassian.com/kb/unable-to-connect-to-ssl-services-due-to-pkix-path-building-failed-779355358.html>

comments: author: Erik Dahl
body: Thanks for your suggestion. However this is not the problem. SSLPok is successful:

$JAVA_HOME/bin/java SSLPoke bitbucket.org 443

Successfully connected
How to return back to original Server ID?
Asked by Unal Koksal:

Hi,

I have installed Bamboo Starter License on my own Windows 2012 Server. During the configuration it asked for a license key and I generated one by copying Server ID and pasting into my.atlassian.com license generation page.

Then I tried to import exported .zip file from my customer's Bamboo to get existing builds and deployments imported into my Bamboo, because we want to start managing websites on our own.

After I successfully import .zip file, my Bamboo's Server ID changed to the one which is actively working on its own server. There is no license problem or something. Builds and deployments are showing properly.

The problem is, when I try to link my Bamboo with Bitbucket Server hosted by my customer, as my customer's Bamboo is already linked with Bitbucket, I cannot link my new Bamboo with Bitbucket because I'm getting Server ID duplicate error inside Bitbucket.

What should I do? How can I return back to my originally generated Server ID which I used to generate my own license?

So that I will link my Bamboo with that Bitbucket Server.

Note: I have found [this](https://community.atlassian.com/t5/Bamboo-questions/Need-steps-to-generate-new-Server-ID-for-an-existing-Bamboo/qaq-p/229973) while searching, which I think it can be helpful for me but I don't remember or know what is my original Server ID.

Thanks in advance.


Answers:
author: robhit
body: Hi Unal,

As mentioned on the link shared by you, how about installing a new Bamboo Version (completely separately) then once the Bamboo starts up, copy the server id from the \<bamboo-home-dir\>/bamboo.cfg.xml file and replacing the same from the required Bamboo bamboo.cfg.xml file.
Using Json Parser.Build result is not coming properly.
Asked by bhagatrsumit:

Using Json Parser.Build result is not coming properly.i am getting this error.**Failed to parse test result file**


Answers:
author: Daniel Santos
body: Hey Sumit, can you give us more details about this problem? What task are you using to parse your tests? How your report is generated?  

If this is Junit parser, please check this link: [JUnit Parser task in Bamboo shows 'Failed to parse test result file' error when parsing test results file](https://confluence.atlassian.com/jirakb/junit-parser-task-in-bamboo-shows-failed-to-parse-test-result-file-error-when-parsing-test-results-file-800701931.html)
Setting Bamboo build expiry without affecting artifacts for deployment projects
Asked by Simon Boland:

I have numerous build plans (around 25). A small number of these are configured with deployment projects.

If I expire the build artifacts will it mean that I can potentially lose the artifacts which were saved for the releases in the deployment plans?

Is there a way I can avoid this? The only way I can think to do this is by applying a label.


Answers:
author: Simon Boland
body: I discover Bamboo deployments keeps these so it's not an issue. I just didn't see it mentioned in the documentation.


Tags: expiration
Setting Bamboo build expiry without affecting artifacts for deployment projects
Asked by Simon Boland:

I have numerous build plans (around 25). A small number of these are configured with deployment projects.

If I expire the build artifacts will it mean that I can potentially lose the artifacts which were saved for the releases in the deployment plans?

Is there a way I can avoid this? The only way I can think to do this is by applying a label.


Answers:
author: robhit
body: Hi Simon,

> If I expire the build artifacts will it mean that I can potentially lose the artifacts which were saved for the releases in the deployment plans?

As far as the loss of build artifacts are concerned the calculation is based on:
> The ages of build and deployment artifacts are calculated as follows:
>
> * If there is no release associated with the build result, then use the build result creation date.
> * Otherwise, if the build result has never been deployed, then use the creation date for the latest release that refers to it.
> * Otherwise, use the creation date for the latest deployment.
>
> If the age of the build or deployment artifact is equal to or greater than the **Expire after** age, then it is deleted when the expiry event occurs (assuming artifacts are configured for deletion).

> Is there a way I can avoid this? The only way I can think to do this is by applying a label.  

Yes, you are right the only option is using Labels.


Tags: build

deployment

expiration
Elastic Bamboo Error :EC2 Instance failed to start: EC2 instance order for image ami-ab5277ce failed
Asked by Chitti:

Unable to start new elastic instance, showing error as mentioned below:

***Elastic Bamboo Error :* EC2 Instance failed to start: EC2 instance order for image ami-35527750 failed.**   
**(com.amazonaws.services.ec2.model.AmazonEC2Exception : The requested configuration is currently not supported. Please check the documentation for supported configurations. (Service: AmazonEC2; Status Code: 400; Error Code: Unsupported; Request ID: 2d26ab25-fc18-47c9-8390-0e4b9fb59988))**

Created Instance in AWS and running.

Can anyone help on this.


Answers:
author: Jeyanthan I
body: It sounds like that particular AMI is not supported by a Spot instance request. The Amazon documentation on supported instances for spot looks pretty limited but from what I can find, Windows Server with SQL Server isn't able to be used with spot:  

<https://aws.amazon.com/ec2/faqs/#Which_Operating_Systems_are_available_as_Spot_Instances>

Is this particular AMI a Windows Server with SQL Server image? If you go to your **AWS console \> EC2 \> Spot instances \> Request spot instance** is **ami-**35527750**** available for selection?  

If this is the case, there is a possibility that Bamboo keeps trying to start this spot instance instead of failing and moving to the on-demand instance. There is an open improvement request for this. Please follow and upvote it.

* [BAM-18348 Bamboo will continuously attempt to run a spot instance even if Amazon reports that spot is unsupported for that AMI](https://jira.atlassian.com/browse/BAM-18348)


Tags: elastic-bamboo
Clover is open source yet license required for bamboo
Asked by Doron Horwitz:

When enabling Clover in Bamboo you are required to enter a license. But there is no way to get a license now that its open source.

What's the solution? (I'm running bamboo v6.2.5)

![clover.png](/t5/image/serverpage/image-id/11570i8A461B2D82AD9BCF/image-size/large?v=v2&px=999 "clover.png")


Answers:
author: Ellie Z _they_them_
body: Hi [@Doron Horwitz](/t5/user/viewprofilepage/user-id/14730)

Thanks for reaching out to us!

From the Screenshot, it looks like you've selected "Automatically integrate Clover into this build." in the Miscellaneous tab of the Job configuration. The text box there is available for users who purchased Clover licenses before it became open source, as their licenses are still valid.

The other option in the Miscellaneous job config is "Clover is already integrated into this build and a clover.xml file will be produced." With this option selected, please add Clover into your pom.xml for Maven to read ([Clover-for-Maven: Basic usage](https://confluence.atlassian.com/clover/basic-usage-588579892.html)), or build.xml for Ant ([Clover-for-Ant: Quickstart guide](https://confluence.atlassian.com/clover/1-quickstart-guide-71599501.html)) -- the license portions no longer apply.

For Maven, you can add the following Goals to your command (or Maven task):

    clover:setup 
    clover:aggregate 
    clover:clover

For Ant, you can use the following arguments when calling Ant -- and/or in your Ant task:

    with.clover
    clover.xml

I hope this helps. Please don't hesitate to reach out if you have any further questions!

Thanks,

Elias

Developer Tools Support \| Atlassian


author: Doron Horwitz
body: Thanks [@Ellie Z _they_them_](/t5/user/viewprofilepage/user-id/50795), very helpful.

The warning message need to be updated then, explaining what you've just explained to me.

Is there any ticket open to fix that message?

comments: author: Ellie Z _they_them_
body: Hi [@Doron Horwitz](/t5/user/viewprofilepage/user-id/14730)

I have just filed two requests:

* [\[BAM-19591\] - Update Clover integration documentation](https://jira.atlassian.com/browse/BAM-19591)
* [\[BAM-19592\] - Update Clover license warning message](https://jira.atlassian.com/browse/BAM-19592)

Please feel free to vote, comment, and watch both of these issues.

If there is anything else we can assist with, please do not hesitate to reach out!

Thanks,

Elias


Tags: clover
How to integrate testing scheme with bamboo
Asked by Aleksandra Maslennikova:

Hello,

There is a task to implement a multilateral verification of the software product, before downloading it to the master, for further deployment on the server. About the project:  
1. Technologies: Asp.net MVC 4 + React + Sass;  
2. Bundler: Webpack;  
3. Version control system: Git;  
4. Used products: Jira, Bitbacket, Bamboo, SmartGit;

It is required to perform a software test, on the server side, within two events: Push and Pull Request. Checks inside the events must be consistent, and be able to cancel the event at any stage, with the developer notifying of the error.

During the first event, all checks are performed on the server side, using a preconfigured webpack. It assembles and connects all the necessary modules for testing.

During the second event, part of the checks is on the server side, and the other part with human control.

The general scheme of the required implementation is indicated by the attached image. How to implement this idea, what products and extensions will be needed for this?![photo_2017-12-25_14-06-59.jpg](/t5/image/serverpage/image-id/11565iAA67AF397A3A5C46/image-size/large?v=v2&px=999 "photo_2017-12-25_14-06-59.jpg")


Answers:
author: Gonchik Tsymzhitov
body: Hi!

I hope the latest version 6.8.0 will cover your request

<https://confluence.atlassian.com/bamboo/bamboo-releases-671089224.html>

Also, please, have a look  
<https://marketplace.atlassian.com/apps/1215235/fail-build-trigger-for-bamboo>

And this one as well

[https://marketplace.atlassian.com/apps/1211303/workzone-pullrequest-workflow?hosting=datacenter\&tab=overview](https://marketplace.atlassian.com/apps/1211303/workzone-pullrequest-workflow?hosting=datacenter&tab=overview)

Cheers,

Gonchik Tsymzhitov
How to change the REST API URI
Asked by qiming:

We have an instance running Bamboo 6.3 in port 8085.

And a reverse proxy engine proxy the my.domain.com to localhost:8085.

When we try to link Applications with Jira, it runs failed.

Also, when we try to install add-ons, it runs failed too.

The root cause is base URI for automation URL is locahost:8085 instead of my.domain.com .

If we try to request the rest resources, the all in localhost.

May I know that there is any way to change the Host for these?

PS: It works before we upgrade to 6.3 from 5.x.

\<resources expand="resources"\>\<link href="http://localhost:8085/rest/api/latest/" rel="self"/\>\<resources start-index="0" max-result="12" size="12"\>\<resource name="info"\>\<link href="http://localhost:8085/rest/api/latest/info" rel="self"/\>\</resource\>\<resource name="project"\>\<link href="http://localhost:8085/rest/api/latest/project" rel="self"/\>\</resource\>\<resource name="plan"\>\<link href="http://localhost:8085/rest/api/latest/plan" rel="self"/\>\</resource\>\<resource name="result"\>\<link href="http://localhost:8085/rest/api/latest/result" rel="self"/\>\</resource\>\<resource name="chart"\>\<link href="http://localhost:8085/rest/api/latest/chart" rel="self"/\>\</resource\>\<resource name="queue"\>\<link href="http://localhost:8085/rest/api/latest/queue" rel="self"/\>\</resource\>\<resource name="export"\>\<link href="http://localhost:8085/rest/api/latest/export" rel="self"/\>\</resource\>\<resource name="clone"\>\<link href="http://localhost:8085/rest/api/latest/clone" rel="self"/\>\</resource\>\<resource name="dependency"\>\<link href="http://localhost:8085/rest/api/latest/dependency" rel="self"/\>\</resource\>\<resource name="elasticConfiguration"\>\<link href="http://localhost:8085/rest/api/latest/elasticConfiguration" rel="self"/\>\</resource\>\<resource name="reindex"\>\<link href="http://localhost:8085/rest/api/latest/reindex" rel="self"/\>\</resource\>\<resource name="currentUser"\>\<link href="http://localhost:8085/rest/api/latest/currentUser" rel="self"/\>\</resource\>\</resources\>\</resources\>


Answers:
author: Lars Olav Velle
body: You are not looking for how to change the REST API URI. Wanting a specific solution often gives the wrong answer.

Instead a heading like "Cannot install add-ons" or similar would make people more eager to help you out.

I think the root cause here is that you have not configured bamboo to be aware that it is running behind a reverse proxy:

<https://confluence.atlassian.com/bamkb/running-bamboo-behind-apache-httpd-proxy-171967281.html>

-Lars
What is the RSS repository ?
Asked by GxP Regist:

There is unknown word appeared in [Bamboo 6.3 release notes.](https://confluence.atlassian.com/bamboo/bamboo-6-3-release-notes-941616828.html)

> Bamboo 6.3 adds new permission controls for linked repositories. User is now
>
> able to choose what RSS repository can use a given repository or grant all
>
> repositories access for RSS repository.

<br />

Can anyone explain about "RSS repository" ?


Answers:
author: Jeyanthan I
body: RSS is Repository Stored Specs. You can now configure your build plan by coding in Java using [Bamboo Specs](https://confluence.atlassian.com/bamboo/bamboo-specs-894743906.html). This Bamboo Specs can now be stored in a Bitbucket repository and this repository is referred as [RSS repository](https://confluence.atlassian.com/bamboo/tutorial-bamboo-specs-stored-in-bitbucket-server-938641946.html).

Hope that clarifies.

comments: author: GxP Regist
body: I was completely convinced. Thank you very much.
Update Plan repository branches via API?
Asked by jmooo:

Since you [can't update Plan variables via the API](https://jira.atlassian.com/browse/BAM-18266) is it possible to use the API to update the Plan repository branches that were [introduced with Bamboo 6.3](https://confluence.atlassian.com/bamboo/bamboo-6-3-release-notes-941616828.html)?


Answers:
author: Branden McElveen
body: Hi,

At this time the [Bamboo 6.3 REST API](https://docs.atlassian.com/atlassian-bamboo/REST/6.3.0) docs are not available yet and I have not seen anything internally discussing the API changes for 6.3. I would suspect the docs should be coming in the next couple days but you can also put in a [JAC](https://jira.atlassian.com/secure/BrowseProjects.jspa?selectedCategory=all&selectedProjectType=all) ticket for updated API documentation.

Cheers,

Branden


Tags: api
Bamboo Deploy plan without build source
Asked by Kus@123:

We are trying to utilize Bamboo for deployment automation, although we are not quite ready for build automation yet. It will take long to get build dependencies resolved, over a year or so.

So I am wondering, if its possible to automate only deployment process. So that we can automate and integrate that with Jira. I see source build is a mandatory field for deploy plan, is there is any workaround to skip build plan? or can I create a dummy build plan?


Answers:
author: robhit
body: Hi Kus,

The basic workflow of CI/CD is you use your Build Plans to build your code, artifacts and then you use your Deployment Plans to deploy the artifacts/release to the target environment - UAT/PROD/DET, etc.

According to your requirement here, if you do not have the build plans then how and what you will supply to the deployment plans to deploy?

And since there will be no or dummy build plan for the deployment plan the release notes will also be useless as it will contain none or useless details in it which will be irrelevant to the deployed release.

Probably you can explain more about the requirement so that I can understand well if I am missing any point here.

Thanks!

comments: author: Sergey
body: Have you ever heard about "12 factors app"? Release = a build + configuration. Thus to be able to deploy a new release based on the same build, you need to have the build of an app defined in a separate repo from the one which defines deployment. And currently you need to make a "dummy" build plan just to create a deployment plan.  

Repo A:

* sources of an app
* build definition

Repo B:

* dummy build definition (actually just pins a version of an app to be deployed)
* Deployment definition

With languages like python which do not require precompilation "build" is even more meaningless.
Deploy to Artifactory
Asked by IT ADVITOS:

**Problem:**

Bamboo deploy task does not work.

**My current config:**

1. Bamboo-Server:
   1. Reverse proxy via IIS
2. Artifactory-Server:
   1. Reverse proxy via IIS; rewrite URL: [http://localhost:8081/{R**:**1}](http://localhost:8081/%7bR:1%7d)
   2. Artifactory custom base URL: [https://artifactory.mycompany.com/artifactory](https://artifactory.hepawash.com/artifactory)

**Analysis:**

1. Artifactory is reachable -\> RevProxy works
2. Bamboo-Plugin configured with [https://artifactory.myconpany.com/artifactory](https://artifactory.hepawash.com/artifactory) -\> Deploy task configurable
3. Bamboo deploy task ends up in an error ("The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.")
4. curl -uadmin:password -k -T c:/t.txt "[https://artifactory.mycompany.com/artifactory/example-repo-local/t.txt](https://artifactory.hepawash.com/artifactory/example-repo-local/t.txt)"
   1. **is working**, but I have to disable SSH via --k
   2. otherwise "curl: (60) SSL certificate problem: unable to get local issuer certificate" occurs

Please help me solve this problem. Might it be a SSL issue?

Jfrog says:

"The SSL Certificate needs to be added to the cURL client. You should be able to find the certificate as it was installed in the IIS in order to configure SSL connection to Artifactory."

-\> How do I do that exactly?

Thanks for your help.


Answers:
author: somethingblue
body: Hi Rainer,

* If you take a look in the Bamboo logs what error(s) do you see when you reproduce the issue?

There appears to be a known issue that you can find at [Artifactory Generic Deploy task is failing when Bamboo is running an SSL prox](https://www.jfrog.com/jira/browse/BAP-334)y.

Please review the ticket and the comment let us know if that helps.

Cheers,

Branden
Will bamboo offer notifications to be sent to stride?
Asked by Jules:

Hi there,

Currently we use Hipchat and we have set up our Bamboo instance (Hosted locally) to send notifications to the different rooms we have set up.

We are soon to be moving to Stride but one possible blocker could be that we don't have the ability to send notifications from bamboo to Stride like we did have when we used Hipchat.

Is this going to be included in an update of Bamboo? or is there some other way we can configure Stride so we can have notifications sent from our Bamboo server?

![Bamboo_to_hipchat_notification.png](/t5/image/serverpage/image-id/11398i8872E0FF6AC2A299/image-size/large?v=v2&px=999 "Bamboo_to_hipchat_notification.png")


Answers:
author: Edwin Kyalangalilwa
body: Hi Julian,

Yes, Stride will replace Hipchat once its released. So you'll be able to send the same notifications as you did with Hipchat.

comments: author: Grzegorz Lewandowski
body: It's not true. Stride and HipChat are different systems and Bamboo needs dedicated support to send notifications to Stride.

It's not implemented yet. [Here's](https://jira.atlassian.com/browse/BAM-18729) a JIRA feature request to add such support.


author: Jules
body: Thanks Grzegorz, it's a shame this feature is not ready at launch as my team find it very useful to have these notifications sent to HipChat.

We might now have to stick with HipChat.

Julian