youngmon/atlassian-qna huggingface dataset:
Cannot configure Artifact download task properly
Asked by Shy Aberman:

I am attempting to configure an Artifact Downloader task in a build plan in Bamboo Cloud. I have other plans with properly configured Artifact Downloader tasks, but I cannot see why my new plan is not working.

**Browser:** Google Chrome on Mac OSX

**Version:** 54.0.2840.71 (64-bit)

**Repro:**

1. Go to the Tasks tab of a stage configuration screen.
2. Either click on an existing Artifact Downloader task or add a new one. (Makes no difference.)
3. In the configuration screen, click in "Source plan" and start typing to find the desired source plan. Note that an error appears in the browser console. (See partial screenshot below.)
4. Mouse over one of the plans shown in the filtered list and click to select it. Note that an error appears in the browser console. Same error as the step above.

<br />

<br />

<br />

**Expected:** The plan should act like it was selected: The drop-down should disappear, the plan should appear in the "Source plan" input, and the "Artifact name" and "Destination path" inputs should appear.

**Actual:** The plan does not act like it is selected. The drop-down remains visible, and no plan on the list is selectable. Attempts to select produce more of the error message indicated above.

**Notes:**

* Directly typing the full plan name (ex: "Quill ? Quill - dev") into the "Source plan" input produces the same problems as above.
* The only way to select a source plan is: 1) Click on the "Source plan" drop-down to show a list of plans. 2) Select one of the shown plans. (Do NOT filter!) Of course, this requires that your desired source plan be visible in the drop-down without filtering.

**Screenshot:**

This shows the browser errors produced:  
image2016-11-9 18:45:24.png

