youngmon/atlassian-qna huggingface dataset:
No Plugin with key 'com.atlassian.bamboo.plugins.testresultparser:task.testresultparser.junit'
Asked by Guruprasad Achar:

Bamboo Remote agents are upgraded to latest version 6.6.1

Remote agents are setup on two different servers. Agents from one server goes fine while the other throws following error.

Could not execute task 'Test Summary' no Plugin with key 'com.atlassian.bamboo.plugins.testresultparser:task.testresultparser.junit' is installed.

In both servers atlassian-bamboo-plugin-testresultparser-6.6.1.jar is present in plugins/system-provided directory

junit-4.12.jar is present in classpath directory

Tried reinstalling Remote Bamboo agent also.


Answers:
author: Gonchik Tsymzhitov
body: Duplicate of <https://community.atlassian.com/t5/Bamboo-questions/No-Plugin-with-key-com-atlassian-bamboo-plugins-testresultparser/qaq-p/995506>
Procedure found here not working (Creating a custom elastic image)
Asked by Roy Gunter:

I'm trying to create a custom image with a larger root partition and am getting errors following the procedures in this article: <https://confluence.atlassian.com/bamboo/creating-a-custom-elastic-image-289277146.html>

We are running Bamboo 6.1.6. Any tips?

Thanks


Answers:
author: Gonchik Tsymzhitov
body: Hi!

On which steps you got error?

Could you provide the error logs?

Cheers,

Gonchik Tsymzhitov

comments: author: Roy Gunter
body: Hi Gonchik

I'd forgotten I posted here. The problem was mine, in a different area. This error was a red herring. I had a command requiring interaction in the startup script. Using an unattended option fixed the problem.

Roy


author: Gonchik Tsymzhitov
body: Hi Roy!

Okay, sorry for delayed answer

Cheers,

Gonchik Tsymzhitov
Bamboo YAML - how to specify multiple tasks
Asked by Miguel Almeida:

Hi,

I'm having a weird experience while using YAML files for builds and I'm wondering if somebody could shed some light.

With the below YAML as an example I'd expect to have 1 job with 2 steps (both scripted). In reality what Bamboo is doing is creating 2 jobs. If I wanted to create 2 jobs I would've created 2 "- jobs:" lines. This is affecting us because if we have 5 or 6 scripted inputs and one of the middle one fails, the build still is considered successful and I end up with a container running nothing because the build step failed.

project:  
key: AAA  
plan:  
key: BBB  
name: Yelp  
stages:  
- jobs:  
- scripts:  
- dotnet clean  
- scripts:  
- dotnet restore


Answers:
author: Victor Debone
body: Hello [@Miguel Almeida](/t5/user/viewprofilepage/user-id/2415920),

Thank you for sharing your experience with YAML!

The solution in your case is to use another item on the "- scripts:" line, like this:

```
- scripts:
  - dotnet clean
  - dotnet restore?
```

Bamboo will create a single stage with 2 scripts jobs :)

Meanwhile, I see that you're actively using YAML and we are considering some improvements for YAML. We are looking to hear some feedback from customers, so if you could reach me at vdebone@atlassian.com, you could make part of this conversation :)

Victor

comments: author: Robert Armenski
body: Hello [@Victor Debone](/t5/user/viewprofilepage/user-id/1892075),

