youngmon/atlassian-qna huggingface dataset:
Remove user from all cards
Asked by Humadyn:

Hi All,

Is there a way to remove a users name from, not just a board, but also all the cards?

Thanks, Kev


Answers:
author: Brittany Joiner
body: [@Humadyn](/t5/user/viewprofilepage/user-id/4389959) try using the Bulk Actions Power-Up! You'll be able to select up to 80 cards at a time and remove a user

comments: author: Humadyn
body: Wow! I couldn't do what I was looking to do...however, Bulk Actions is very cool and useful. Thanks Brittany!
How do I filter and find archived jobs on my iPhone?
Asked by Doug Picatti:

I use Trello to track our service jobs. I want to be able to search on archived (ie old) cards/jobs so I can find past information as I can do on my laptop. I cannot find how to change my settings in my iPhone to allow me to filter/search for archived jobs.

What am I missing??????


Answers:
author: Oliver S
body: Hi Doug,

Welcome to the community!

To access archived cards on Trello for iPhone - select the board menu (3 dots top right of board), along the top line of icons click the next 3 dot menu, under which there should be an 'Archive' section. You'll be able to toggle between cards and lists. :)

Hope this helps! Reach out if you have any further questions!

Oliver


Tags: cloud
Automated Due Dates not working
Asked by Andrew Oakes:

Hello,

I'm trying to have labels automatically added and removed based on how far out a due date is, but they're not working. Attaching my commands here.

Any idea why it's not working?

![Screen Shot 2023-01-18 at 9.58.24 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/235111iB9CDF53441A86DDD/image-size/large?v=v2&px=999 "Screen Shot 2023-01-18 at 9.58.24 AM.png")


Answers:
author: Lara
body: Hi Andrew,

Thanks for reaching out!

Hmm, that seems strange. Could you please confirm that your card due dates are incomplete? These command's won't work if the due date is marked as complete.

Could you also check if there are any errors in the command log?

To do so, go to the command that you want to inspect and click the lightbulb icon in the upper-left corner of that command.

