youngmon/atlassian-qna huggingface dataset:
I need to know how to stop getting mails after I currently archive a list
Asked by Giancarlo Quassia:

How do I stop getting the mail from do-not-reply@trello.com, that sais:

Hello, {#toc-hId--526184262}
----------------------------

The list you attempted to send a card to, **ASSISTENZA DA GESTIONALE** , is currently archived and you will therefore not see your card on the board. You can still view [your card](https://trello.com/c/NJzskgsk/814-richiesta-di-assistenza-12327-censimento-vie-cancedda-sara-pisa-barbaricina) and move it to a visible list. To change the list new cards are sent to, you can use the email settings menu on the board page.

For more information on sending cards to your board via email, please visit [our help page](http://help.trello.com/article/809-creating-cards-by-email).


Answers:
author: Brittany Joiner
body: [@Giancarlo Quassia](/t5/user/viewprofilepage/user-id/5027598) it sounds like there's a chance you have an automation or something set up that is moving a card there but it's not actually moving there. If you go to Automations in the top toolbar on your board, and then select "rules" and then the filter button and "enabled", do you see any rules moving cards? (Also check under the calendar and due date sections on the left side as well)

comments: author: Giancarlo Quassia
body: Hi Brittany, and thqk u for getting back to me. There's no ''rules'' at all. Not even in ''calandar''.


author: Brittany Joiner
body: [@Giancarlo Quassia](/t5/user/viewprofilepage/user-id/5027598) strange! You might need to reach out to trello support and contact them to get to the bottom of it: <https://trello.com/contact>
Using capabilities to resolve the path to an executeable
Asked by Jan Swaelens:

Consider this scenario:

* we have 1 set of scripts to build two projects
* the first project requires a certain executable (lets say GWT 2.0)
* the second project requires another executeable (lets say GWT 2.4)

I configured two custom capabilities on the bamboo server: GWT2.0 and GWT 2.4.

Each project has its own plan in bamboo and the relevant jobs are marked with the relevant requirement.

To pass the location of the GWT folder to each build script (Ant) I pass a system property to the build target like this:

```
-DgwtHome=${bamboo.capability.GWT_XYZ}
```

What troubles me is that I need to alter this system property to include the correct capability's path. What I would want to do is:

1. Add the capability to the job for the relevant GWT version (already doing that)
2. Referencing the capability in a generic way to be able to do something like:

```
-DgwtHome=${bamboo.capability.GWT}
```

This would require something like a custom type level on capabilities along with the possibility to find a capability based on its type using bamboo variabled.

Is something like this possible? Are there other ways of doing this kind of abstraction?  
I have several cases where I could use this patterns, its not only for the GWT compiler location (app server location for ejb compiles ...).

many thanks


Answers:
author: Cameron Ferguson
body: I dont think there is a native way to do what you are wanting... the capability part of the variable I believe is only designed to obtain the value of that particular agent's capability so it can be used. So if AgentA had GWT 2.0 in "/usr/bin" and AgentB had GWT 2.0 in "/usr/local/bin" then you could get the path for that particular build.

comments: author: Jan Swaelens
body: Yeah that's what I thought, maybe Atlassian would find this something neath to add to the product?

Thanks for your input!


author: Erik Husby
body: According to the Bamboo documentation one is supposed to do this, but it does not appear to work. See the documentation -- [](https://confluence.atlassian.com/display/BAMBOO/Bamboo+variables#Bamboovariables-Usingcapabilities)<https://confluence.atlassian.com/display/BAMBOO/Bamboo+variables#Bamboovariables-Usingcapabilities>

And I found references to this capability back in Bamboo 2.

Following the instructions to see the value to be used I use this in a script task (Bamboo running on Linux)

```
echo "GIT ${bamboo.capablity.system.git.executable}"
```

I get errors like this

```
02-Jan-2014 11:01:02	/prodinfolocal/atlassian-bamboo-5.2/temp/E2P-GD-CR-12-ScriptBuildTask-6848542872684244705.sh: line 2: GIT at ${bamboo.capablity.system.git.executable}: bad substitution
```


author: Ryan Petrick
body: Just to help anyone looking, this does in fact work. There is a typo in the syntax listed in the response:

`${bamboo.capability.system.git.executable}`

Also, you would need to pass this as an argument into the script for it to work correctly.


author: Kevin Dixon
body: This actually works if you
BindException in DirectClickThroughUiPlugin when using 2 Eclipse instances
Asked by loic dev:

Hi,

I have installed:

- com.atlassian.connector.eclipse.feature.group (3.0.2.v20111010)

- com.atlassian.connector.eclipse.jira.feature.group (3.0.2.v20111010)

Everything works fine in my Eclipse.

I am developing my own Eclipse plugin (PDE). When testing it, it seems that the second instance of Eclipse tries to start a server on the same port that the one used by the main Eclipse. When I start my test (i.e. start a second instance of Eclipse) I get the following stack trace in my main Eclipse console:

!ENTRY com.atlassian.connector.eclipse.directclickthrough.ui 1 0 2012-03-15 15:32:58.808

!MESSAGE Unable to run embedded web server, Direct Click Through will not be available

!STACK 0

java.net.BindException: Address already in use: JVM_Bind

at java.net.PlainSocketImpl.socketBind(Native Method)

at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)

at java.net.ServerSocket.bind(ServerSocket.java:328)

at java.net.ServerSocket.\<init\>(ServerSocket.java:194)

at org.mortbay.jetty.bio.SocketConnector.newServerSocket(SocketConnector.java:80)

at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)

at org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:283)

at org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:147)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.jetty.Server.doStart(Server.java:235)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:90)

