youngmon/atlassian-qna huggingface dataset:
Are parent plans with manual stages still marked as in progress?
Asked by jmccarty:

Given the scenario that "Plan A" is a parent plan to "Plan B" and the dependency blocking stratagy of "Block build if parent builds are qued or in progress" is enabled.

If "Plan A " is designed like this:

-Stage: Checkout/Build

-Stage: Deployment (Manual)

When "Plan A" reaches the "Deployment Stage" will the child plan "Plan B" still remain queued until the "go" button is pressed on the Deployment stage? The documentation on Manual stages and blocking strategies doesn't seem to mention this scenario.

Thanks


Answers:
author: Przemek Bruski
body: IIRC with Bamboo \<4.3, plan B will be triggered after checkout/build (or to be more precise, each time Bamboo stops on manual stage or completes all stages).

With Bamboo 4.3, the behaviour depends on the setting you choose in Dependency tab, you can optionally run the dependency build after all stages are completed.

Test it out.  

comments: author: jmccarty
body: It looks like on at least 4.2 that yes plan B will trigger when it hits the manual stage. If this is indeed not the case with 4.3 then I will be looking to upgrade.
Process for setting up proxying from various ports to a web server
Asked by GregS:

Hi,

We are in the process of setting up Confluence, Crowd, Bamboo, Stash and configuring Crowd for authentication. We would like to redirect each port from our Tomcat server via a Web proxy (e.g., for Confluence we would want to redirect blood.ahc.umn.edu:8090 to blood.ahc.umn.edu/confluence, similarly with Jira, etc.). Authentication would then be done through Crowd.

First of all, how do we set up the ssl certificates for these apps? Secondly, how do we set up the Web proxy server to redirect the port requests through Tomcat (we are using Apace Web server on RHEL). Do you have any resources on-line that describe this process in-depth?

Thanks in advance!

Greg--


Answers:
author: GregS
body: Done! Got step by step response on how to proceed.


author: Tiago Comasseto
body: Hi Greg,

