youngmon/atlassian-qna huggingface dataset:
Butler: Updating sub-task due dates
Asked by karen:

I've figured out how to create subtasks and link cards to view dependencies. But, I'm not able to figure out how to update all dates for linked cards as shown in this video: <https://www.youtube.com/watch?v=SM5eMd7KuOI>


Answers:
author: Theodoro Reato
body: Hey Karen,

This rule can be set with the automation:
> when a due date is moved in a card, for each card linked from an item in checklist "Checklist", move the due date by the same amount of time

Go to the Automation panel, Rule tab, and click on Add (plus sign), the trigger is on the Due date tab, then the first action is on the Content Tab, and to finish the last command is on the Due date tab. Don't forget to save it! :D Als, pay attention to the Checklist name you added, it needs to match with the checklist (on the video example Sub-tasks)


Tags: dependency
My ATLASSIAN account was deactivated and received emails from Atlassian asking for my IDs
Asked by DG:

super suspicious!!


Answers:
author: Brant Schroeder
body: [@DG](/t5/user/viewprofilepage/user-id/5165428) Welcome to the Atlassian Community

Do not respond this is phishing. Atlassian would not ask for something that they already have.

comments: author: DG
body: Thanks Brant! I thought it could be phishing but my Atlassian account did get deactivated overnight not sure why


author: Brant Schroeder
body: [@DG](/t5/user/viewprofilepage/user-id/5165428) Hmm maybe they saw funny activity on the account. You can always contact support and see if the email was legit. I have never heard of anything like that but if it was just redirecting you to the Atlassian website then maybe it was from them. <https://support.atlassian.com/contact/>


Tags: jira
How can you tell bamboo that a release was manually deployed to an environment
Asked by David_Mills:

Hi, with our database, when a database build is complete, it can be deployed to a Database instance (environment). This takes 4-6 hours. Once a Database instance has been deployed to, we can take a backup and restore this to other Database instances. How can we tell bamboo that these instances now contain the same release - given that bamboo was not involved in getting them there?  

Or do we have to create an alternative "deployment" plan that does the restore alternative?


Answers:
author: David_Mills
body: We found a way - disable the script that actually does the deploy, then run. It "succeeds" and registers the environment as having the release.


Tags: bamboo-administration
Bamboozled Ruby Plugin - Ruby Environment dropdown EMPTY
Asked by Craig Solinski:

How do I get a value in the 'Ruby Environment' dropdown for  
Version:  
5.0.5  
Vendor:  
[AlienFast](http://www.alienfast.com/)  
Add-on key:  
com.alienfast.bamboozled.ruby.bamboozled-ruby-plugin?  
.  
I have RVM and RUBY installed on my Bamboo Server already.  
\[esitstj@esappj77 \~\]$ which ruby  
/opt/bamboo/rvm/rubies/ruby-2.0.0-p598/bin/ruby  
\[esitstj@esappj77 \~\]$ which rvm  
/opt/bamboo/rvm/bin/rvm  
\[esitstj@esappj77 \~\]$ ruby --version  
ruby 2.0.0p598 (2014-11-13 revision 48408) \[x86_64-linux\]  
\[esitstj@esappj77 \~\]$ rvm --version  
rvm 1.26.9 (latest) by Wayne E. Seguin \<wayneeseguin@[gmail.com](http://gmail.com)\>, Michal Papis \<mpapis@[gmail.com](http://gmail.com)\> \[<https://rvm.io/>\]  
.  
It appears all ENV vars and appropriate Paths have been set by command:  

```
source /opt/bamboo/rvm/scripts/rvm
```

Thank you,

Craig


Answers:
author: Craig Solinski
body: RESOLVED:

For Linux running Bamboo app:

Created sym link from user that runs bamboo in home dir:

ln -s /opt/bamboo/rvm .rvm

Then on Server Capabilities in Bamboo click Detect Server Capabilities.

Results are seen in log.


Tags: addon-com.alienfast.bamboozled.ruby.bamboozled
Multiple AWS accounts with Elastic Bamboo
Asked by Thomas Bui:

Is it possible to configure multiple AWS accounts (access key pairs) with a single Elastic Bamboo subscription?

Under *Bamboo administration \> ELASTIC BAMBOO \> Configuration* you are asked to enter access key pair. Our organisation maintains separate AWS subscriptions, as such multiple keys are required. Is it possible to administer all subscriptions under a single Eastic Bamboo subscription?

Thanks,

Thomas


Answers:
author: Steffen Opel _Utoolity_
body: Unfortunately the resp. feature request is still unresolved as of today:

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

Given the low activity and number of votes, I wouldn't expect it to be implemented anytime soon.


Tags: account-management

aws

elastic-bamboo
Can't build dockerfile in bamboo build
Asked by Wellington Silva:

I have made a script task to run during a build and it should build and start some docker containers based on dockerfiles but it gives me the following error:

```
Building proxy...Couldn't connect to Docker daemon at http+unix://var/run/docker.sock - is it running?If it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
```

I have made some tests accessing ec2 instance and trying to run simple docker commands like

```
docker ps
```

When I run as bamboo or ec2-user user

```
su - bamboo -c "docker ps"#?orsu - ec2-user -c "docker ps"
```

it shows me the error:

```
su - bamboo -c "docker ps"2015/02/09 12:34:05 Get http:///var/run/docker.sock/v1.14/containers/json: dial unix /var/run/docker.sock: permission deniedsu - ec2-user -c "docker ps"2015/02/09 12:34:05 Get http:///var/run/docker.sock/v1.14/containers/json: dial unix /var/run/docker.sock: permission denied
```

When I run as root it runs normally:

```
sudo docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
```

What should I do to run this script?


Answers:
author: Pawel Skierczynski
body: There are two parts of it.

Docker service must be started as a root, so it's best done during system startup etc.

Docker client can be accessed with user that is not root but is in docker group. It depends on docker version as it was changing.

Look here: <http://askubuntu.com/questions/477551/how-can-i-use-docker-without-sudo>

Or here: <https://docs.docker.com/installation/ubuntulinux/#giving-non-root-access>

comments: author: Wellington Silva
body: Hello Pawel.

First of all I would like to thank you.  
I made a change in the script task to run with "sudo". It worked fine. I am facing another issue now:

"...Service 'redis' failed to build: Error pulling image (unstable) from debian, Driver devicemapper failed to create image rootfs..."

Seems to be Device Mapper vs AUFS stuff. Anyway I am still searching.

Thanks again.


author: Pawel Skierczynski
body: sudo is usually not the best option but it's simple so if it's enough for you that's ok tooit seems race condition on device mapper is neverending story. Especially when building new image.Maybe as you suggest you can try switching to different storage. If docker and kernel is kind of new you could try "-s overlay" when starting docker service. You've probably seen this already: <https://docs.docker.com/reference/commandline/cli/> (section "Daemon storage-driver option")


Tags: build

docker

docker-file
What is the Bamboo host when installing the remote agent?
Asked by Jeff Hansen:

I'm trying to follow:

<https://confluence.atlassian.com/display/BAMBOO/Creating+a+custom+elastic+image>

and

<https://confluence.atlassian.com/display/BAMBOO/Bamboo+remote+agent+installation+guide>

so that I can run the Bamboo agent on my own custom version of Ubuntu. I want to export my image as an AMI that I can use it as an elastic instance in Bamboo (Cloud?). I downloaded the full Bamboo 5.7.2 and extracted the tarball, and I'm ready to issue this command:

java -jar ./atlassian-bamboo-5.7.2/atlassian-bamboo/admin/agent/atlassian-bamboo-agent-installer-5.7.2.jar BAMBOO_HOST

But I don't know what BAMBOO_HOST is supposed to be.

Maybe I'm doing something wrong, though... How am I supposed to install (or even just start if installation isn't necessary) the Bamboo agent on boot so that Bamboo cloud can use my instance?


Answers:
author: Jeff Hansen
body: This page is not applicable for Atlassian-Hosted Bamboo:

<https://confluence.atlassian.com/display/BAMBOO/Creating+a+custom+elastic+image>

It ought to have a link and a notice at the top to this page:

<https://confluence.atlassian.com/display/BAMBOO/Creating+a+custom+elastic+image+-+Linux>


author: Volodymyr Krupach
body: BAMBOO_HOST should be a domain resolved to the IP of the machine where you installed the BAMBOO server.

For example:

bamboo.yourcomapeny.com where [bamboo.yourcomapeny.com](http://bamboo.yourcomapeny.com) is resolved by the DNS.

For sure you can put naked IP of the bamboo server but make sure that it's persistent. If your host the bamboo under the amazon EC2, you can allocate Elastic IP for this.

comments: author: Jeff Hansen
body: This is not a server that I set up myself; it is an Atlassian hosted one. In step 2 of the remote agent install guide, it says to "Click Agents in the left panel (Under Build Resources)", which link doesn't exist, so I found the referenced atlassian-bamboo-agent-installer-5.7.2.jar file in the full Bamboo release instead. However, when I run the jar with my Atlassian hosted domain name, I get a bunch of log4j errors, and it says:log4j:ERROR Could not read configuration file from URL \[null\].There must be a different host that I use for Atlassian-hosted Bamboo. Can anyone at Atlassian please help?


author: Jeff Hansen
body: I just found:<https://confluence.atlassian.com/display/BAMBOO/Creating+a+custom+elastic+image+-+Linux>Which seems to apply to my setup and have up-to-date instructions, as opposed to:<https://confluence.atlassian.com/display/BAMBOO/Creating+a+custom+elastic+image>Which appears out of date and non-applicable to my Atlassian-hosted Bamboo setup.


Tags: cloud
Why am I limited to 5 plan branches ?
Asked by Jean-S?bastien GERARD:

I have setup a plan so that it creates automatically plan branches when a branch is created from my main git branch.

I can see up to 5 plan branches but no more. If I want to see the next ones, I have to delete plan branches.

Why is that ?

Please have a look at how it looks in Bamboo :

5 plan branches max.JPG

Thanks for your help !  
[](https://community.atlassian.com/t5/Bamboo-questions/Why-am-I-limited-to-5-plan-branches/qaq-p/353552?attachment-id=9134){#link_11691ea5cdc8a9}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/11217/1/5%20plan%20branches%20max.JPG){#display_11691ea5cdc8a9_0}


Answers:
author: Krystian Brazulewicz
body: Looks like you're using Starter License. Please read carefully [our licensing details](https://www.atlassian.com/licensing/bamboo#serverlicenses-1)

comments: author: Jean-S?bastien GERARD
body: Indeed! It looks like I'm limited to 10 jobs... As I have 5 plans with 1 job per plan, I only have 5 available jobs left.... so I guess it is the reason.


author: Timothy
body: There is a limit that branches are somehow calculated along into the license. You should raise a support issue with Atlassian to confirm.

comments: author: Jean-S?bastien GERARD
body: yep, the limitation comes from the license '-(


Tags: branch

cloud

plan
Why in bamboo can only choose artifacts from build results since the last created release.
Asked by Ian Kent:

We are using Bamboo 5.7 OnDemand.

We want to create an artifact release from a successful build result to be deployed to one of our deployment environments. The UI will not allow us to create a release from the build result because of restriction.

"Note: You can only choose artifacts from build results since the last created release."

Why can't we create a release from a successful build result before a later released result?

I don't understand the rationale behind this restriction and the docs do not help me understand.


Answers:
author: Krystian Brazulewicz
body: Rationale behind that was we though of consecutive Deployment Versions as representation of the progress in your product development.

We wanted to make sure that it can be possible to display accurate list of changes (commits and issue keys) between any given Deployment Versions. In case you have chosen a build result that run before the build result connected to previous Deployment Version you can't tell what are the changes between just created Deployment Version and the previous one.

To workaround this problem you can create separate Deployment Project for this ad-hoc deployment and deploy it from there.

Hope this helps.

comments: author: Lech Rogowski
body: No, it doesn't help.

*"In case you have chosen a build result that run before the build result connected to previous Deployment Version you can't tell what are the changes between just created Deployment Version and the previous one."*

Sure I can. And Bamboo should too. Diff the list of commits between the build result connected to previous Deployment Version and the build result connected to the one connected to the just created Deployment Version.

What's so hard about it? Bamboo knows both build results and commits that went into them, doesn't it?


Tags: cloud
What is the best way to keep a bamboo plan under version control?
Asked by Nicholas Fisher:

We have both bamboo and stash. Is there a good way to keep our build plans under source control. The only option I can see is to export the plans and commit it, but that is a binary, which consumes space and is not easily readable.


Answers:
author: Bob Swift (personal)
body: We have our plans under source control using [Plan Creation Scripting](https://bobswift.atlassian.net/wiki/display/BCLI/Plan+Creation+Scripting?src=sidebar) from [Bamboo Command Line Interface (CLI)](https://bobswift.atlassian.net/wiki/display/BCLI). It has been a real benefit (I am a bit biased :wink:) especially for creating new plans similar to existing plans and managing plans across multiple Bamboos (production and development). There are certainly limitations and some rough spots we hope can be ironed out once better REST APIs are available from Bamboo in the future.


author: James Dengel
body: Indeed this would be a most welcome feature.


Tags: bamboo-administration
Can I set a default argument for bash execution in Bamboo?
Asked by Chris Warren:

In Bamboo, I want my Bash commands and scripts to run with the -e option by default. I tried specifying "/bin/bash -e" as a custom executable, but that couldn't be detected as a capability on any of my remote agents. Is there a way to make -e a default argument/option when using Bash? There are a *lot* of build and deployment plans here, and going through to each one and manually adding "set -e" is something I would really like to avoid.

Thanks.


Answers:
author: Chris Warren
body: Thanks! I really like that second suggestion, and I'm a little embarrassed I wasn't able to think of it. :smile:


author: Daniel Wester
body: Couple of ways:

You could set:

```
set -o pipefail
```

in the startup script of the bamboo agent (that would affect all builds though - kinda sledge hammer approach).

The other way would be to create a bash-e.sh script and have it execute bash -e. Then just change the executable to point to it in bamboo's ui. I would probably go for that one.


Tags: bamboo-administration
How to update (increment) a plan-level (or higher) variable?
Asked by Pascal:

I'm using Bamboo plan branches. These are deployed through Octopus Deploy. The latter expects a unique release number with every deploy. Bamboo offers auto incrementing for releases of regular branches but not for plan branches. This is a true pain.

The only solution I see is to have a plan-level (or higher will do too) variable that I can increment and update with every deployment. But so far I have tried:

1. to update a regular Bamboo variable
2. to write the variable to a globally accessible file with Powershell, but the scope of a script is the current deployment directory
3. to use system variables, but I wasn't able to write to these from script either

Is any of this possible and if so: how? Or is there a better solution to my core problem?

Thanks, Pascal


Answers:
author: Pascal
body: Yes! I got it to work using the [Variable Task add-on](https://marketplace.atlassian.com/plugins/com.atlassian.bamboo.plugins.variable.updater.variable-updater-generic) for Bamboo. Here's how I set it up:

1. Create a plan-level variable, e.g.   
   Plan_level_variables.png  
   Add_plan_variable.png  

   <br />

2. Add a "Version Variable Incrementer" deployment step with the following configuration:  
   Version_Variable_Incrementer.png
3. Use the variable ${bamboo.release_sequence_number_for_plan_branches} in subsequent steps, e.g. in the release numbering for Octopus Deploy:  

   ```
   create-release --project "Test" --releaseNumber ${bamboo.alphaVersion}-alpha-${bamboo.inject.jiraIssueNumber}-${bamboo.buildNumber}-${bamboo.release_sequence_number_for_plan_branches} --packageversion ${bamboo.alphaVersion}-alpha-${bamboo.inject.jiraIssueNumber}-${bamboo.buildNumber} --ignoreexisting --server http://localhost:8090/ --apiKey ${bamboo.OctopusApiKey_Password} --releaseNotes "${bamboo.inject.jiraIssueNumber}"
   ```

[](https://community.atlassian.com/t5/Bamboo-questions/How-to-update-increment-a-plan-level-or-higher-variable/qaq-p/130397?attachment-id=1913){#link_11691efda3e42c}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/4223/1/Plan_level_variables.png){#display_11691efda3e42c_0}  
[](https://community.atlassian.com/t5/Bamboo-questions/How-to-update-increment-a-plan-level-or-higher-variable/qaq-p/130397?attachment-id=1914){#link_11691efda3e42c_0}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/4223/2/Add_plan_variable.png){#display_11691efda3e42c_2}  
[](https://community.atlassian.com/t5/Bamboo-questions/How-to-update-increment-a-plan-level-or-higher-variable/qaq-p/130397?attachment-id=1915){#link_11691efda3e42c_1}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/4223/3/Version_Variable_Incrementer.png){#display_11691efda3e42c_4}
Why will branches not create themselves automatically?
Asked by johntholland:

We would like for any new branch created in a repository to create a new branch in Bamboo. In settings for a given project, there is selected the following with a check:

**Create plan branches for branches detected in the repository**

However, new branches are not appearing as options. When I click to switch between branches, only a few that have been manually added are in the populated list. I can add more branches in the settings, but I want to not have to do this.


Answers:
author: cbenard1
body: Hi John,

Sergey's initial comment is correct. If you are creating new branches in your VCS then Bamboo should follow suit, however it will not create plan branches for existing branches in your VCS. If you are creating new branches in your VCS and that isn't translating to Bamboo properly could you please create a support request at <http://support.atlassian.com> because you may be dealing with some other issue.

Thanks!

Turner


author: Mauro Minosse
body: About the wrong behaviour of "Automatic branch management" with SVN, I just raise the issue BSP-24079 to [http://support.atlassian.com](http://support.atlassian.com/)


author: Sergey Podobry _Stellarity Software_
body: Hi John,

**Create plan branches for branches detected in the repository** will create plan branches for any new repository branches (not for existing repository branches).

Try creating a new repository branch and see whether a new plan branch is created automatically (it should if everything is ok).


Tags: cloud
Is it possible to script a mass change to all "script body" values in a bamboo instance?
Asked by David Karr:

I work with a Bamboo 4.4.5 instance that has a large number of build plans. Quite a few of those build plans have a particular script task that I need to make a small change to in the "script body" field. Does Bamboo provide any way to "script" the modification of this, so I don't have to go into every single build plan and hunt and click into each script task to change the value?


Answers:
author: Przemek Bruski
body: Changing the script content directly in the db (build_definition table) is the only way to achieve this.

There are no checksums or anything, you can directly replace it. Keep in mind it has to be valid XML and make a backup before you do that.


Tags: bamboo-administration
update bamboo global variable from deployment project
Asked by Sreekumar Menon:

I have a global variable called last_deployed_commit_id . Ater a succesful release I want to update this variable from bamboo deployment project, is it possible? I am using this variable to get all the files changed between last deployment and the last commit.

if not, is here a better way to store this information ?

Any help is appreciated.


Answers:
author: Krystian Brazulewicz
body: Take a look at this plugin: <https://marketplace.atlassian.com/plugins/com.atlassian.bamboo.plugins.variable.updater.variable-updater-generic>


Tags: bamboo-administration

bitbucket-server
Get Feed of Incomplete builds from Bamboo
Asked by Peter Kahn:

Hi all,

Bamboo restarted leaving incomplete workspaces scattered across my many build agents. I'd like to find and purge them quickly and effectively.

I can get a list of successful builds and failed builds via RSS but I'd like to get a list of those yellow icon'd incomplete builds.

Does anyone know how to build the right url for feedType incomplete createAllBuildsRssFeed.action ?

Thanks

Peter


Answers:
author: Peter Kahn
body: REST API Does it. Using the result resource we can specify collection of Unknown buildstates which would be out incomplete builds.

...rest/api/latest/result?buildstate=Unknown\&includeAllStates=true\&max-results=200

[Doc for 4.x](https://docs.atlassian.com/bamboo/REST/4.0/)


Tags: bamboo-administration
Shared Artifact from Non-Existant Build Plan on Elastic Bamboo
Asked by Richard Dyer:

Over time I've modified and edited our build projects and now currently have a single build project and a single deploy project. In my dropdown for artifacts in the deploy projects, I have an old entry from older projects. It's confusing because the two are named the same but are clearly not the same. How can I get rid of this? I can't find any single place where all shared artifacts are stored so I can purge and now I'm left with a ghost artifact from some project that doesn't seem to exist.

Note: I'm an admit and can see all the build plans in the environment. This shared artifact is from nothing as far as I can tell.. How do I get rid of it?


Answers:
author: rsperafico
body: Hello Richard,

Thank you for your question.

I would kindly ask you to run your deploy using the "ghost" artifact and please attach the deployment log generated to this inquired. In there, we can have more information about the artifact and from where this artifact is being requested.

---

Kind regards,  
Rafael P. Sperafico  
Atlassian Support


Tags: cloud
how to change build requirements per branch?
Asked by Laert Pires:

Hi,

With a plan with multiple branches that run builds in parallel is there a way to change the build requirements per branch? I specifically want to set a requirement based on a branch variable to enforce the builds to run on specific servers.  

Thanks,  


Answers:
author: rsperafico
body: Hello Laert,

Thank you for your question.

Regarding to your question: *is there a way to change the build requirements per branch?*, no, the requirements are set up in the job level and you cannot change it to behave differently in an individual branch, I am afraid.

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

---

Kind regards,  
Rafael P. Sperafico  
Atlassian Support