youngmon/atlassian-qna huggingface dataset:
Bamboo New Install Won't Start
Asked by Barry Pape:

I just installed Bamboo on Windows Server 2008 R2 64 bit with Java 1.7.0_09-b05, and when running \<bamboo.install.dir\>\\bin\\start_bamboo.bat [](http://localhost:8085/)<http://localhost:8085/>is "unable to connect"

Here's what I'm seeing in the console output:

```
15:06:46,977 |-ERROR in ch.qos.logback.core.joran.action.AppenderRefAction - Could not find an appender named [stdout]. Did you define it below instead of above in the configuration file?15:06:46,977 |-ERROR in ch.qos.logback.core.joran.action.AppenderRefAction - See http://logback.qos.ch/codes.html#appender_order for more details.15:06:46,977 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.15:06:46,977 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@4fb97f90 - Registering current configuration as safe fallback pointJul 31, 2014 3:07:38 PM org.apache.coyote.AbstractProtocol startINFO: Starting ProtocolHandler ["http-bio-8081"]Jul 31, 2014 3:07:41 PM org.apache.coyote.AbstractProtocol startINFO: Starting ProtocolHandler ["ajp-bio-8009"]Jul 31, 2014 3:07:41 PM org.apache.catalina.startup.Catalina startINFO: Server startup in 73531 msException in thread "Distribution initialization" java.lang.NullPointerException        at java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:332)        at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:987)        at org.xwiki.extension.repository.internal.installed.DefaultInstalledExtensionRepository.getInstalledExtension(DefaultInstalledExtensionRepository.java:475)        at org.xwiki.extension.distribution.internal.job.DistributionJob.createNewStatus(DistributionJob.java:74)        at org.xwiki.extension.distribution.internal.job.DistributionJob.createNewStatus(DistributionJob.java:43)        at org.xwiki.job.AbstractJob.start(AbstractJob.java:128)        at org.xwiki.extension.distribution.internal.DefaultDistributionManager$1.run(DefaultDistributionManager.java:165)        at java.lang.Thread.run(Thread.java:722)
```

Any ideas?

Thanks,

Barry

```

```


Answers:
author: Krystian Brazulewicz
body: Barry

I think you should contact Bamboo Support at <https://support.atlassian.com/servicedesk/customer/bsp>


author: Barry Pape
body: The server is a test server, so I've had other applications installed on it, but this is the first time I've installed an Atlassian product on the server. Other than that, I installed Bamboo and ran into the issue, so I uninstalled and reinstalled. But that didn't change anything. Would another app cause the error?  


author: Krystian Brazulewicz
body: Barry

Are you sure this is new clean install? Those error messages looks like coming from 3rd party plugins. Can you confirm that you installed 3rd party plugins?
Create Release with CLI
Asked by V:

I've found no action in the documentation for creating a release. Did I miss something, or is it impossible to create a release with the CLI?


Answers:
author: Bob Swift (personal)
body: Answered here: [**Create** **Release** with Bamboo-CLI](https://bobswift.atlassian.net/wiki/questions/77004907?src=search)


Tags: bamboo-administration
Setting up Path in Bamboo
Asked by Joshua Hulst:

We're using Boxen (on OS X) for our build server setup but are having a hard time getting Bamboo to pick up the binaries it provides. Boxen provides a script that is to be sourced which adds the appropriate directories to the path but Bamboo won't pick those up. We've tried source the environment script in /etc/profile as well as \~/.profile but nothing seems to work.

What needs to be done to add the directories to Bamboo's path?


Answers:
author: Joshua Hulst
body: I wanted to setup the PATH for the entire machine, not just a single job. We use a configuration management tool which places our development tools in a specific location for all machines and wanted to make sure of the commonality for multiple projects too.

The struggle I had was that Bamboo was being started by launchd so none of the Bamboo user scripts were running (.bashrc, .profile, .bash_profile). Once I started editing the launch script in /Library/LaunchDaemons I was able to get it to work (although I did have to switch from /bin/sh to /bin/bash to get the Boxen environment script to source correctly)


author: Gretchen
body: You can add them at runtime as an Environment variable. PATH=%PATH%;/home/...; You'll probably end up doing this at some point anyway to accomodate builds that use different paths (unless you're in a single application environment).


Tags: bamboo-administration
trade depot
Asked by James Youngman:

Exports are failing when a plan uses the Accurev repo


Answers:
author: Nic Brough -Adaptavist-
body: What does the log say the error is?

comments: author: James Youngman
body: {"message":"Repository of type com.luxoft.bamboo.plugins.accurev:accurev is not supported yet.","status-code":500,"stack-trace":  
"java.lang.UnsupportedOperationException: Repository of type com.luxoft.bamboo.plugins.accurev:accurev is not supported yet.\\r\\n  
\\tat com.carolynvs.bamboo.plugin.trade_depot.repositories.RepositoryBuilder.resolveAdapter(RepositoryBuilder.java:64)\\r\\n\\tat co  
m.carolynvs.bamboo.plugin.trade_depot.repositories.RepositoryBuilder.resolveAdapter(RepositoryBuilder.java:36)\\r\\n\\tat com.carol  
ynvs.bamboo.plugin.trade_depot.repositories.RepositoryBuilder.getDefinition(RepositoryBuilder.java:24)\\r\\n\\tat com.carolynvs.bam  
boo.plugin.trade_depot.RepositoryServiceImpl.convertRepository(RepositoryServiceImpl.java:144)\\r\\n\\tat com.carolynvs.bamboo.plug  
in.trade_depot.RepositoryServiceImpl.getRepositories(RepositoryServiceImpl.java:136)\\r\\n\\tat com.carolynvs.bamboo.plugin.trade_d


author: Nic Brough -Adaptavist-
body: Well, there's the answer - it's not supported.


author: James Youngman
body: is support for Accurev planned ?


author: Gretchen
body: If you can access it from the command line just script it. You don't have to use plugins for revision management tools.


author: Andrei Markov
body: What repository type has to do with dumping plan's info? Isn't it just a DB operation?Looks like perforce is not supported either (I am getting similar message). Is there a Jira style board for this project? Where to ask all these questions?
Bamboo php test & deploy add-on
Asked by Maxime Macameau:

Do you have some news about add-on for php in bamboo ?


Answers:
author: Maxime Macameau
body: do you have any answer for me


author: Maxime Macameau
body: or a Capistrano add-on


author: Maxime Macameau
body: A Phing add-on would be nice.

I think


author: Krystian Brazulewicz
body: ATM we have a dedicated task for PHPUnit. What other integrations do you have in mind?

comments: author: Maxime Macameau
body: do you have any answer for me

<br />


Tags: bamboo-administration
Need help to configure Bamboo 'Build Summary Report'
Asked by Tapashwani Anand:

Dear Team,

I am new to Atlassian. Currenly I have installed Bamboo and Jira trial version and integrated both the application so that I can report bug directly from the Bamboo.

I am facing issue while watching 'Build Summary Report' as that is not as per requirement.

I need below Reporting as mentioned under [](https://www.atlassian.com/software/bamboo)<https://www.atlassian.com/software/bamboo>\>\> TEST \>\> *CI ON THE BRANCH PREVENT DRIFT **QUARANTINE** TESTING AT SCALE*

Please suggest what odon I need to install into bamboo to see desired 'Build Summary Result'

Thanks,

Tapashwani


Answers:
author: Gretchen
body: You will only see the Quarantine option with a failed test. You must have plan admin permissions to quarantine (I think - doc was fuzzy on this).


author: Tapashwani Anand
body: Hi Gretchen,

Thank you for your response.

Currently I am getting below report in Bamboo![](../../upfiles/Report1.1.jpg)

But I am looking for report with Quarantine option, mentioned below![](../../upfiles/Report1.2.jpg)

Please suggest if there any plugin or tricks to acheive Report with 'Quarantine' option enabled.

Thanks,

Tapashwani


author: Gretchen
body: The build summary "report" described in that link is displayed at the end of every build. (failed or successful). It accurately lists all jira issues associated with the build assuming you 1. use jira, 2. identify the jira ticket associated with the code checkin in your checkin comments.


Tags: bitbucket-cloud

build

cloud

summary
solve complex plan dependencies
Asked by Fabian Wagner:

Hello,

we try to switch with our continous integration to bamboo and got a problem with the plan dependencies.

We use one subversion repository that contains multiple projects. One of those is a project which contains a lot of external components that are shared by all the other projects. I set up a plan that is triggered every night and checks out the components and builds them first. After that it triggers all the plans building the other projects using the child-plan dependencies. That works!

But now we need the possibility to manually start a plan of a certain project and run the build-plan for the components !before! the product-plan itself starts (so only the components and the specific project-plan should start). I can't work with blocking dependencies, because they don't work for manually or scheduled triggers.

Is there an other way to realize this kind of dependencies with bamboo?

Thanks,

SMu


Answers:
author: Benedek Farkas
body: Related topic: <https://answers.atlassian.com/questions/325707>

This problem seems still seems to unresolved.


author: Fabian Wagner
body: That might work.

I can't see this option for the trigger type. At the moment we use an evaluation license to test Bamboo. Can this be the reason?

Now another problem came up. We try to make the build process very abstract and capsulate it in a common plan. This plan should be triggered by a couple of other plans representing the certain projects. Each of those should set a couple of variables and the common build plan builds the projects referring to those variables. We do this, because our build-process is pretty complex and we try to avoid redundant plans for multiple projects. What is the best way to exchange those variables between the project plans and the common plan?


author: Marcin Gardias
body: \>I can't work with blocking dependencies, because they don't work for manually or scheduled triggers.

How about setting Polling trigger with cron expression set in the past? It will never actually start the build but, combined with dependency blocking, will make your project build check the library repository for changes and launch it if necessary.

(you need Bamboo version which supports multiple triggers obviously)


author: Fabian Wagner
body: ok, thank you.

Yes, there is a risk. We've got several commits every day in every project as well as in the components part of the repository. Then there are the Nightly Builds, that are triggered at a certain time. But when we want to release a new version of a specific product manually, the components need to be up to date and also need to be compiled. We plan to add some automation that tests the compiled products (this takes about 7-8 hours) after every nightly build. So more than one (automated) build per day is not possible.


author: Krystian Brazulewicz
body: ATM you can't trigger another plan as a part of your build.

My question is: why do you need to trigger the components-plan before your project-plan? Is there a risk that artifacts in latest build are outdated? Is it possible to run components-plan more frequently (after each commit?)
Bamboo github configuration using ssh
Asked by Me Me:

I've tried many different configurations with the goal of configuring a GitHub account to use ssh authentication in Bamboo version 5.5.1. For the repository host I'm using "Git" instead of "GitHub", since the GitHub option requires a username and password.

For the repository URL this seems correct: [ssh://git@github.com:path/to/project.git](ssh://git@github.compath)

The Authentication Type is set to "SSH private key" and I uploaded the private key to use. The build fails though, with the error "(java.lang.IllegalArgumentException : Unknown RepositoryDefinition 393240)". I've confirmed on the host that cloning the repo over ssh works, and I'm out of ideas on how to correctly configure this repository URL after doing many variations of the patterns at [](https://confluence.atlassian.com/display/BAMBOO/Git)<https://confluence.atlassian.com/display/BAMBOO/Git>

Any help is much appreciated!


Answers:
author: cbenard1
body: Hi All,

I believe the github SSH address looks something like this:

```
git@github.com:toolbelt/test.git
```

Could you edit your URL to remove the "ssh://" and attempt to process the build again? Please let me know the resuls and we'll go from there.

Thanks!

Turner

comments: author: Me Me
body: Yes that was the pattern I started with and it wasn't working initially. I changed back to it last week and for whatever reason it has started working today, so I can confirm it works for GitHub. Thank you for the feedback.


Tags: bamboo-administration
artifactory plugin does not work with bamboo 5.6
Asked by Eusebio Del Rio:

When will the artifactory plugin be updated to work with bamboo 5.6?


Answers:
author: Eusebio Del Rio
body: If you rebuild the artifact from the github repository it will now work. I was able to rebuild the artifact and deploy successfully on bamboo 5.6.

<https://github.com/JFrogDev/bamboo-artifactory-plugin/issues/6>
During auto-merge how we can avoid merge conflict as many developers working on the same project?
Asked by SGD:

Interested in using Bamboo's pre-build merging feature, but wondering what happens if there are merge conflicts.


Answers:
author: SGD
body: Actually, I'd say you should *embrace* the merge conflict! The sooner you discover them, the easier they are to deal with. The great thing about pre-build merges is that they surface both merge conflicts *and* integration conflicts.

If merge conflicts do arrise, the build will fail at that point. From there, you can either resolve the merge conflicts or disable auto-merging, then re-run the build.


Tags: continuous-delivery
Exeption when try to export Bamboo
Asked by Ismael Silvestre:

Hi,

I'm getting this error when I try to export Bamboo: Export has failed. Errors encountered while exporting: Exception initializing proxy: \[com.atlassian.bamboo.resultsummary.BuildResultsSummaryImpl#22282267\].

I'm using Bamboo 5.3


Answers:
author: Felipe Kraemer
body: Hi Ismael,

It looks like the database has become corrupted for some reason.

We have a KB that explains how this corruption can be cleaned:

[](https://confluence.atlassian.com/display/BAMKB/Database+Corruption++-+Bamboo+export+fails)<https://confluence.atlassian.com/display/BAMKB/Database+Corruption++-+Bamboo+export+fails>

The queries might be outdated, though...

I would suggest you to:

1. Shutdown Bamboo;
2. Create a database dump;
3. Try to use run the queries meant for "Bamboo 4.1.2 and 4.4.5";

* If all the queries get executed without issues, it means that the corruption has probably been cleaned, so it should be fine to start Bamboo again.
* If they fail, restore the database dump to get you up and running again, open a [Support](https://support.atlassian.com) ticket and attach the database dump to the ticket, and also let us know what is the database type (MySQL, Oracle, etc). You can also mention this Answers thread.

Kind regards,  
Felipe Kraemer  
Atlassian Support


Tags: bamboo-administration

moderators
How to handle version numbers in Bamboo?
Asked by Robert Dailey:

Using Bamboo, our build jobs compile version numbers into our actual program (We build an APK for Android) and also modify some other data files with the version number. The version number is generated via variables in the plan.

Deployment is confusing. You deploy previously completed builds, but Deployment Project settings also allow you to setup a versioning scheme. Why does the build process not use a versioning scheme? The Deployment project does not initiate a brand new build to use the scheme, so what is the purpose of the versioning settings in the deployment project? Those wouldn't be used since we already setup our version number during the build steps.


Answers:
author: Ron Chan
body: +1

IMO, the end to end functionality of Bamboo's deployment projects just wasn't thought out very well. It leaves users wanting so much more and I'm not talking about bells \& whistles. Seems it wasn't created with a users perspective in mind, which makes it extremely frustrating to use.
New Bamboo 5.6.0 Stash Integration
Asked by Kyle Nicholls:

I have just updated to Bamboo 5.6 and I have an application link to Stash 3.1.

In the release notes Stash is supposed to be able to trigger bamboo builds instead of polling. Also branch detection is supposed to be automatic. I cannot get either of these features to work. In Bamboo I have branch detection enabled and the Stash Repository trigger. It actually doesn't detect any branches at all now.

Am I missing something or is there a bug?


Answers:
author: Tobias L?bermann
body: For everyone who have the same Problem with Bamboo version 5.6. It is possible that the option "Stash repository triggers the build when changes are committed" doesn't work. There is a Bug related to this issue: <https://jira.atlassian.com/browse/BAM-14952>

The issue was fixed in version 5.7.

comments: author: Pascal
body: I'm still having this problem with v 5.7.2. and Stash 3.6.0. Any ideas?


author: Krystian Brazulewicz
body: Is your applink bidirectional and configured to use OAuth as mentioned on <https://confluence.atlassian.com/display/BAMBOO/Stash?>

comments: author: Kyle Nicholls
body: Yes both apps are using OAuth. I also have basic access configured which I think was required for Stash notifications. Would I need to disable that?


author: Krystian Brazulewicz
body: Please disable it just to see if it changes anything. If it continues to fail please contact support


author: Gary Kennedy
body: Can I get a status update on this please?I'm having the same issue, and I don't want to re-create the issue if it already exists (and hopefully solved).


author: Krystian Brazulewicz
body: Gary please check your application link authentication configuration. If it uses only OAuth and still doesn't work then please contact support (in your support request describe your network configuration especially if you use any proxies)


author: Tobias L?bermann
body: Just for documentation, I have the same problem with same Bamboo and Stash versions. My application links are configured with OAuth only, but it still doesn't work. If anyone has fixed it already, please give an update!I will open a support request too.


Tags: bamboo-administration
Deployment Projects - Dependencies
Asked by Radek Antoniuk:

Do the Deployment Projects support dependencies?

I.e. I want to run some plan as an effect of successful deployment project plan.


Answers:
author: Krystian Brazulewicz
body: It is not supported out of the box. However you can trigger a plan by calling REST API or simply POSTing to triggerManualBuildAction

comments: author: Radek Antoniuk
body: Krystian, will you file an enhancement task for me to support this as a task or in another way or should I do it. It would be nice to have it available out of the box, the REST API will work, but it is a hackish way :)


author: Bhagyashree
body: PlanRunners for Bamboo plugin lets you trigger Build as well as Deployment plans from each other.

<https://marketplace.atlassian.com/plugins/com.mdb.plugins.planrunners/server/overview>


Tags: bamboo-administration
Disable remote agent shutdown
Asked by V:

I just noticed today that whenever you shutdown your main Bamboo-Server all the remote-agents are shut down too. Is there a way to disable this behaviour?


Answers:
author: Przemek Bruski
body: No, the agents will restart.

comments: author: V
body: When we did a maintenance shutdown this night the remote-agents didn't restart together with the bamboo-server. Are there any steps we have to take to ensure that the remote-agents will restart?


Tags: bamboo-administration
Bamboo does not show all repositories
Asked by DevopsD:

Bamboo is not not displaying all the repositories, when clicking on "Load Repositories" when trying to add a new repo. Any hints what might be the issue?


Answers:
author: neeraj.mendiratta
body: We are using the cloud version - [aetndigital.atlassian.com](http://aetndigital.atlassian.com)and linking github repositories.


author: Krystian Brazulewicz
body: What repository type are you using? What Bamboo version?


Tags: cloud
How to generate extent report in bitbucket pipelines post build completion.
Asked by Sandeep.Dash:

I have created a CI/CD pipeline for my automation test cases which uses java as the technology \& maven as the build tool. I want the extent report to be generated post build completion irrespective of build fails or not. Please let me know how to integrate this with the pipeline


Answers:
author: deepa
body: Hi [@Sandeep.Dash](/t5/user/viewprofilepage/user-id/4309840) , how to resolve this?

Even I'm facing the same problem. I can see artifacts section and able to download tar gz file..but unable to open and see


author: Sandeep.Dash
body: Hi [@Ankit Gupta](/t5/user/viewprofilepage/user-id/4704323) - I do see the artifacts section in the log file. I am able to download it as well however the file is a rar .gz extension file. How do we view it?


author: Sandeep.Dash
body: [@Ankit Gupta](/t5/user/viewprofilepage/user-id/4704323) When i run the code in local, extent report gets generated post the execution of code in a folder named as TestReport. I want the same to happen when the build gets completed in bitbucket pipelines.

Please let me know if there is a way to make changes in yml file and see the extent report getting generated in the TestReport folder.


author: Ankit Gupta
body: I haven't integrated with the maven tool in Bitbucket Pipeline, but maybe you are looking to [save the artifacts](https://support.atlassian.com/bitbucket-cloud/docs/use-artifacts-in-steps/) from the extent reports generated in the test step.

comments: author: Sandeep.Dash
body: [@AnkitGupta](https://community.atlassian.com/t5/user/viewprofilepage/user-id/4704323) When i run the code in local, extent report gets generated post the execution of code in a folder named as TestReport. I want the same to happen when the build gets completed in bitbucket pipelines.

Please let me know if there is a way to make changes in yml file and see the extent report getting generated in the TestReport folder.


author: Ankit Gupta
body: Hi [@Sandeep.Dash](/t5/user/viewprofilepage/user-id/4309840)

You can add the below to your \`yml\`:

```
artifacts:
   - TestReport/*
```

You can reference the documentation: <https://support.atlassian.com/bitbucket-cloud/docs/use-artifacts-in-steps/>

It would be available in the "Downloads" Tab in the Pipeline run


author: Sandeep.Dash
body: Hi [@AnkitGupta](https://community.atlassian.com/t5/user/viewprofilepage/user-id/4704323) - I do see the artifacts section in the log file. I am able to download it as well however the file is a rar .gz extension file. How do we view it?


Tags: atl-gruland

bitbucket-cloud

cloud

java

maven

report