![screenshot_CommandLog2 (1).png](https://community.atlassian.com/t5/image/serverpage/image-id/235484iCC41B9AFBC7859BD/image-size/large?v=v2&px=999 "screenshot_CommandLog2 (1).png")

Let me know how that goes,

Lara  
The Trello Team
git checkout fails due to windows path length restriction
Asked by Timothy Borrowdale:

Our .net source folder structure ends up with some very long file paths (think \\verylongsolutionname\\verylongprojectname\\Service References\\verylongservicename\\verylongprojectname.verylongservicename.datasource). This code is (currently) autogenerated through visual studio, so changing them to short names would be a large task with continual maintenance.

This limits us when cloning the repository to quite short repository paths. When bamboo checks out the version it tries to do so into something like this "bamboo-home\\xml-data\\build-dir\\HZN-DEV-JOB1" it fails because it's violating windows 260 char limit. I'm guessing this sort of path structure is hard coded, so I can't just get it to clone into c:\\shortpath or similar...

Has anyone overcome this sort of issue?


Answers:
author: Jason Monsorno
body: We had a problem with the build not the checkout so it was a bit easier to handle. I made a symlink to bamboo-home\\xml-data\\build-dir and always used that.


Tags: git

windows
Wait for previous plan to finish building before starting the next one
Asked by JohnD:

I have set up a Plan in Bamboo (running on Ubuntu 12.04) with 3 Stages. I'm just using the default Agent.

Builds are manually triggered via a POST request to the REST API. I want builds to be able to be queued so I've set number of concurrent builds to a high value (which seemed to be the only way to achieve this), but I also want one build to finish before the next one begins.

At the moment this is what's happening if I send 3 build requests in quick succession:

* Build #1 Stage 1
* Build #2 Stage 1
* Build #3 Stage 1

<!-- -->

* Build #1 Stage 2
* Build #2 Stage 2
* Build #3 Stage 2

<!-- -->

* Build #1 Stage 3
* Build #2 Stage 3
* Build #3 Stage 3

This is what I would like to happen:

* Build #1 Stage 1
* Build #1 Stage 2
* Build #1 Stage 3

<!-- -->

* Build #2 Stage 1
* Build #2 Stage 2
* Build #2 Stage 3

<!-- -->

* Build #3 Stage 1
* Build #3 Stage 2
* Build #3 Stage 3

Anyone know how to achieve this? Stage 2 takes about half an hour and Stage 3 sends an email, so if 20 build requests are submitted then we have to wait around 10 hours for all of the Stage 2s to complete before the emails are finally sent all at once, rather than receiving one email every half hour or so.


Answers:
author: ????? ???
body: I have the same problem like John, someone know how to solve it ?


author: Nico_Jahn
body: I am facing the same issue, Had to go through the same approach (Calling bamboo via its rest API).  
If I change the number of concurrent builds (Miscellaneous \> Override default number of concurrent builds), my rest API call returns the following:  

\<status\>\<status-code\>400\</status-code\>\<message\>Build requested but not started, you have reached the maximum number of concurrent builds allowed 1.\</message\>\</status\>  

<br />

Does anyone know a way to prevent it from happening? I would like to have the same solution as John Delaney described.

I know that I could have one stage only and one job and many tasks, but I'd at least like to know if there's a flag or something else easier to be implemented to avoid refactoring.  

Cheers,

comments: author: Nico_Jahn
body: Yeah, you get mostly unuseful ideas instead of answers to your question :-/


author: Felipe Kraemer
body: Hi John,

I am wondering if [setting up plan build dependencies](https://confluence.atlassian.com/display/BAMBOO/Setting+up+plan+build+dependencies) could help you. Can you please give it a try?

I hope this helps!

Kind regards,  
Felipe Kraemer  
Atlassian Support


Tags: bamboo-administration
Bamboo builds twice the main branch
Asked by Viktor Nagy:

My bamboo plan is set up for a Bitbucket repo, the branch set up for the repository is "develop".

Under the branches settings, I've set up Bamboo to automatically manage my branches, and as "master" and "develop" already existed, I've added them using the "Create branch" button.

Since then, whenever I push to my develop branch, bamboo builds the develop branch twice.

How can I stop this behavior, and have bamboo building only once?


Answers:
author: bmccoy
body: Hi,

Bamboo will build the plan and the branches. As you have configured the plan to use the branch develop, it will be responsible for this vcs branch. Therefore you remove the "plan branch" for your develop branch.

If you want some of the branch features for your develop branch (like the auto merging) then you can disable the plan preventing it from running against the 'develop' branch, and the branches will all still run.

Cheers,

Brydie


Tags: cloud
How do you handle persistent windows?
Asked by Caleb Tote:

We need to deploy a weblogic environment, which requires that the window it's launched in remain open. How can we accomplish this with Bamboo? I started using SSH, but realized that as soon as the window is closed, the weblogic session is killed.


Answers:
author: Daniel Wester
body: What do you mean "remain open"? (It's been a while since I've dealt with weblogic). Can you use the weblogic deployer to deploy things?


author: rsperafico
body: Hi Caleb,

In what language your deploy to your weblogic environment is written on?

I would suggest you adding an {Executable \> Command} under {Bamboo administration \> Build Resources \> Server Capabilities} that will wait for a callback from your deploy.

Kind regards,  
Rafael


Tags: bamboo-administration
Directory structure in Bamboo builds
Asked by JohnD:

I'm porting across a PHP project from Jenkins to Bamboo, and feel as though there's something I must be missing with Bamboo.

I wanted to get rid of the linear set of commands that we had with Jenkins and separate things out into Stages. The very first Task is to checkout the source repos, which end up in xml-data/build-dir/PROJ-PLAN-JOB1/(foo\|bar\|baz). Now for every task in subsequent stages, e.g. running unit tests, I need to set the working directory to "${bamboo.build.working.directory}/../PROJ-PLAN-JOB1/foo". Is this the correct way of doing things?

Also, is there a standardized location for things like configuration files? We have a set of .yml and .xml files that contain sensitive info like the live database credentials, which we don't want to keep under source control. At the moment I'm just doing the following in a script, which seems suboptimal:

```
cp /path/to/live-parameters.yml ${bamboo.build.working.directory}/../PROJ-PLAN-JOB1/foo/app/config/parameters.yml
```

**TL;DR** I want to work on the same set of files in each Stage of my Plan, but it appears that I always need to refer to the relative path of the subdirectory where the files are first checked out. Is this correct?


Answers:
author: Marcin Gardias
body: Let me explain why it is so.

The stages are designed with parallel \& distributed execution in mind. You can define many jobs in single stage and they will run in parallel (as long as you provide enough agents). But this has consequence on how we had to organise working directories: since jobs can run in parallel and are dynamically assigned to agents (which can be remote), each job runs in separate directory. This in turn means that if you need to pass information to later stages you should use Artifacts.

Long story short: if your build is sequence of things to be happening on single dir, using single Job is better solution.

What you do will work only as long you don't use concurrent builds and have only 1 agent that runs your build.


author: JohnD
body: I see, thanks for the quick response!


Tags: bamboo-administration
Bamboo error "Error creating bean with name 'agentManager'"
Asked by Jason Monsorno:

|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 11-Apr-2014 02:59:33 | Failed to execute the build 'SYS-PU-JOB1-10': Failed to find component: Error creating bean with name 'agentManager': Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)                                                                             |
| 11-Apr-2014 02:59:33 | Error occurred while executing the build for System Maintenance - Production Updater - Default Job #10 (SYS-PU-JOB1-10) : Failed to find component: Error creating bean with name 'agentManager': Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!) |

My system configuration hasn't changed in a few months - no upgrade to OS, bamboo, or add-ons - and this just started happening. It seems isolated to this job which has about a 3hr script.


Answers:
author: Jason Monsorno
body: FTR, the WYSIWYG editor displayed the log message a lot cleaner.


Tags: bamboo-administration
Deploying a branch using FTP
Asked by Miguel Rodriguez:

I setup JIRA, Stash, and Bamboo together (I am not sure if correctly) and want to grab a repository from Stash to Bamboo, then deploy it to a FTP server.  

I got as far as the Plan setup, now how do I deploy the files to the FTP server? Is there something I am missing?


Answers:
author: Daniel Karso
body: This feature really needs to exist because of limitations in some server hosting. Especially with PHP/Drupal/Wordpress development where (S)FTP deployment is standard workflow.

The only proper GIT -\> deploy FTP tool currently available is Beanstalk. They auto deploy via (S)FTP only the changed files automatically.


author: Sergey Podobry _Stellarity Software_
body: Hi everyone,

In case someone needs to deal with FTP here is the plugin: [FTP Task](https://marketplace.atlassian.com/plugins/com.stellarity.bamboo.ftp-task/server/overview).


author: Mirko Skramusky
body: Hi Miguel,

You can do a lot of different tasks after building a project using bamboo. Unforunately uploading to a FTP server isn't a standard task. You could use a plugin, e.g. [this](https://marketplace.atlassian.com/plugins/com.println.bamboo.ftp.plugin) one (I have not tested it) or you upload it via the command line as a bamboo task (using "Script" task). Alternatively can you upload the build result via SSH or SCP? There are standard tasks available.

Regards, Mirko


Tags: bamboo-administration
Bamboo, Create branch and Build Enable
Asked by Christopher Searle:

Hi,

We have a copy of Bamboo, there is one thing that annoys us the most, and that is when we create a branch we always forget to enable the branch. Is there anyway to set this to being checked by default - its more as we forget to check this, then we have to enable it through the branch page then have to start the build, whereas, if in the create branch dialog we select to enable it, it automatically runs a build for us!

Cheers

Chris


Answers:
author: Ron Chan
body: I suppose this would be nice to have, when whenever we need to create a branch build from bamboo.

But usually, since we have Bamboo auto detect new branches, Bamboo will just auto enable and build our branches.


author: rsperafico
body: Hi Christopher,

Thank you for contacting Atlassian Support.

Unfortunately the functionality you're requesting is not currently implemented in Bamboo. This is being tracked here:

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

I would suggest adding any comments to the issue above as well as voting ([](https://confluence.atlassian.com/display/JIRA/Watching+and+Voting+on+an+Issue)<https://confluence.atlassian.com/display/JIRA/Watching+and+Voting+on+an+Issue>) on the issue to create it's popularity and likelihood of being implemented in a future release.

For more information on how Atlassian implements new features and improvements please see the following document:

<http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy>

My apologies that I don't have a solution for you at this time.  
---  
Kind regards,  
Rafael P. Sperafico  
Atlassian Support


Tags: bamboo-administration
Automatically remove Plan branches when they have been deleted from Stash?
Asked by Ian Gregson:

Hi there,

I have noticed that my branches under my plans are still left there even when I merge and delete a branch. I know its possible to set this to automatically delete if no commits are received in XX days but surley there must be a way of saying "Remove the branch from the if it no longer exists" - runs every 5 minutes?

I can't seem to find this funcitionality, anbody know if there is a plugin that takes care of this?

The problem is that my braches seem to count towards my number of Jobs that I can run with my lience. And removing a branch from stash either manually or deleted because of a merge should, in my opinion, remove the plan branch as it no longer exists?

Anybody have any ideas?


Answers:
author: Mibex_Software
body: Hi,

Better late than never :smile: We have open sourced a plug-in for Bamboo meanwhile which instantly deletes a plan branch once the corresponding Git branch got deleted in Stash and Bitbucket server. It is in an early alpha state, so please use it with care:

<https://github.com/mibexsoftware/plan-branch-terminator>

Best regards,

Michael


author: GaryBond
body: We are using JIRA in the cloud and running Bamboo on our own server.


author: Mibex_Software
body: We could also provide a plug-in for Bamboo, because now with some recent changes that occurred in Bamboo this will be possible. Are you using Bamboo in the cloud or behind a firewall?


author: GaryBond
body: It appears that that plugin is only for Stash.   
We are using JIRA \> Bitbucket \> Bamboo, but have the same requirement to remove deleted branches from Bamboo.


author: Mibex_Software
body: You might have already noticed it, but I wanted to mention it anyway: There is a plug-in on the Marketplace called [Plan Branch Terminator](https://marketplace.atlassian.com/plugins/ch.mibex.stash.branchterminator)[](https://marketplace.atlassian.com/plugins/ch.mibex.stash.branchterminator) which deletes plan branches instantly when the related branch is deleted in Stash.


author: Zack Sheffield
body: Found an open improvement request \[[BAM-13129](https://jira.atlassian.com/browse/BAM-13129)\] to do exactly this, I suggest you vote on it as well... for larger instances this would tend not to be an issue because the age-off after 30 days of inactivity would clean up the dead plans eventually, starter licenses really need this functionality to avoid blowing through their 10 job limit as soon as they start using a feature-branch workflow.


Tags: bamboo-administration

branch
does the working directory change as a plan executes?
Asked by john livingston:

Does each stage of a bamboo plan have a unique working directory?

And so for each stage, the variable bamboo.build.working.directory would change?


Answers:
author: Przemek Bruski
body: Each job runs in a separate dir.

comments: author: john livingston
body: Thank you. This was not evident via documentation.

Also, via email, I accepted this answer, however, that response did not create the accepted 'check' here.
log entries are out of order
Asked by john livingston:

What conditions would create log entries out of order in relation to their timestamps?

The following is a log snippet from one stage of a Bamboo Plan.

[Atlassian Bamboo](http://www.atlassian.com/software/bamboo/) version 5.4.2 build 4208 - 03 Mar 14

|----------------------|------------------------------------------------------------------------------|
| 10-Apr-2014 16:26:20 | executing make clean                                                         |
|                      |                                                                              |
| 10-Apr-2014 16:26:20 | cleaning finished                                                            |
| 10-Apr-2014 16:26:21 | Finished task 'clean'                                                        |
| 10-Apr-2014 16:26:21 | Running post build plugin 'Artifact Copier'                                  |
| 10-Apr-2014 16:26:21 | Running post build plugin 'NCover Results Collector'                         |
| 10-Apr-2014 16:26:21 | Running post build plugin 'Clover Results Collector'                         |
| 10-Apr-2014 16:26:21 | Finalising the build...                                                      |
| 10-Apr-2014 16:26:21 | Stopping timer.                                                              |
| 10-Apr-2014 16:26:21 | Build DEV-FH-COM-18 completed.                                               |
| 10-Apr-2014 16:26:07 | Running on server: post build plugin 'NCover Results Collector'              |
| 10-Apr-2014 16:26:07 | Running on server: post build plugin 'Clover Delta Calculator'               |
| 10-Apr-2014 16:26:07 | Running on server: post build plugin 'Build Hanging Detection Configuration' |


Answers:
author: Przemek Bruski
body: You probably don't have ntp set up either on agent or the server. The first section comes from the agent and the second from the server.

comments: author: john livingston
body: I think it would be benficial to note host names as part of the log message when hosts other than the local server are involved.
Bamboo Create Release permissions
Asked by Dimitri Tischenko:

Hello,

We are using Bamboo 5.2.2. I have configured a deployment project and everything works fine. I noticed that there is no separate permission to create releases - the permission is granted when the 'edit' permission on the deployment project is granted. Unfortunately, this means that the person also can edit the project's tasks which is not what we want. Is it possible to have a separate permission for creating releases? Or is there another work-around?


Answers:
author: Felipe Kraemer
body: Hi Dimitri,

Unfortunately the functionality you're requesting is not currently implemented in Bamboo.

I have created a new issue in our development issue tracker for this functionality to ensure our development team is aware of your request:

[](https://jira.atlassian.com/browse/BAM-14469)<https://jira.atlassian.com/browse/BAM-14469>

I would suggest adding any comments to the issue above as well as [voting](https://confluence.atlassian.com/display/JIRA/Watching+and+Voting+on+an+Issue) on the issue to create it's popularity and likelihood of being implemented in a future release.

For more information on how Atlassian implements new features and improvements please see the following document:

[](http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy)<http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy>

My apologies that I don't have a solution for you at this time.

Kind regards,  
Felipe Kraemer

comments: author: Dimitri Tischenko
body: Hi Felipe,

Thanks for your answer. As a work-around, could we configure Bamboo to automatically create a release when a branch is created?
Deployment project from multiple plans
Asked by Radek Antoniuk:

I am using Bamboo for a long time before the Deployment Projects were there.

Currently, I have a setup where I have multiple "deploy" bamboo plans, where they fetch appropriate artifacts via bash script and then deploy them to a specific server.

Additionally, I have multiple build plans for different projects branches (as the configuration of tasks for them may be different).

Now, when the Deployment projects came up I thought - great! I will be able to remove all the separate deploy plans and create environments.

However, I have one problem. I need the deployment plan to fetch artifacts from multiple build plans (because I want to sometimes deploy a version from one branch and once from another).

Is that possible?


Answers:
author: Radek Antoniuk
body: I can confirm this actually works with Bamboo 5.5.1.

I have configured branches for the project and nevertheless that in the deployment project configuration, the trunk branch is selected, while deploying i am able to select a build from another branch! :-)


author: Hussain Misbah
body: I want to do the same thing and unfortuantly I don't find any good docummentation to use the new deployment plans..I hope someone will help over here.


Tags: bamboo-administration
Bamboo Deployment Project - Skipping Versions
Asked by Eclipse Trading:

I am new to deployment project, and this is the workflow I am thinking about:

\* Bamboo building continuously, and when I like a release, I go to Deployment project and create a new release (say v10)

\* v10 contain 20 commits, and 3 issues

\* now I figured I dont' want to deploy v10 to production, so I create v11

\* v11 is next build containing 2 commits and 1 new issue

How do I capture the next production release contains 22 commits and 4 issues, rather than 2 commits and 1 issue?


Answers:
author: Marcin Gardias
body: - if you deploy manually, the 'run deployment' screen will compare the currently deployed version with the version that is currently deployed

- in version page, you have tabs for commits and jira issues, when you go there you can select any version from the history and see agregated commits and issue since that version


Tags: bamboo-administration