at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

I don't know why you need to start a server, but could you update your code to catch this exception and deal with it ? This exception prevents me automated test to run. If you cannot avoid this exception, I will have to uninstall your plugins in order to carry on...

Thanks.


Answers:
author: jjaroczynski
body: Hi,

Atlassian Connector for Eclipse tries to start the server because you have activated Direct Click Through feature (it allows to open file/task from other Atlassian products like Bamboo, Fisheye or Crucible). If you don't need the feature then simply deactive it in Windows \| Preferences \| Atlassian Connector \| Direct Click Through.

If you want to use the feature you can ignore the exception message as it does not affect your debug Eclipse instance and does not have impact on your automated tests - it is just a log printout of caught exception.

Depending on how you start the debug instance of Eclipse you can also disable Direct Click Through only for this instance (or change port) while it stays enabled for your main Eclipse instance.

Best,

Jacek

comments: author: loic dev
body: Hi thanks for the explanation. I deactivated direct click. Now I don't see the exception anymore. Thanks again. Now I can focus on my own exceptions :)Cheers.


Tags: ide-connector
Bamboo hg error pulling bitbucket subrepository
Asked by Jason Skjonsby:

We have bitbucket hosted repositories with several subrepositories, when I try to pull a repository with a subrepository it fails with this message: stderr: abort: repository \<sub repository name\> not found! This of course fails the build since it couldn't pull the source.

The Repository structure looks sort of like this:

dev_all_main_repository = bitbucket.org/companyname/dev_all

- subrepository1 = bitbucket.org/companyname/subrepo1

- subrepository2 = bitbucket.org/companyname/subrepo2

- subrepository2_subrepository1 = bitbucket.org/companyname/subrepo2_subrepo1


Answers:
author: chrismott
body: (buildlog.txt)

Problem is still happening with "Disable repository caching" checked. Have tried many different configurations and this error still occurs with the subrepo.

Attached is the failed build log from a test repo that is very simple:

main \\ a.txt

\\.hgsub

\\component \\ b.txt

where .hgsub is component = component

The repo and subcomponent clone fine from the command line. Not sure why this is failing in Bamboo.

One thing that seemed curious in the log is "Removing '/var/bamboo-home/xml-data/build-dir/RT-TEST-JOB1' as it does not contain a valid hg repository ".


author: PiotrA
body: Hm... Have you tried to disable "repository caching" in the plan's repository advanced configuration? There should be a checkbox "Disable repository caching" there, which is supposed to enable subrepositories support.
Treat a Task failure as a warning
Asked by Michael:

I have a series of Tasks associated with a Job. And I have a series of Jobs associated with a Plan.

When a build kicks off for the Plan should one of the Tasks in a Job fail I would like to have the option to treat the failure as a warning, display the Build as yellow on the dashboard, and have Bamboo continue on to the next Job.

Possible?

Real world example -

1. Job to build .NET solution.
2. Job to run unit tests.
3. Job to deploy to development server.

If #2 fails, I want to know by looking at the Dashboard but I also want Bamboo to continue on to #3.