I stumbled across the same issue while looking at the [YAML Spec Reference](https://docs.atlassian.com/bamboo-specs-docs/6.8.1/specs-yaml.html).

Having the above setup, multiple entries under one scripts entry actually produces **one script task** with multiple lines (tested with the example from [Multiple Jobs](https://docs.atlassian.com/bamboo-specs-docs/6.8.0/specs-yaml.html#multiple-jobs)).

Atlassian Bamboo version: 6.8.1 build 60805 - 13 Mar 19.

Please confirm if this is a bug or an intended feature.

P.S. As the YAML spec reference already has sections for Multiple Stages \& Multiple Jobs, it would be nice to add a section for Multiple Tasks as well. Also, it would be beneficial to have a section about writing multiline elements (using the \> prefix).


author: Victor Debone
body: Hello [@Robert Armenski](/t5/user/viewprofilepage/user-id/3104401),

Thanks for pointing that out. You are right, I couldn't create a job with two script tasks.

This feature is improved in the next version of Bamboo, the 6.9, and it will allow you to create all the variations of script, jobs and stages that are discussed in this question :)

Also, I will include a new example to Multiple tasks in the documentation, alongside some multi-line examples. Thanks for the improvement suggestion

Victor


Tags: yaml
Hello, I've upgraded Bamboo from 6.3 to 6.7 and now bamboo won't start.
Asked by BCS IT:

Hello, I've upgraded Bamboo from 6.3 to 6.7 and now bamboo won't start. I need help resolving this before I upgrade production.

Thanks,  
Sal


Answers:
author: Murthy Mokkapati {Appfire}
body: Hi [@Salvador Farias](https://community.atlassian.com/t5/user/viewprofilepage/user-id/2290728),

Did you follow the [Bamboo Upgrade Guide](https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html) while upgrading your instance from 6.3 to 6.7.

Also please provide the logs from `<bamboo-home>/logs/`atlassian-bamboo.log.

Thanks

Murthy

comments: author: BCS IT
body: Sorry for the very late response. I did follow the guide and had issues with the elastic service not restarting. I will provide the logs as soon as i can.

Sal


author: Yogesh Mude
body: HI [@BCS IT](/t5/user/viewprofilepage/user-id/2290728)

WElcome to the community!

What was the error you are getting?

For more details about the error please check the log files.

comments: author: BCS IT
body: Hello Yogesh, after the services were brought back up, the web browser indicated the site was unavailable.

What logs should I be looking at?

Thanks,

Sal


author: Murthy Mokkapati {Appfire}
body: Hi [@Salvador Farias](https://community.atlassian.com/t5/user/viewprofilepage/user-id/2290728),

Did you follow the [Bamboo Upgrade Guide](https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html) while upgrading your instance from 6.3 to 6.7.

Also please provide the logs from `<bamboo-home>/logs/`atlassian-bamboo.log.

Thanks

Murthy
Bamboo notifications to Slack
Asked by Nishant Gupta:

Hi we have installed bamboo notifications for Slack plugin to send notifications to Slack but unfortunately the notification disappears after working for the first time. We recently migrated from hipchat so please help.

I have tried adding notifications for "All jobs completed, All builds completed, Failed and first successfull build" but getting the same result. It runs for the first time and then the notification disappears.


Answers:
author: Gonchik Tsymzhitov
body: Hi!

How it works your notification?

And which app do you using?

1. [https://marketplace.atlassian.com/apps/1217681/slack-task-for-bamboo?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1217681/slack-task-for-bamboo?hosting=server&tab=overview)

2. [https://marketplace.atlassian.com/apps/1212291/slack-notifications-for-bamboo?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1212291/slack-notifications-for-bamboo?hosting=server&tab=overview)

3. [https://marketplace.atlassian.com/apps/1213289/slack-notifications-for-bamboo?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1213289/slack-notifications-for-bamboo?hosting=server&tab=overview)

4. Or own one based on the webhook ?

I hope the problem related the supporting the slack or another workplace, channel etc.

Cheers,

Gonchik Tsymzhitov
devenv build installer
Asked by Ben:

I am using devenv to build installer in Bamboo, but always get "parameter incorrect" error. Below are the parameters.

Executable: Visual Studio 2017

Solution: src\\build\\MySolution.sln

Option: /deploy Release /project src\\InstallProject\\InstallProject.vdproj


Answers:
author: Gonchik Tsymzhitov
body: Hi!

Have you tried to escaping and set correct?

And is your task cmd based?

Cheers,

Gonchik Tsymzhitov

comments: author: Ben
body: Tried "/deploy Release /project src\\\\InstallProject\\\\InstallProject.vdproj", it did not work.

But if option is "/deploy Release", it builds whole solution exception installer project.
Best Practice - Server Configuration for Bitbucket, Bamboo & Jira
Asked by MGervais_Walkers:

We currently have an existing on-prem instance of Jira Software running and I have been asked to investigate migrating our existing TFS instance to a Bitbucket/Bamboo setup.

My question is this - what is the best practice for this setup in terms of servers? Is it wise to have all 3 of these applications running on the same server and if so, what should the minimum specifications be? Keep in mind that we do not have a large team and I am trying to avoid requisitioning more rack space/servers if we really do not need them.

Thanks.


Answers:
author: Alexis Robert
body: Hi [@MGervais_Walkers](/t5/user/viewprofilepage/user-id/2102168),

there is not a definitive answer here (no official recomandation by Atlassian), but I personnaly think, by experience, that it's better to not have that many services running on the same host as it can lead to:

* performance issues being hard to investigate, as many services means many potential sources of problems
* at least separate the database server from the application server, as they tend to have different needs in terms of ressources (Java applications like Jira will need more RAM, whereas databases will need more storage performance)
* it will also depends on how many users you have on each platform. For example if you have 500 users on Jira but only 25 on Bamboo, it's best to "isolate" your Jira application on a different server so your Bamboo performance is not affected by Jira workload

Let me know if you have any questions,

--Alexis

comments: author: MGervais_Walkers
body: Hi [@Alexis Robert](/t5/user/viewprofilepage/user-id/1213386)

Thanks for the response and, I agree with your assessment. I think it would be best if we kept some separation between Jira and the other server systems.

Thanks.

Marc.


Tags: bitbucket-server

jira-server
Having problems with getting triggers for multiple repositories to work
Asked by Jason Templeman:

We are using Bamboo Server version 6.6.3 build 60607 and I am having issues getting triggers to work. Our project has many repositories and I am trying to create a single plan utilizing branch plans that will trigger a build if there is a change in any of the configured repositories.

For my plan I have 10 "linked" repositories configured under the Repositories tab. Under the Triggers tab I have selected "Bitbucket Server repository triggered" as we are using Bitbucket for our repository management. Under the trigger I have selected repositories 3-9 as these are the only ones I want to trigger on. Under the Branches tab I have chosen "When new branch in repository is created" so I can test just by creating branches in the various repositories. Once working I plan to change this to "When pull request is created".

What I am seeing is that only branch plans are created when I create a branch in the 1st repository in the list. As I stated earlier this is not one of the triggered repositories.

I'm trying to figure out

1. Why is this the only branch plan being created?
2. Why is this being created at all as it is not selected in trigger?

Any help getting this resolved will be greatly appreciated.


Answers:
author: Gonchik Tsymzhitov
body: Hope it helps :)

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

You can vote
No Plugin with key 'com.atlassian.bamboo.plugins.testresultparser:task.testresultparser.junit' is in
Asked by Guruprasad Achar:

Bamboo Remote agents are upgraded to latest version 6.6.1

Remote agents are setup on two different servers. Agents from one server goes fine while the other throws following error.

Could not execute task 'Test Summary' no Plugin with key 'com.atlassian.bamboo.plugins.testresultparser:task.testresultparser.junit' is installed.

In both servers atlassian-bamboo-plugin-testresultparser-6.6.1.jar is present in plugins/system-provided directory

junit-4.12.jar is present in classpath directory

Any solution ?


Answers:
author: Gonchik Tsymzhitov
body: Hi!

Once I have met the same problem, I have upgraded to latest one and before I checked on remote agents then ownership for those bamboo directory.. (just chown -R bamboo:bamboo \* :)

e.g. today is latest is Bamboo 6.8.0, and this is so good one :) We are upgraded yesterday looks like everything works fine.

Otherwise feel free update to 6.7.2 :)

Cheers,

Gonchik Tsymzhitov

comments: author: Guruprasad Achar
body: [@Gonchik Tsymzhitov](/t5/user/viewprofilepage/user-id/726117), As of now the main server hosting Bamboo is 6.6.1. We can only make use of the available version. Hence I will have to try changing the ownership of the remote agent server folder.

Thank you.
The drive that my bamboo is running on is getting full. what can I safely change to use that?
Asked by Robert Webster:

our bamboo drive is almost full. we added a large drive to the application server. what would I need to change to start using the new drive? I need this to be seamless and safe and do whatever will get me the biggest bang for the buck. currently I only have 5gb free out of 50gb.


Answers:
author: Gonchik Tsymzhitov
body: Hi!

1. Logs

2. tmp

3. <https://confluence.atlassian.com/bamboo/configuring-global-expiry-289277253.html>

4. Reset Repo cache <https://confluence.atlassian.com/bamkb/git-cache-removal-in-bamboo-329982070.html>

Cheers,

Gonchik Tsymzhitov


Tags: log

space
Run another build before current build - Build Dependencies.
Asked by peeterkobu:

On a "Plan configuration" page i can select the "Dependencies" tab and set child project to build **after** current build is done.

But..

I need the opposite. I don't want to trigger all my other projects that depends on one project.   

I need to run other plans **before** my current plan, not after.

For example:  
Plan A  
Plan B  
Plan C

<br />

Plan B depends on Plan A

Plan C depends on Plan A

<br />

For now i can set dependencies like that:  
When Plan A is built successfully, trigger Plan B and Plan C.

But, I want:

When i run Plan C, i want to build Plan A **before** Plan C and **then build Plan C** .   

Is that possible?


Answers:
author: Gonchik Tsymzhitov
body: Hi!

Let's cover by Final stage from Bamboo 6.8 release,

and using these plugins

[https://marketplace.atlassian.com/apps/1215235/fail-build-trigger-for-bamboo?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1215235/fail-build-trigger-for-bamboo?hosting=server&tab=overview)

[https://marketplace.atlassian.com/apps/1216136/after-deployment-trigger-for-bamboo?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1216136/after-deployment-trigger-for-bamboo?hosting=server&tab=overview)

Cheers,

Gonchik Tsymzhitov


Tags: bamboo-administration
How to display Jira Issue field values in Confluence page
Asked by Mahesh Pawar:

Hi i am triggering a bamboo build using Jira WebHook

**https://user:pass@bambooserver/rest/api/latest/queue/RT-ENV?os_authType=basic**

Now i also want to pass values like ${issue.key} to that bamboo.

Once triggered i need to print those value in job.

How can i do that.

Thanks in advance


Answers:
author: Mahesh Pawar
body: Solution for above issue i wrote a rest API script in bamboo first task\[which will get triggered via same webhook\].

which basically get all details \& fields values of that particular Jira.

comments: author: Gonchik Tsymzhitov
body: Congrats!


author: Gonchik Tsymzhitov
body: Hi!

I have covered by this python module <https://pypi.org/project/atlassian-python-api/>

Cheers,

Gonchik Tsymzhitov

comments: author: Mahesh Pawar
body: Seems interesting [@Gonchik Tsymzhitov](/t5/user/viewprofilepage/user-id/726117)


Tags: jira

webhook
Unable to Create application link between Bamboo & Bitbucket
Asked by Rahul Khandelwal:

Hi Team,

We are not able to add the Repo when we choose Bitbucket Server as Repository Host in Bamboo whereas it works when we choose GIT . In Bamboo v6.0+ there is an option which allows the Build to be triggered on the Pull request

For this to happen, we need to create an application link between Bamboo \& Bitbucket server.As per the application matrix published by Atlassian, we won't be able to create an application link between our versions (Bamboo v6.4 \& Bitbucket server v5.9). Please refer to the below link for further reference

<https://confluence.atlassian.com/applinks/application-links-version-matrix-779174762.html>

If we Upgrade our Bamboo to v6.5 , will we be able to create the application link Between Bamboo \& Bitbucket.

Also, why do we get the below error when we choose Bitbucket server as the the Host Repo. Is that due to Application linking or is it due to any network restriction. Could you please help us with the analysis we can do to check this

Create repository

Service Unavailable

The service is temporarily unavailable. Please try again later.


Answers:
author: Gonchik Tsymzhitov
body: Hi!

Please, checkout this article

<https://confluence.atlassian.com/kb/application-links-troubleshooting-guide-718668765.html>

Hope it helps

Cheers,

Gonchik Tsymzhitov


Tags: bitbucket

bitbucket-server

server
What does selecting Repository -> "Enable Submodule support" actually do??
Asked by Jorge Suarez:

We have a repo that contains submodules because it makes organizing folder structure compatible with a 3rd party product we are stuck using.

What exactly does this option do?? I know submodules point to a specific commit, not to a branch. But with git there is also the option to add branch = xxxxx to .gitmodules file.

It seems the option runs:

git clone --recurse-submodules

is there a standard way to get each branch to the latest branch develop??

I assume: git submodule foreach --recursive 'git checkout develop; git pull'

Thanks!


Answers:
author: Gonchik Tsymzhitov
body: Hi!

We are facing the same issue.

BTW, we are added git aliases for the standard command which include submodule commands.

Hope it helps

Cheers,

Gonchik Tsymzhitov


Tags: git
YAML support in Specs for multiple plans?
Asked by Jeff_Schaeffer:

Currently two languages are supported for Bamboo Specs, Java and YAML. However, the implementation of these are not equal as the Java side is enabled to work with multiple bamboo plans where the YAML side is restricted to just one.

As we're a non-java shop currently we prefer the YAML side as it simplifies the technology stack (ansible using YAML as well).

When will the YAML side be upgraded to keep in sync feature-wise with the Java side?


Answers:
author: Victor Debone
body: Hello [@Jeff_Schaeffer](/t5/user/viewprofilepage/user-id/2579819),

We are considering some improvements for YAML and we are looking to hear some feedback from customers, if you could reach me at vdebone@atlassian.com you could make part of this conversation :)

Kind Regards,  
Victor


Tags: spec
Permissions to add add-on
Asked by Dorit Mozesh:

Hi,

How can i grant permissions to add add-on

Don't have the "Overview" under configuration.

Also got BigPicture add-on but don'r have permissions to add new project there.


Answers:
author: Scott Theus
body: Hi [@Dorit Mozesh](/t5/user/viewprofilepage/user-id/2637606),

The "Administer Jira" permission has the ability to create projects, so you will need to log in as the site-admin and set the Global Permission to Administer Jira for the user or group that will be creating projects. Here are a couple of links with more information:

<https://confluence.atlassian.com/jirasoftwarecloud/permissions-overview-764478244.html>

<https://confluence.atlassian.com/adminjiracloud/managing-global-permissions-776636359.html>

Only a site-admin can install an add-on product. If you are not the site-admin you'll need to ask that person to install it for you.

Hope this helps,

-Scott


Tags: app

permission
How to send out notifications after each task in deployment is completed?
Asked by Mallika Dasanoor:

I have a scenario where we have a task to run smoke tests after the deployment is successful. We would like to know if the deployment failed or if the smoke tests task failed. So, would prefer to receive email notification from bamboo saying deployment is successful and smoke tests task is starting.

Can we accomplish this?


Answers:
author: Jobin Kuruvilla [Adaptavist]
body: You might want to create a separate build for the smoke tests and add it is a child build of the original deployment build.

That way, you can configure separate notifications for the builds. Also, the smoke tests won't be triggered if the deployment failed. Would that help?

comments: author: Mallika Dasanoor
body: Thanks for the reply. But the way we have it set up is that we have a build plan which generates the artifacts and we have a deployment plan set up which is tied to that build plan. once we have a successful build, the deployment is triggered. I dont see an option to set up dependencies for a deployment plan like we have it for build plans. Am i clear? If not i can try to explain it in more detail. Let me know. Thanks!


author: Jobin Kuruvilla [Adaptavist]
body: Yeah, that's a bummer. You can work around by defining a new environment in the same deployment project that just does the smoke tests. And it can have a trigger to start after the successful deployment of the actual deploy.

It is not pretty as environments are meant for deploys not tests but it is a workaround.

Another option is to use a script task in the deployment to trigger the test plan using the REST API.


author: Mallika Dasanoor
body: **Yeah, that's a bummer. You can work around by defining a new environment in the same deployment project that just does the smoke tests. And it can have a trigger to start after the successful deployment of the actual deploy**. .\>\> I just checked and there is no trigger based off a successful deployment .. but there are triggers based of off successful builds ...

Do you have an example script using REST API? I am fairly new to this approach and would like to customize based of your sample.

But thank you so much. You have been extremely helpful!!


author: Jobin Kuruvilla [Adaptavist]
body: > I just checked and there is no trigger based off a successful deployment

Did you check the trigger in a deployment env? I was talking about adding a new env and then add a trigger on it to start the env tasks as soon as the actual deploy is done.

Env1: DEV DEPLOY

Env2: DEV SMOKE TEST

DEV DEPLOY will be triggered by the build. DEV SMOKE TEST will be triggered after a successful deploy of DEV DEPLOY.

Again, as I mentioned, a deploy to DEV SMOKE TEST is a bit odd given that it won't be deploying anything. It will just be doing some tests.


author: Mallika Dasanoor
body: I see what you are saying and I could see that trigger show up when I added the 2nd environment. When it was just one environment, the trigger did not show up and thats where i was confused. Thanks again!