We have this [doc](https://confluence.atlassian.com/display/DOC/Using+Apache+with+mod_proxy) explaining this configuration for Confluence and it is pretty much the same to the other applications. It have the instructions to configure it through mod_proxy and there is a section at the end explaining how to set it over ssl.

I hope this helps

Cheers

comments: author: GregS
body: Cool!

Thanks much!

Greg--


Tags: configuration

proxy

ssl

web
Configuring Bamboo, Ngix and SSL
Asked by James Kyle:

I have an nginx proxy dispatching to bamboo on its default localhost setting. It terminates my ssl certs and listens over https.

I've set the base url in bamboo's General Configuration to <https://bamboo.mydomain.com>. However, some urls continue to redirect to http.


Answers:
author: Harry Chan
body: Hi, the simple solution would be to set a rule in nginx to redirect http-\>https.


Tags: https

nginx
agent-smith-wallboard-plugin - can it work with no elastic agents enabled?
Asked by Andrei [errno]:

running   
http://mybambooserver.com/bamboo/viewAgentWallboard.action

results in AWSException:

com.atlassian.aws.AWSException: Could create AWS account entity,   
no configuration details were found.   
Please configure you AWS credentials.

I have Elastic disabled in my Bamboo.

what configuration might the plugin need?  
thanks


Answers:
author: Odd Vinje
body: Upgraded to Bamboo 4.3.2 and agent smith plugin 4.3.1, and it still fails with the AWS error.

But I can see that in the source repository for this plugin, there is a tagged versjon 4.4.0 and 4.4.1: <https://bitbucket.org/atlassian/agent-smith-wallboard-plugin/downloads>

Hopefully it will be released soon.


author: James Dumay
body: Apparently a new version has been released of Agent Smith Wallboard that has this [fixed](https://bitbucket.org/atlassian/agent-smith-wallboard-plugin/issue/2/navigating-to-bamboo).

comments: author: Andrei [errno]
body: upgraded to Bamboo   
**Version:** 4.3  
**Build:** 3400

and the plugin to version 4.3.1

still failing...


Tags: app

wallboard
How do I setup Bamboo ondemand to run Ruby Rails Capybara Rake Test?
Asked by Wagner Pereira:

I have already configured EC2, Bitbucket, etc, but I didn't find how to configure a task to run my test job


Answers:
author: LucasA
body: Hello,

Note that if you can run this test using your EC2 instance coomand line, you can run Ruby/Rails tests using Bamboo. To perform this action, you have to create a "Task" that calls a script were you can run your test. If you have to install something, make use of bin/customise-extras.sh to install/configure what you want before elastic Agent runs.

Here you can find some usefull information about this:

* <https://confluence.atlassian.com/display/AOD/Bamboo+OnDemand>

<!-- -->

* <https://confluence.atlassian.com/display/AOD/Getting+started+with+Bamboo+OnDemand>

<!-- -->

* <https://confluence.atlassian.com/display/BAMBOO/Creating+a+new+plan>

<!-- -->

* <https://confluence.atlassian.com/display/BAMBOO/Using+plan+branches>

<!-- -->

* <https://confluence.atlassian.com/display/BAMBOO/stage>

Cheers,  
Lucas Lima  
Atlassian Support


Tags: cloud

rails

ruby

test
Bamboo Agent Licence
Asked by Senthil:

I installed Bamboo 30 days trial software. Now i purchased one licence for agent, with that licence can i create multiple Remote Agent and schedule multiple jobs? More over i want to know the difference between Agent and Remote Agent.

Thanks in Advance


Answers:
author: Przemek Bruski
body: Which license did you buy?

You can read about diffferences between local and remote agents here: <https://confluence.atlassian.com/display/BAMBOO/Creating+a+local+agent>
How do you refer to a Branch's artifact if you do not know the branch "number" beforehand?
Asked by Daniel Nugent:

I'm trying to setup a build that pulls artifacts from several other parent builds and am having some trouble figuring out how to correlate the branch "id" for a specific plan (the integer appended to the plan key) with the branch name. The variable $bamboo.repository.branch.name seems to only contain the branch name from the version control repo.

For example, I have two branches, master and release. master's "id" is 0 and the Plan name looks like MYPLAN0 while release's id is 1 and the plan name looks like MYPLAN1.

Is there a way to easily refer to branches in Bamboo by the version control branch name? Is there some variable that makes it easy to generate a URL to the corresponding branch of another Plan? Dependencies are capable of being linked based on plan name, but I can find no way to actually pull in artifacts.

Ideally, it'd be as simple as MYPLAN/branch/master or MYPLAN/branch/release and then all routes normally following MYPLAN could instead follow the branch name.


Answers:
author: PiotrA
body: Oh, and there is a ticket in the Bamboo issues tracker that you might be interested in: <https://jira.atlassian.com/browse/BAM-12154> - basically it is the same feature request you would like to have, isn't it? Might be a good idea to add yourself as a watcher/voter to that issue.


author: Daniel Nugent
body: More or less that ticket would do what I'm asking for, yes. Will add myself as a watcher/voter.

Guess I'll try the API too.


author: PiotrA
body: Hi,

I'd try a REST api to obtain a proper branch-plan. AFAIK there is REST resource in Bamboo that for a given master-plan key and for a given branch name will return you in the response the relevant plan-branch key. Probably you could use that to craft the necessary urls by yourself... or maybe not.

The REST resources I'm thinking of are:

\* <http://docs.atlassian.com/bamboo/REST/4.2-SNAPSHOT/#idp85888> plan/{projectKey}-{buildKey}/branch/{branchName}

\* <http://docs.atlassian.com/bamboo/REST/4.2-SNAPSHOT/#idp113040> /plan/{projectKey}-{buildKey}/vcsBranches

regards,


Tags: artefact

branch

build
Unable to perform upgrade on just renewed license.
Asked by Benjamin Joldersma:

I've just renewed my license, and I'm unable to perform my upgrade, this error in the logs:

2012-11-02 13:40:33,596 FATAL main DefaultAtlassianBootstrapManager Unable to run pre-bootstrap upgrade tasks as your support period has ended

2012-11-02 13:40:33,597 INFO main lifecycle Using bamboo.home: /opt/atlassian/home/bamboo

2012-11-02 13:40:33,601 FATAL main UpgradeLauncher Unable to upgrade Bamboo instance as your support period has ended

2012-11-02 13:40:33.601:INFO:oejsh.ContextHandler:started o.e.j.w.WebAppContext{/,file:/opt/atlassian/atlassian-bamboo-4.3/webapp/},webapp

2012-11-02 13:40:33,635 INFO main DefaultConfiguration Loading global messages from com.atlassian.bamboo.ww2.BambooActionSupport

2012-11-02 13:40:33,635 INFO main DefaultConfiguration Loading global messages from help-paths

2012-11-02 13:40:33.720:INFO:/: CompressingFilter/1.4 CompressingFilter has initialized

2012-11-02 13:40:33.775:INFO:/:org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok)

2012-11-02 13:40:33,777 INFO main AccessLogFilter AccessLogFilter initialized. Format is: \<user\> \<url\> \<starting memory="" free="" (kb)=""\> +- \<difference in="" free="" mem="" (kb)=""\> \<query time="" (ms)=""\>

2012-11-02 13:40:33.852:WARN:oejuc.AbstractLifeCycle:FAILED SelectChannelConnector@0.0.0.0:8085: java.net.BindException: Address already in use

java.net.BindException: Address already in use

at sun.nio.ch.Net.bind(Native Method)

at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:137)