Answers:
author: Rick Herrick
body: We have a situation with a similar requirement albeit a different context. As part of the deployment process for our app, we want to undeploy the app from a remote Tomcat. This frees up database connections so we can drop and re-create the app database.

I have two alternatives here:

* Stop Tomcat itself
* Stop and undeploy the app via the Tomcat manager app

I've been unable to stop and start Tomcat via ssh because I can't get sudo access that way. I can undeploy the app via the manager app assuming that the app is installed. But if it's not installed (which can happen when there's a problem with the code or app configuration) that whole task fails and the build fails with it.

But frankly I don't CARE! If it fails to undeploy, that means that the app's not even there and therefore not locking database sessions and I can proceed. But to Bamboo it seems all failures are created equally and require the entire build process to abort. That seems very inflexible and frankly useless to me.

I see it's been a year since the original inquiry with no Atlassian response. So does that mean I'm hosed?


author: PinoS
body: Why can't we make a task no fail the build but maybe add a badge or something...

Also, if a project has no tests why does it fail? For example, when a project starts or at some point they are disabled... doesn't make sense to fail build or to change the plan.
Bamboo & Perforce & Label's?
Asked by Damien Glancy:

Quick question.... we use Bamboo 2.5.1 (download) and Perforce source control here at work and I am struggling to achieve something which on the face of it should be fairly straighforward.

I am trying to get a Bamboo plan to to grab a Perforce label rather than just the latest/head of a perforce repository and I just can't figure out how this can be done.

The scenario is that I have a "Release" plan that has been labeled in Perforce (dev changes may have been made since the label was applied) and I want this plan to go against the tested label rather than the head.

Anybody got any ideas?


Answers:
author: Gabor Maghera
body: You're supposed to be able to do this via the "Depot View" field in the source repository configuration, but it's broken. If it were working correctly, you would enter something like this for the field value:

//autobuild::main-dist/...@myLabel (where autobuild::main-dist is the name of the workspace used by the plan)

There is a support issue here <https://jira.atlassian.com/browse/BAM-8773> , which is "resolved" although the issue is still present.

I wish Atlassian spent as much effort on supporting Perforce as it does for Mercurial or Git. Replacing the outdated Tek42 P4Java with Perforce's own P4Java API would be a nice move, IMO.


Tags: perforce
Can you use saucelabs with OnDemand?
Asked by Anton Selfe:

The blog entry below suggests that you can integrate saucelabs (selenium) with OnDemand Bamboo:

<http://blogs.atlassian.com/2011/11/atlassian-ondemand-meet-sauce-labs/>

It takes you to the Wiki page for the plugin:

<https://plugins.atlassian.com/plugins/com.saucelabs.bamboo.bamboo-sauceondemand-plugin>

However reading the onDemand policy on plugins you aren't allowed to install it. Is this something that can be achieved can I request the plugin be installed ? anyone any ideas?

Cheers

Paul


Answers:
author: Michael Knight
body: There is only integration with JIRA OnDemand, not Bamboo OnDemand. Instructions for enabling the plugin for JIRA OnDemand can be found [here](http://confluence.atlassian.com/display/AOD/Disabling+or+Enabling+a+JIRA+Plugin#DisablingorEnablingaJIRAPlugin-Enablingaplugin).

comments: author: Anton Selfe
body: Yep so just to add some further details in case someone else tries the same thing. There is a plugin already installed in onDemand that allows you to create bugs in SauceLabs and push them into Jira. I think confusion in the blog entry comes from two products called onDemand ;)

You currently can't use Bamboo OnDemand to initiate tests in SauceLabs. For anyone interested there is a plugin request so please vote here [request to bundle the plugin](https://studio.atlassian.com/browse/JST-3240)


Tags: cloud
Bamboo EC2 Remote Desktop Connection password is not (yet) available
Asked by Jason Skjonsby:

I'm trying to setup bamboo with a Elastic Instance on Amazon EC2. After starting the new instance, it always says

'Remote Desktop Connection password is not (yet) available. If password randomisation is enabled on this image, it should become available within 15 minutes of startup.'

I'm unsure how to enable 'password randomisation', and evidently it's not enabled because the password does not become available after 15 minutes of startup.

Am I missing something here?


Answers:
author: Przemek Bruski
body: Are you using a stock Bamboo Windows image? If so, are there any exceptions in the server log?

If you are using a custom image, you need to create the image using EC2 Service program located on you instance.

comments: author: Ephraim Moss
body: I'm having a simlar issue. I made a copy of a stock bamboo windows image with some cutomisation. when booting up password never appears