[](https://community.atlassian.com/t5/Bamboo-questions/Cannot-configure-Artifact-download-task-properly/qaq-p/63143?attachment-id=10928){#link_11704b23b6259b}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/1978/1/image2016-11-9%2018%3A45%3A24.png){#display_11704b23b6259b_0}


Answers:
author: Alexey Chystoprudov
body: Hello, @Shy Aberman

Thank you for detailed description. Unfortunately it's known issue fixed in 5.14 - <https://jira.atlassian.com/browse/BAM-17173>

According to Bamboo Cloud EOL fix will not be deployed to Bamboo Cloud.

You can easily migrate your Cloud instance to Bamboo Server. If you don't want to manage hardware, it's possible to migrate to AWS - <https://confluence.atlassian.com/display/BAMBOO/Running+Bamboo+Server+in+AWS>


Tags: cloud
How to check if Build Trigger Condition is installed?
Asked by Josel Joaquin:

How can I verify if Build trigger condition is installed, following the documentation below;

<https://confluence.atlassian.com/bamboo/triggering-builds-289276897.html>

There should be a trigger condition for the version that we are using 5.94 however can't seem to find the options inside the plan configurations? Thank you.


Answers:
author: Alexey Chystoprudov
body: Open Bamboo UPM - \<BAMBOO_URL\>/plugins/servlet/upm/manage/all

Search to Condition world in browser

Check if plugin is running

Screen Shot 2016-11-10 at 11.37.11.png  
[](https://community.atlassian.com/t5/Bamboo-questions/How-to-check-if-Build-Trigger-Condition-is-installed/qaq-p/118664?attachment-id=8144){#link_11668f4bff2f1b}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/3759/1/Screen%20Shot%202016-11-10%20at%2011.37.11.png){#display_11668f4bff2f1b_0}

comments: author: Josel Joaquin
body: Thanks Alexey.
org.springframework.orm.hibernate4.HibernateSystemException: could not read a hi value - you need to populate the table: hibernate_unique_key; nested exception is org.hibernate.id.IdentifierGenerationException: could not read a hi value - you need to popu
Asked by TPanigrahi:


Answers:
author: Henry Zhang
body: Generally, this exception means that your database user lack some operation permission(eg. create table).

Please check the database user's permission on Bamboo db.
http://bambooserver
Asked by sourabh sharma:

**What should specifically be at place of "bambooserver" in <http://bambooserver>? Explain with some example.Thanks.**


Answers:
author: Jonas Andersson
body: The hostname of your machine, so if your corporate network is acme.inc, the machine-name could be bamboo.acme.inc, and if you enable SSL the address in the URL field would be <https://bamboo.acme.inc> but this depends on https forwarding (apache rewrite proxy or similar required)
SSIS Continuous Integration
Asked by Dennis Estrada:

Has anybody done continuous integration with SSIS and Bamboo. SSIS stands for SQL Server Integration Services. So, I would create a Project on Stash. From Stash, Bamboo gets the what it needs. Then, Bamboo deploys the Project to the SQL Server.


Answers:
author: Timothy
body: I don't think that there would be a plugin for Bamboo that would do that for you. You can of course automate it by writing your own scripts that will be triggered by the Bamboo agent.
Bamboo License Migration from one server to another server
Asked by Manas Dodya:

Hi,  

I have purchased license of Bamboo server for a machine A.  
I have another bamboo server running on different machine B with evaluation license.  

How can I migrate license of server A to server B and discontinue using paid license for server A ?  
Can I interchange License between machine A and B by changing respective server-id's ?  

Thanks,  
Manas Dodya


Answers:
author: Jim C.
body: Hi Manas,

There is no need to update the Server ID. The license was issued to a [my.atlassian.com account](https://my.atlassian.com/products/index), you can retrieve the license from there and enter it into machine B (see [Updating your Bamboo license details](https://confluence.atlassian.com/display/BAMBOO/Updating+your+Bamboo+license+details)). Once that's done and machine B is in production, you can decommission machine A.

Cheers,

Jim

comments: author: Manas Dodya
body: Hi Jim,  

Thanks for your reply. That is really helpful.  
But I have one issue, In my case, Machine A and Machine B are having license issued by different Atlassian accounts, that will cause an issue in migration, right ?  

We have installed Machine B server for redesigning production purpose, now since we are stable with the Machine B, we don't want to loose the existing plans from Machine B and we just wish to move license of Machine A to Machine B. Is that possible ?  

Thanks,  
Manas Dodya


author: Jim C.
body: Hi Manas,
> Machine A and Machine B are having license issued by different Atlassian accounts, that will cause an issue in migration, right ?

It doesn't matter, a license can be issued to one or more than one [my.atlassian.com account](https://my.atlassian.com/products/index). The license isn't tied to a single account nor a single Bamboo instance. So, you can enter the license in machine B without issue.


Tags: licence
How do I fix the Bamboo Jenkins importer error message "No resource was found for hudson.model.Messages"?
Asked by Peter Callies:

I zipped up a Jenkins project folder and I've trying to import it, but I get an error message "No resource was found for hudson.model.Messages". How do I work around this? What do I need to change?


Answers:
author: Peter Callies
body: We're using a newer version of Jenkins and we can't go backwards because we'll re-encounter issues that caused us to upgrade.

After re-reading the imported documentation, I see that it says to zip up the Jenkins home directory. I just zipped up one project sub-directory in the jobs directory. I can't even imagine zipping up a real, live Jenkins home directory with years of history and thinking that it will be under 50MB (even after making the recommended deletions) without doing as much editing and work as it would take to recreate the jobs by hand.

My takeaway from this is that Atlassian should remove the Jenkins importer if they're not going to make it ready for primetime. In it's current state, it's just a frustrating tease.


author: Marcin Gardias
body: You can try to edit your config.xml adding the following section

```
<hudson>
```

```
(...)
```

```
?<views>
```

```
??? <hudson.model.AllView>
```

```
????? <owner class="hudson" reference="../../.."/>
```

```
????? <name>All</name>
```

```
????? <filterExecutors>false</filterExecutors>
```

```
????? <filterQueue>false</filterQueue>
```

```
????? <properties class="hudson.model.View$PropertyList"/>
```

```
??? </hudson.model.AllView>
```

```
</views>
```

```
</hudson>
```


author: Pawel Skierczynski
body: First thing to do is to check Bamboo version and Jenkins version.

There is one specific Jenkins version that will work for each Bamboo. And most probably it will not be the newest one... (there is usually some JIRA issue to vote for requesting Bamboo Jenkins importer upgrade).

According to this <https://confluence.atlassian.com/display/BAMBOO/Importing+data+from+Jenkins> Bamboo 5.14 should work with Jenkins 1.581
How can you enable trusted keys if you re not using Bamboo Cloud or without Restricted Administrators ?
Asked by Nick Tkach:

p style color:#6f6f6f;border: 1px solid #e9e9e9;border-radius: 3px;padding: 5px; \> em\>This question is in reference to Atlassian Documentation: a href https://confluence.atlassian.com/pages/viewpage.action?pageId 826889392 \>How to suppress BambooTrustedKeyServerKeyVerifier unverified RSA key warnings in logs /a\> /em\> /p\> p\> span class text-placeholder \>Ask your question here... /span\> /p\>


Answers:
author: Nick Tkach
body: 100% of the checkboxes on that page are disabled. I would take a snapshot, but it doesn't show up. If you float over the checkbox for "Manage Trusted Keys" the cursor changes to a greyed out pointer with a little circle with a line through it. Also per <https://confluence.atlassian.com/bamboo/managing-trusted-keys-800714520.html> "Trusted keys management is available only for restricted administrators." Since the checkbox for "Enable Restricted Administrator Role" is on the same page and is also disabled, not sure this is even possible. I saw something talking about how "restricted administrator" role is only available for bamboo cloud, but I could have misread. We're talking about bamboo 5.10.3 specifically.

comments: author: Alexey Chystoprudov
body: There is **Edit** button on the bottom


author: Alexey Chystoprudov
body: Administration \> Security settings \> Manage trusted keys


Tags: key

trust
Can bamboo launch VM on Azure
Asked by Sylvain Gagne:

Hello, We actually use Azure cloud. Instead having fix build machines with dedicated agents, we would like to use azure and have bamboo build agent as a cloud. Is there similar functionality or plugin available as the plugin "Virtual Agents for Bamboo" provide ?

The scenario we are looking for is :

1) create and then turn off all our build images on Azure, install the bamboo build agent on them

2) Have Bamboo, starting the proper build environment when a build need it and use an agent licence

3) At the end of the build, close the build image and free the agent licence