at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)

at org.eclipse.jetty.server.nio.SelectChannelConnector.open(SelectChannelConnector.java:182)

at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:311)

at org.eclipse.jetty.server.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:260)

at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)

at org.eclipse.jetty.server.Server.doStart(Server.java:272)

at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)

at com.atlassian.bamboo.server.Server.main(Server.java:75)

2012-11-02 13:40:33.853:WARN:oejuc.AbstractLifeCycle:FAILED com.atlassian.bamboo.server.Server@17332b63: java.net.BindException: Address already in use

java.net.BindException: Address already in use

at sun.nio.ch.Net.bind(Native Method)

at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:137)

at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:77)

....

Any thoughts? Does it just take some time for the license renewal to fully propagate?

cheers


Answers:
author: Septa Cahyadiputra
body: Hi Benjamin,

Before you upgrade your instance, have you update the license with your new license which is accessible from <http://my.atlassian.com/>. Judging from the above logs, you might want to change the port of Bamboo as well as it mentioned that the [address already in use](https://confluence.atlassian.com/pages/viewpage.action?pageId=196837806).

Hope it helps.

Cheers,  
Septa Cahyadiputra
Compiling OpenGL with a Bamboo remote agent
Asked by John Bowker:

I've encountred an issue with compiling applications that use opengl 2 or higher.

I've done some research and it appears that when a remote session is invoked on Windows opengl is reverted to version 1.1 as this version is compatible with how Microsoft implements a remote session.

Is there any way around this with Bamboo. Can I enable the remote agent to start in a certain mode that allows OpenGL 2.0 and higher? Has anyone else overcome this problem?


Answers:
author: John Bowker
body: Okay so it seems its due to the Bamboo agents being NT services. I started them using the batch start and opengl reports the correct version.

Is there anyway to configure the Bamboo service to run in the foreground?


author: James Dumay
body: Unfortunately its not possible to run NT services in the foreground - you will have to configure your machine to autologin and start up the Bamboo agent in the console.

comments: author: John Bowker
body: Thanks for the confirmation.


Tags: remote-agent

server

windows
How can I run a script with custom requirements from Bamboo OnDemand
Asked by Iwein Fuld:

I've created a Testacular config file that I can use locally to output JUnit like test results. Now I want to integrate that in a plan in Bamboo.

I'm seeing the error: No agents meet the Job's requirements. This Job cannot be built in the Elastic Cloud.

I've created a custom image that can run Testacular and I'm now trying to connect it to to Bamboo, but so far I haven't been lucky.

The problem is that the bamboo agent scripts work only on an Amazon Linux node, wereas installing Node on such a system is a drag. I've found [http://wkmacura.tumblr.com/post/5511638182/ubuntu-bamboo-ec2-ami](http://wkmacura.tumblr.com/post/5511638182/ubuntu-bamboo-ec2-ami,), which promises it can't be done, but the changes in the scripts there are unfortunately not visible.

Atlassian is not trying to support this, so I'm hoping to find someone that has done this before so I don't have to rewrite all the agent scripts myself.


Answers:
author: Iwein Fuld
body: I've almost solved this now by extending the existing Atlassian AMI. To do this you need to make sure it stays on long anough so that you can work on it. This you can do by commenting out the auto-shutdown from /opt/bamboo-elastic-agent/etc/rc.local. Do this first, then create a snapshot and start that outside of Bamboo for customization.

Then

* checkout, compile and install NodeJS.
* npm install -g testacular
* download PhantomJS and unpack binary and create a symlink to bin/phantomjs in /usr/local/bin

Now I'm still running into trouble with the bamboo agent that seems rather unstable, but since I didn't touch that part it should sort itself out eventually.

I've put up the exact steps in my blog: [Running Jasmine tests with Testacular and Bamboo OnDemand](http://iweinfuld.posterous.com/running-jasmine-tests-with-testacular-on-bamb).


author: catherina lucy
body: Finally, you have to look at outsourcing as one of many arrows in your quiver.

<http://www.jobrequirements.net/>


Tags: cloud
Wrong redirect after logging in with Bamboo behind mod_proxy
Asked by Radek Antoniuk:

I have Bamboo running on a different host and masked behind an apache mod_proxy.