author: Chad Godsey
body: Before you create the image and while logged into the running instance you want to build an image of, go to Start \> All Programs \> EC2ConfigService Settings. This window will pop up.

Check the box to set a random password on boot (highlighed red here, it turns off after boot). Now when you image this instance and spin up new instances the password will show. Otherwise, you are stuck with whatever password you had last been able to log in with.

![Ec2 Service Properties](http://i.imgur.com/ruEr4HA.png?1)


author: Mauro Badii
body: The "elasticbamboo.pk" key could be missing on the bamboo/home/xml-data/configuration directory.

If that's the case, the keypair will have to be recreated by following the steps on [Obtaining AWS Key Pair to access Amazon Elastic Instances](https://confluence.atlassian.com/display/CLOUDKB/Obtaining+AWS+Key+Pair+to+access+Amazon+Elastic+Instances)

On Cloud, please contact Support at <https://support.atlassian.com> to check the keypair and to upload the key to the directory after creating it.

Cheers!


author: Jason Skjonsby
body: It's a default image: [Default Image EBS x86_64 (windows)](http://tools.internal.pulsarinformatics.com/bamboo/admin/elastic/image/configuration/viewElasticImageConfiguration.action?configurationId=262148 "View Configuration"). The server log shows no exceptions.

comments: author: Przemek Bruski
body: Are you able to retrieve the password using AWS Console?
How do I set up the log generated in the Bamboo install directory to rotate?
Asked by David Corley:

Bamboo writes a single log to \<BAMBOOINSTALL\>/logs/bamboo.log and this can become extremely large for a long-running, busy instance.

I'd like to be able to rotate the log, so that at the end of every day, the log content for that day is spun off into its own date-stamped log.

So instead of:

\<BAMBOOINSTALL\>/logs/bamboo.log

I could have logs in the format "bamboo.YYYY-MM-DD.log" like:

\<BAMBOOINSTALL\>/logs/bamboo.2012-03-15.log  
\<BAMBOOINSTALL\>/logs/bamboo.2012-03-16.log  
\<BAMBOOINSTALL\>/logs/bamboo.2012-03-17.log


Answers:
author: Jobin Kuruvilla [Adaptavist]
body: Modify the log4j.properties file under Bamboo/webapp/WEB-INF/classes folder to use [DailyRollingFileAppender](http://stackoverflow.com/questions/1711423/how-to-rotate-log-files-based-on-time-rather-than-size-in-log4j).

comments: author: David Corley
body: Hey Jobin,  
That appears to be for the \<BAMBOOHOME\>/logs/atlassian-bamboo.log.x logs.

I'm specifically looking for \<BAMBOOINSTALL\>/log/bamboo.log. I've got a feeling it's something I need to tweak in wrapper.conf. I'll check the Tanuki Wrapper docs. I need to modify the following section:

```
#********************************************************************# Wrapper Logging Properties#********************************************************************wrapper.console.format=PMwrapper.console.loglevel=INFOwrapper.logfile=../logs/bamboo.logwrapper.logfile.format=LPTMwrapper.logfile.loglevel=INFOwrapper.logfile.maxsize=10mwrapper.logfile.maxfiles=10wrapper.syslog.loglevel=NONE
```


author: Przemek Bruski
body: IIRC, one of the patched jar files you got will change the log level to DEBUG.


author: David Corley
body: I hope so! We restarted yesterday, and we've already got a 1.8GB bamboo.log!  
Is there anything that can be done to reduce this ahead of upgrading to the next release?


author: Przemek Bruski
body: BTW, I think I know which messages you're talking about in your specific case. There will be considerably less stuff logged on your instance with the next release.


author: David Corley
body: Seems to be controlled by this property that needs to be set in wrapper.conf:

<http://wrapper.tanukisoftware.com/doc/english/prop-logfile-rollmode.html>

comments: author: Jobin Kuruvilla [Adaptavist]
body: Cool. Let us know if it worked.


author: David Corley
body: It didn't work.   
\<BAMBOOINSTALL\>/log/bamboo.sh over-rides the log settings in wrapper.conf in the following line:

```
        $RUNNER "nohup sh -c \"cd $BAMBOO_INSTALL && exec $RUN_CMD 2>&1\" >$BAMBOO_LOG_FILE & umask 022 ; echo \$! > $BAMBOO_PID"
```

, where BAMBOO_LOG_FILE is defined earlier in the shell script as:

```
BAMBOO_LOG_FILE=${BAMBOO_LOG_FILE:-$BAMBOO_INSTALL/logs/bamboo.log}
```

I guess I can hack bamboo.sh to include some form of timestamp, but it this will only ensure that a rollover occurs when Bamboo is restarted, and not every day as desired. Bummer


author: David Corley
body: Improvement request created here:  
<https://jira.atlassian.com/browse/BAM-11246>
Bamboo 3.4.5 Release Date?
Asked by Adam Myatt:

Is there a tentative or firm release date for Bamboo 3.4.5? The product roadmap at <https://jira.atlassian.com/browse/BAM#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel> shows March 6 but it does not yet seem available. Any update?


Answers:
author: Przemek Bruski
body: We are finalising the fixes scheduled for that update and building the related releases now. I'd say it's about a week away at most.

comments: author: Adam Myatt
body: Excellent. Thank you.
What is the purpose of shared capabilities in Bamboo?
Asked by emddudley:

I'm not sure I understand how shared capabilities work in Bamboo, even after reading [the documentation](http://confluence.atlassian.com/display/BAMBOO/Configuring+a+Shared+Executable+Capability).
> *Shared capabilities* are inherited by all applicable agents, that is, (shared) local server capabilities are inherited by all local agents, and shared remote capabilities are inherited by all remote agents.

So if I define a shared remote agent capability, are all remote agents required to support that capability?

Should shared capabilities be avoided if even just one agent does not support the capability?


Answers:
author: Przemek Bruski
body: > Should shared capabilities be avoided if even just one agent does not support the capability?

Correct. It's a set of capabilities common to all the agents.


Tags: capability
How can I use Ant 1.8.2 with Bamboo onDemand?
Asked by carlos benitez:

I created a build plan using Ant to compile my project. It fails because my project requires Ant 1.8.2, but Bamboo onDemand, since it runs Bamboo 3.0, works with Ant 1.7.1. I tried to create a new builder for Ant 1.8.2, but I don't have permissions (and I'm the admin).

I've read that Bamboo onDemand will upgrade to Bamboo 3.4 soon ([https://answers.atlassian.com/questions/36624/ondemand-bamboo-version-upgrade](/questions/36624/ondemand-bamboo-version-upgrade)) and then my build plan will work, but is there any way it could work before that happen?

Thank you very much.


Answers:
author: Przemek Bruski
body: It's possible.

You should install newer Ant on your instance using EBS. Once you start your instance from Bamboo, you'll be able to associate new Builders with your image (go to Elastic Bamboo/Instances, click on Image Config, click Edit, Add Capability combo is at the bottom of the page)


author: carlos benitez
body: I tried but I wasn't able to configure properly a new instance with Ant 1.8.2, so I gave up.

Some weeks ago Bamboo onDemand was updated, and Ant 1.8.2 is now available, so I don't have this problem anymore.

Anyway, thank you very much for your help, Przemek.

comments: author: Przemek Bruski
body: And the next update will include 1.8.4 ;-)