Thanks,

Sylvain


Answers:
author: Greg P
body: [@Sylvain Gagne](/t5/user/viewprofilepage/user-id/604512) No answer here Sylvain sorry, but this is the first place in the whole internet (kidding) where I think I found someone had the same request as myself. And it has been almost a year. Have you found an azure solution to this? Or did you move to AWS? I tried to find a way to send you a message through here directly but without success.


author: Krystian Brazulewicz
body: @Sylvain Gagne Bamboo supports the scenario you have described but only for Amazon AWS. Azure cloud is not supported at the moment.

comments: author: Greg P
body: [@Krystian Brazulewicz](/t5/user/viewprofilepage/user-id/853277), I decided to do a search for what I am doing and replaced Azure with Amazon AWS for search options. We have servers both on Azure and on AWS (but my knowledge is more on the Azure side). But maybe you can answer some more questions I have with the AWS side of this.

1) Does it build remote servers with the agents residing on it through AWS? Or is it more like a service that exists in AWS cloudland?

2) If we have capabilities we need to use like node, MSTest, most commonly used capabilities, etc etc...we can specify this on AWS? I am assuming so, based on what I read, but until I jump into and learn more about AWS, I am not 100% sure.

3) I am assuming I can keep my main bamboo server on Azure? And in the adminstration on that server turn on access/configuration to AWS through that?

4) Any other Bamboo with AWS you can point me to to enlighten me?
Git repo url changes while running bamboo plan and fails
Asked by Syed Imran:

I have a bamboo plan configured for git repo as ([ssh://fnmst001@gerrit.app.xxx.com:29418/FNMS/anv-sdolt](ssh://fnmst001@gerrit.app.alcatel-lucent.com:29418/FNMS/anv-sdolt))

But when i run the bamboo plan, this is the error i get, Not sure why the repo url changes, can some one help

```
com.atlassian.bamboo.repository.RepositoryException: java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/local/git/bin/git ls-remote ssh://7753cca3-e062-48a6-8d03-567fa8cfd3b3@127.0.0.1:47408/FNMS/anv-sdolt failed with code 128. Working directory was [.]., stderr:[Host key verification failed., fatal: Could not read from remote repository., , Please make sure you have the correct access rights, and the repository exists.]
```


Answers:
author: Alexey Chystoprudov
body: Hello @Syed Imran,

It looks like you enabled Trusted keys verification feature <https://confluence.atlassian.com/display/BAMBOO/Managing+trusted+keys>

And your repository gerrit.app.xxx.com public key is not added to trusted keys list. It's the root of the error you see.

Regarding your question why Bamboo tries to connect another repo than you configured. Bamboo uses SSH proxy started locally to avoid storing your private SSH keys in file system at agent side. So agent makes checkout from proxy which forwards requests to real repository


Tags: bamboo-administration
Access to path denied..
Asked by Kapildev Gupta:

The topic was raised to Bamboo Support below is the reference

Reference: BSP-28674

<https://support.atlassian.com/servicedesk/customer/portal/10/BSP-28674>

please go through this and help

thanks

Kapil


Answers:
author: Jonas Andersson
body: We are the Atlassian user group, not Atlassian support.. And raising a case to get support on a case makes little sense.. Just escalate the open case you have?

comments: author: Nic Brough -Adaptavist-
body: Plus, we can't see support issues anyway, unless we're directly included in them.


author: Kapildev Gupta
body: Ok, Thanks anyways...

I have escalated the issue

kapil


Tags: team-foundation-studio
elastic bamboo uses public ip even for VPC
Asked by Sergey:

We're using local Bamboo server installation and trying to start elastic bamboo instances from original bamboo image.

We're using VPC, we've configured Elastic Bamboo to use VPC - nodes start as intended, in right subnets, this part goes fine.

But then they are stuck on '*Pending*' status. In node description I see its public name like 'ec2-\*-us-west-2.compute.amazonaws.com' and their public IP address.

If we connect to bamboo server and use tcpdump then we can see it trying to connect to that public IP.

The problem is that:

1. That's what we're using VPC for - our local bamboo server has no access to outer network (exception is made for http(s) requests via proxy).
2. Even on server itself dns resolves that 'ec2-\*-amazonaws.com' with local (VPC) IP. But bamboo prefers to get its Public IP from AWS API for some reason.

Is there any way to force bamboo server using VPC addresses to connect elastic agents instead of public ones?


Answers:
author: Paul Crockett
body: I am having the same issue. Elastic instances are connecting to the Bamboo server using the server's public IP, rather than the private IP.

I'm trying to restict incoming access for the Bamboo server to just the VPC subnet (and our office IP for SSH/HTTPS) but because the elastic agents connect via the public IP, this doesn't work as incoming address is the agent's public IP rather than its private IP.


author: Sergey
body: I've managed it out. I were creating elastic instances in VPC subnet, which allowed (and by default did) public ip addresses. So this was instances were created with Public IP, and Bamboo server were totally ignoring its 'Assign public IP' checkbox and tried to use that public ip just '*because it exists*'.

Now I moved elastic bamboo instances to fully private subnet and now server uses local ip to reach those nodes, because it has no choice =)

comments: author: Kai Paro
body: I'm running into the same issue -- are you implying that because the subnet has a route out to IGW that it will automatically assign a public IP address even though the subnet 'auto-assign public ip' setting is disabled?

Can you confirm that moving the elastic agents to a subnet with no IGW forced a private ip only instance?


author: Przemek Bruski
body: Check out Miscallenious section in Elastic Bamboo configuration, you should have an option  
"Allocate a public IP address to VPC instances"

comments: author: Sergey
body: This option changes nothing. Being enabled or disabled, elastic instances always get public ip (as mentioned in documentation- to be able to connect to s3 and other aws services), and bamboo server itself always uses public ip (and only public) to connect to these instances.

Even if local system itself resolves that public dns name with local (vpc) ip, bamboo tends to get public ip of the instance from aws api and use it, instead of dns resolved, or private one from api.

btw, we're using Bamboo 5.12.2.1 (will try updating soon, but I could not find anything related to such issues in release notes of recent versions).


Tags: bamboo-administration

elastic

elastic-agent

elastic-bamboo
How to checkout specific directories from git in Bamboo?
Asked by Thomas Hartwig:

Hi, I have created a checkout task from a git repo. This is working fine, however instead of checkout the whole repo I would like to checkout only specific subdirectories and run tests on these. How is this possible?


Answers:
author: Mark de Bont
body: Not supported out of the box by Bamboo, you would have to create custom scripts

comments: author: Thomas Hartwig
body: Hi Mark, thanks for the clear and fast answer. Is this by special purpose or just a lacking feature, is it possible to create a feature request on this?  

PS: We have a huge company repo. I know of many controversial discussions having one or multiple git repos. For this reason I am convinced it would be beneficial for Bamboo to be able to checkout subdirs only.


author: Peter Geshev
body: Hi Thomas,

Check out [this thread](http://stackoverflow.com/questions/600079/how-do-i-clone-a-subdirectory-only-of-a-git-repository/13738951#13738951)

Regards,

Peter
How to change default user permissions
Asked by Kulbhushan Mayer:

When I create a new plan in Bamboo, "Anonymous users" and "Logged in users" are always allowed to view the plan by the default permissions. Is there a way to change that?  
[](https://community.atlassian.com/t5/Bamboo-questions/How-to-change-default-user-permissions/qaq-p/414863?attachment-id=7077){#link_116690b43f7ec1}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/13054/1/Screen%20Shot%202016-11-02%20at%2016.32.22.png){#display_116690b43f7ec1_0}  
[](https://community.atlassian.com/t5/Bamboo-questions/How-to-change-default-user-permissions/qaq-p/414863?attachment-id=7078){#link_116690b43f7ec1_0}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/13054/2/image2016-11-2%2010%3A38%3A56.png){#display_116690b43f7ec1_2}  
[](https://community.atlassian.com/t5/Bamboo-questions/How-to-change-default-user-permissions/qaq-p/414863?attachment-id=7079){#link_116690b43f7ec1_1}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/13054/3/image2016-11-2%2010%3A40%3A27.png){#display_116690b43f7ec1_4}


Answers:
author: rsperafico
body: Hello [Kulbhushan Mayer](https://answers.atlassian.com/questions/users?username=557058%7C03078659-e85a-4013-85b1-7227e23269fd),

Thank you for your inquire. Please, find below an improvement request filed to address the issue in question:

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

Among the comments you will find the request you are looking for.

---

Kind regards,  
Rafael P. Sperafico


author: Alexey Chystoprudov
body: It's global configuration Administration \> Global permissions (BAMBOO_URL/admin/viewGlobalPermissions.action)

comments: author: Kulbhushan Mayer
body: We would like to have the ability where there will no default view permission to Logged in users and Anonymous users on any new plan created in bamboo.


author: Alexey Chystoprudov
body: So you can turn off these permissions on mentioned page


author: Kulbhushan Mayer
body: This will only turn of the permissions.. but these permissions are still available by default when someone create new plan.


author: Saarvaani Vadlamani
body: A setting which turns off the permissions to Logged in users and Anonymous users to view a newly created plan is requirement for us too.


author: Alexey Chystoprudov
body: I can't get the issue. See screenshot

Screen Shot 2016-11-02 at 16.32.22.png

In such configuration anonymous users can't access Bamboo at all


author: Saarvaani Vadlamani
body: We want the logged in users to view the plan to which they have permissions. Right now every newly created plan is viewable by all logged in and anonymous users because of the following default permissions. Is there any way to turn off these default permissions for logged in and anonymous users?

image2016-11-2 10:40:27.png


author: Kulbhushan Mayer
body: Yes, as shown by Saarvaani, we want this permission to be removed. instead of having them by default.


author: Kulbhushan Mayer
body: We are planning to give self service to users in Bamboo to create and manage their plan.. so early reply will be highly appreciable...


Tags: bamboo-administration