The problem is that during login to Bamboo, it redirects to wrong URL: /error/HTTP_NOT_FOUND.html.var

I tried running it in the "standard way" and currently running through jetty.

Anyone had that problem and has some non-invasive workaround?

I could obviously alias this to bamboo directly, but ... that's so wrong.


Answers:
author: ArmenA
body: Hey Radoslaw,

Thanks for the question. Please have a look at [this page](https://confluence.atlassian.com/display/BAMKB/Running+bamboo+behind+apache+httpd+proxy) and confirm if you have followed the steps mentioned there. Also, you can try to clean your web browser cookies and reproduce the problem. After, check what URL you see in the cookie that gets saved into your browser (browser settings -\> cookies -\> locate Bamboo cookies). Is that a correct URL?

Cheers,  
Armen

comments: author: Radek Antoniuk
body: Yeap. This is exactly the scenario I am running. The cookies are fine.

It just seems that Bamboo renders the wrong redirection because I can see during the login: os_destination=%252Fstart.action which is /start.action instead of /bamboo/start.action.

If I go again directly to /bamboo/ though, I am logged in, so just the initial redirection is broken.


author: Radek Antoniuk
body: Solved it, using SSO authentication between Crowd and Bamboo (thus avoiding the problem a bit).


Tags: mod_proxy
[Bamboo] How to cleanup maven local repository on agent?
Asked by Shijun Kong:

I am happy to find out that Bamboo is capabile of isolation maven local repository on each agent. Now I have a problem how to clean up maven local repository on an agent (better, if there is a way to automatically wipe out after each build).


Answers:
author: Przemek Bruski
body: You can create a Final Task (as a regular script task) that will remove the repository, there's no automated way of doing it.

comments: author: Shijun Kong
body: I see. Thanks.


author: bjartenilsen
body: How do you access the variable of local repo in a script when it's isolated? The expression

```
$BAMBOO_HOME/.m2/AGENT-${agendid}/repository
```

from <https://confluence.atlassian.com/display/BAMBOO/Configuring+repository+isolation+for+Maven+executables>

Gives me an null-string for the ${agentid} part when used in script


author: PiotrA
body: Hi Bjarte,

just to be sure we're on the same ground: are you using ${agentid} or ${bamboo.agentId} (note the 'bamboo.' prefix and the uppercase 'I' in the 'Id' part) ? That said, I think the <https://confluence.atlassian.com/display/BAMBOO/Configuring+repository+isolation+for+Maven+executables> is outdated a bit - could you confirm whether the ${bamboo.agentId} substitution does work for you? If yes, I'd update the docs.

cheers!


author: bjartenilsen
body: ${bamboo.agentID} works.

My inline script contains:

1. echo \*\*\* SCRIPT START \*\*\*

2. echo Repo: $BAMBOO_HOME/.m2/AGENT-$AGENTID/repository

Environmant variables settings on job:

AGENTID=${bamboo.agentId}

Build result.

|----------------------|----------------------------------------------------------|
| 20-Mar-2013 13:00:49 | Running pre-build action: Maven Settings Prebuild Action |
| 20-Mar-2013 13:00:49 | Substituting variable: ${bamboo.agentId} with 20709377   |

20-Mar-2013 13:00:50 \*\*\* SCRIPT START \*\*\*

20-Mar-2013 13:00:50 Repo: /dnb/data/bamboo-home/.m2/AGENT-20709377/repository

using Bamboo 4.3.2 build 3402 -28 Nov 12

Thank you


author: tomas.bohunek
body: Hi guys.

This command

echo Repo: $BAMBOO_HOME/.m2/AGENT-${bamboo.agentId}/repository

shows me:

```
Repo: /.m2/AGENT-32047106/repository
```

Env. variable AGENTID=${bamboo.agentId} is set correctly. I think correct output should be */home/bamboo/agent1-home/.m2/AGENT-32047106/repository*

Where do I have issue? Thanks for some response.


author: bjartenilsen
body: You should look into Maven dependency plugin. It has a purge local repo goal. ( <http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html> )

Put it in your maven pom of your project - and it will always delete all the dependencies your project depends on from local repo, and redownload them prior to building.


Tags: maven
Bamboo plan and branch variables
Asked by Ferenc Deak:

I have defined a plan variable (buildArguments) as being a list of parameters that are passed into a build script as

```
bamboo_build.sh ${bamboo.buildArguments}
```

(bamboo_build.sh is a script that is being checked out from the repository and it basically executes cmake with the given build arguments), on the Build Stage -\> Tasks -\> Build

Now, we have created a branch of our application which needs a different set of buildArguments, so I have created a variable in the branch too, the same name, with different values. But to my greatest surprise this is not overriding the plan variables, but is passing in the value of the new variable as extra environment variables to the script, which still gets the variables as arguments from the plan. Obviously my build process is not working anymore.

How can I override the plan variables in a branch?


Answers:
author: Xabier Davila
body: Can anyone point me to the bug issue in Atlassian support? I'm interested in branch variables, and would line to know if this has been resolved.


author: PiotrA
body: Hm... I'm worried you had encountered some bug in Bamboo. Especially the discrepancy between what is passed to the bamboo_build.sh and what is passed to the environment is worrying me. Can you raise your issue on <http://support.atlassian.com> ? I think Atlassian Supporters can help you in investigating this issue and fixing the problem. What do you say?


author: Ferenc Deak
body: Ok, I will open one support request!

Thanks


author: Ferenc Deak
body: Bamboo:

Version 4.0.1  
Build Number 2907  
Build Date 4/12/12  

Sorry for the big screenshots ...

Here is the plan configuration regarding the variables:

![](../../upfiles/bamboo_plan_variables.png)

here is the branch configuration regarding the variables:

![](../../upfiles/bamboo_branch_variables.png)

Here is the task configuration:

![](../../upfiles/bamboo_task_config_1.png)

and here is the output when running the build:

![](../../upfiles/bamboo_make_process.png)


author: PiotrA
body: Hello Ferenc,

You say: " so I have created a variable in the branch too, the same name, with different value" - may you elaborate a bit how exactly you'd done that? Maybe a screenshot illustrating the configuration you use?

From your description it seems to me that you're doing exactly what you should in order to make the Bamboo use variable value from the Bamboo-Branch... So... Either you're encountering a bug (which Bamboo version do you use?), or there is some misunderstanding...


Tags: variable
Bamboo OnDemand plan won't start on commit to OnDemand Subversion
Asked by Sergey Morkovkin:

We are trying to establish continuous integration, but for some reason nothing is triggered when code is commited to SVN. We use Bamboo OnDemand and SVN OnDemand. Plan is configured to be triggered on code commit. Should we somehow configure SVN hooks as well to make this work?


Answers:
author: Michael Knight
body: Bamboo should be configured to poll the repository for new commits. I believe this is the default but it's possible it was changed by somone, so it would be worthwhile checking your plan configuration.

If it looks like it's configured appropriately, please raise a [support request](https://support.altassian.com) and we'll look into it further for you.

comments: author: Sergey Morkovkin
body: Occasionally, I've discovered it's actually working. However, it doesn't start on every commit. Is there a setting that control this behavior? We only have 1 Elastic Instance. May this be the cause?


author: Sergey Morkovkin
body: It actually triggered automatically only once. More than 15 commits were ignored.


author: Sergey Morkovkin
body: For some reason [support.atlassian.com](http://support.atlassian.com) doesn't respond. Is this at my end?


author: Michael Knight
body: I'm not aware of any recent outage with our Support site. You could try this link to check:

* <http://www.downforeveryoneorjustme.com/support.atlassian.com>


Tags: cloud
Enabling Pipeline in Bitbucket Cloud using REST API doesn't work suddenly
Asked by Akshay b:

I have been enabling the Bitbucket Pipeline using REST API.

![error.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/169168iBAAC701364936C74/image-size/large?v=v2&px=999 "error.JPG")

It was working fine for more than a year. But for the last couple of days, I am not able to enable the pipeline. It gives me the below error:  

**ERROR:**

```
{"type": "error", "error": {"message": "Resource not found"}}
```

**CURL:**

```
curl --url "https://api.bitbucket.org/2.0/repositories/{organization_name}/{repo_slug}/pipelines_config" --user XXXX:ZZZZ --request PUT --header "Content-Type: application/json" --data "{\"enabled\": true}"
```

Is there any change in the API?


Answers:
author: Caroline R
body: Hi, [@Akshay b](/t5/user/viewprofilepage/user-id/4025953)!

Thank you for reaching out to Atlassian Community!

I was able to enable Pipelines in a repository using the API you mentioned. By the error message you shared with us, the problem seems to be in the repository. If, for example, I change the repository name for some repo that doesn't exist, I get the same error message:

```
{"type": "error", "error": {"message": "Resource not found"}}
```

With that said, could you please check if the workspace/repository name is correct? If it is, would you mind sharing the workspace/repository name here, so I can check if there is a problem with this repo? You can mask the name with \*\*\*.

Looking forward to hearing from you.

Kind regards,  
Caroline


Tags: bitbucket-cloud

bitbucket-pipelines

cloud

rest-api