Tags: ant

cloud
Changing Bamboo Servers
Asked by philban:

Hi Guys,

We've recently bought a Bamboo download license which we've installed on a Windows Machine. We now need to change the bamboo server over one of our Linux Machines.

My Question is do we need to purchace another license or is it possible to just install it again on the new Linux box?

Many thanks!

Phil


Answers:
author: Jeremy Largman
body: You can just install it on the new box and use the existing license.

comments: author: philban
body: Ah thats great! Thanks for getting back to me Jeremy!

Cheers!
Problem configuring MYSQL 5.x with bamboo
Asked by MassimoManca:

Database configuration failed:

Error registering bean with name 'broker' defined in class path resource applicationContextJMSServer.xml : Could not resolve placeholder 'bamboo.home'

These are the parameters to configure the db:

jdbc:mysql://localhost/bamboo?autoReconnect=true\&useUnicode=true\&characterEncoding=utf8

and this is the content of bamboo-init.properties

## You can specify your bamboo.home property here or in your system environment variables.

#bamboo.home=/var/atlassian/application-data/bamboo-home


Answers:
author: Andrew Frayling
body: Hi Massimo,

Your bamboo.home is commented out, you need to remove the # so it's just:

bamboo.home=/var/atlassian/application-data/bamboo-home

Hope that helps?

Andrew.