youngmon/atlassian-qna huggingface dataset:
JMeter Aggregator for Bamboo Plugin - "The add-on couldn't be loaded"
Asked by Anil Jindal:

Hi,

The install of jmeter plugin is not working for me, we receive an error "plugin couldn't start due to some error". Checkout the screenshot below. Please assist with the resolution.

![Bamboo_JMeter.png](/t5/image/serverpage/image-id/101398i9C7D70B864DB3574/image-size/large?v=v2&px=999 "Bamboo_JMeter.png")


Answers:
author: Alexey Chystoprudov
body: See exception at Bamboo logs

comments: author: Anil Jindal
body: Had a look in bamboo logs, no exceptions observed there.


author: Alexey Chystoprudov
body: Then search logs for "atlassian-bamboo-jmeter-aggregator" string


author: Anil Jindal
body: Log shows following relevant entries, no exception indicated.

2020-07-01 21:42:08,647 INFO \[http-apr-8085-exec-1\] \[AccessLogFilter\] GET <https://bamboo.url.io/rest/plugins/1.0/atlassian-bamboo-jmeter-aggregator-5.14.0.jar-key/media/plugin-icon> 1203131kb  
2020-07-01 21:42:18,134 INFO \[http-apr-8085-exec-35\] \[AccessLogFilter\] GET <https://bamboo.url.io/rest/plugins/1.0/atlassian-bamboo-jmeter-aggregator-5.14.0.jar-key?_=1593603719102> 769495kb  
2020-07-01 21:42:18,175 INFO \[http-apr-8085-exec-6\] \[AccessLogFilter\] GET <https://bamboo.url.io/rest/plugins/1.0/atlassian-bamboo-jmeter-aggregator-5.14.0.jar/marketplace?_=1593603719103> 769187kb  
2020-07-01 21:42:18,216 INFO \[http-apr-8085-exec-9\] \[AccessLogFilter\] GET <https://bamboo.url.io/rest/plugins/1.0/pac-details/atlassian-bamboo-jmeter-aggregator-5.14.0.jar/0.0?_=1593603719104> 768380kb


Tags: jmeter
Bamboo Build User Switched
Asked by Karanpaul Multani:

All my build plans are failing after migration. Now all the plans are running as root vs Bamboo. I have looked everywhere to figure out what's going on but any help would be greatly appreciated.


Answers:
author: Daniel Ebers
body: Hi Karanpaul,

welcome to the Atlassian Community!

You mentioned a migration - do you mean by that a migration from one server to another took place? Could you please explain further what was done?

You mentioned it seems that Bamboo is now executing the build plans as root. Did I get it right that you are running Bamboo itself under 'root' account? If so, you could alternatively run Bamboo with a dedicated account - assuming you a using a linux distribution.

Any more details might help for experts here in community to catch up.

Cheers,  
Daniel
How do I add git capability to agent for Per Build Container builds?
Asked by Jason Templeman:

We are working to get our Bamboo builds running in a K8s cluster. We have the PBC plugins installed and configured, sidekick image created and our test plan seemS to be running OK (within OpenShift) but when the Source Code Checkout task executes, getting our source code from Bitbucket, I see the message "Submodules handling requested but no native Git capability defined for agent. Please define native Git capability for agent to use submodules." in the log file.  

I've created a new sidekick image adding:  

/buildeng/bamboo-update-capability "system.builder.command.Git" "/usr/bin/git"  

to the file setup.sh and added:  

Add setup.sh /buildeng-custom/  

to the Dockerfile  

I then ran the container locally via docker run and verified that the file and contents were there and in the correct location.  

docker run --rm -it bamboo-agent-sidekick  
# cat buildeng-custom/setup.sh  
# GIT capability  
/buildeng/bamboo-update-capability "system.builder.command.Git" "/usr/bin/git"  

When I re-run the job I'm still getting the same error.  

Can someone tell me how configure the system this so that I can do submodule updates?  

Thanks  

<br />

<br />

<br />

<br />

<br />


Answers:
author: Duke
body: I am not sure about "system.builder.command.Git". Have you tried "system.git.executable"?

```
/buildeng/bamboo-update-capability "system.git.executable" "/usr/bin/git"
```

See [Submodules handling requested but no native Git capability defined for agent. Please define native Git capability for agent to use submodules](https://community.atlassian.com/t5/Bamboo-questions/Submodules-handling-requested-but-no-native-Git-capability/qaq-p/422041) for more details.

comments: author: Jason Templeman
body: Thanks. That seemed to get one step further. Now getting "Permission denied (publickey)". We are using linked libraries and I have tried saving the repository configuration to refresh the authentication details multiple times as well as putting the access key into Bitbucket manually without avail.  

Any thoughts?


author: Duke
body: It's great that "system.git.executable" got you one step further. Now it looks like you hit the issue discussed in [BAM-11369](https://jira.atlassian.com/browse/BAM-11369). I suggest trying the workaround in [Permission denied (publickey) submodule after upgrade](https://community.atlassian.com/t5/Bamboo-questions/Permission-denied-publickey-submodule-after-upgrade/qaq-p/1134023).


author: kkundi
body: Can you please share your Helm chart? We may suggest for you some cloud-native recommendations (using initContainers, configmap,... instead of building image on top of the official image, ... so on) ?
Configure Bamboo Branch Naming Convention
Asked by jake_naughton:

At the moment, when an automated bamboo branch is added, it is named after the git branch. For example:

**feature/XX-1234**

becomes:

**feature-XX-1234**

Is there away to change the automated naming convention? In my particular case I would like the branches to include the original creators name:

{branchName}-{user.name}

example:

**feature-XX-1234-john.doe**

This would help developers in our team be able to identify which branches are theirs. We all so send broken builds to a slack channel for back merging and need to alert the correct developer, doing this off the last person to commit is not always accurate here.

Unsure of how to achieve this? Happy to install any plugins


Answers:
author: Lasse Langhorn
body: Hi [@jake_naughton](/t5/user/viewprofilepage/user-id/2146620)

Would it be possible to add the the name of the creator as a suffix to the git branch when created? Then it will propagate to Bamboo.

Otherwise you will have to create the branch manually in Bamboo and then choose the display name.

Regards

Lasse Langhorn

comments: author: jake_naughton
body: *[@Lasse Langhorn](/t5/user/viewprofilepage/user-id/1261572)*

*Would it be possible to add the the name of the creator as a suffix to the git branch when created? Then it will propagate to Bamboo.*

We thought of this, it would make our branch naming far too messy.

*Otherwise you will have to create the branch manually in Bamboo and then choose the display name.*

This is kind of what we are doing, once they get automatically created we change the branch display name to include the devs name. Anything that requires manually work however is a pain. It would be optimal if we could automate this. If it is not possible are there any future plans to implement this feature?
Ignore build trigger of Bitbucket repository in YAML specs
Asked by fstr:

I'm running Bamboo 7.0.4. I have defined my build plan as YAML specs.

The build plan is connected to multiple linked repositories hosted on Bitbucket Server. One of them is the main repository which should trigger the build. The others are checked-out to fetch some configuration files. I'm using the [repository-checkout task](https://docs.atlassian.com/bamboo-specs-docs/7.0.4/specs.html?yaml#task-repository-checkout) for this.

After setting up this configuration, a commit to any linked repository will trigger a build.

Is there a way to ignore triggers of linked repositories in the YAML specs?

The YAML specs manual states (section [triggers](https://docs.atlassian.com/bamboo-specs-docs/7.0.4/specs.html?yaml#triggers)):
> If your plan repository is Bitbucket Server, the Bitbucket Server trigger will be used instead.

The YAML specs manual states (section [repository triggers build on commit](https://docs.atlassian.com/bamboo-specs-docs/7.0.4/specs.html?yaml#repository-triggers-a-build-on-commit))
> On the Bamboo side, use the `triggers(new RemoteTrigger())` on plan definition. By default the remote trigger will react on all triggering repositories defined in a plan. You can limit it by selecting a subset of repositories.

And on the right hand side, the YAML doesn't match this comment:
> A plan listening for events from a `my-repo` repository from `12.34.56.78` IP address.

The manual is quite misleading. Is it currently possible to ignore triggers of linked repositories (ideally by name) in YAML specs?


Answers:
author: Alexey Chystoprudov
body: It's not implemented yet, please vote and watch status of <https://jira.atlassian.com/browse/BAM-20932>

comments: author: fstr
body: Thanks! I'll vote for it in JIRA :)


Tags: link

repository

spec

trigger

yaml
Docker container run, container removed before it is started
Asked by k.habets:

Hi,

I'm using a Docker task in a Bamboo (7.0.2) plan and running the "run a docker container" option.

It looks like my container is either taking too long for Bamboo to see it as a succesful start or maybe no proper return code (?) because the container is removed straight after the execution of the plan.

I tried to introduce a "wait for service" but I don't really have something to check against so even though the container is then started correctly, the plan will still fail and remove the container.

When I just use a script task and execute the same run, all is fine. This looks like a shortcoming in the Docker tasks.

I would like to use the out of the box tooling so if anyone has a suggestion, it's very welcome! Otherwise I'll stick to a script task.

Regards,

Kamiel.


Answers:
author: Mehmet A _Bloompeak_
body: I suggest that you stick to script task because it is under your control and transparent whereas docker task is a black box. In case something goes wrong, there is no hint for the reason of the failure.

comments: author: k.habets
body: Thanks for your answer, that's what I'm doing now. Still would be nice to have the plugin working properly, else why even bother making plugins? I could just script everything.
Getting the logged in user (Bamboo Deployment Project)
Asked by justint:

We're looking to use the current logged in user for the a portion of the deployment script in a Bamboo Deployment project.

May I ask if there is a Bamboo variable for the deploying user for a Deployment Project (not a build plan)?


Answers:
author: Richard White _TechTime_
body: Hi,

I have noticed when I do a manual deployment the variable:

```
bamboo.ManualBuildTriggerReason.userName
```

is set to the deploying user's username, which should hopefully work for your case too?

This variable was not set in the case of automatically triggered deployments.

Usually, the logs of a deployment will show all available variables.

Cheers,

Richard

comments: author: justint
body: Thanks for the idea. I'm going to do some tests and see.

It seems to me that Bamboo distinguishes between Plans and Deployments.

I'll try with different users doing each, see what happens and share the results.


Tags: deployment

user
How is the remote agent "sidekick" container specified when using the Per Build Container plugin?
Asked by Jason Templeman:

I recently had the PBC plugin installed by our IT department. The sidekick image has been created via the script and stored in our registry but not sure where it is used/referenced within Bamboo.   

As an end user, I only have access to edit my plans. I see the addition of the PBC plugin in the isolate build area under the Docker tab and when I select it I see a field to enter a Docker image. The text above the field states "The build is picked up by an agent specially created for the current run and discarded afterwards. The agent will be based on a Docker Image provided." This seems to suggest that the sidekick image should go here but the text below the field says "Docker image to use by the build's tasks. It has to provide all capabilities required by tasks." which seems to indicate the custom image I created that contains my build environment. The Agent Size field also seems to indicate that this field is for the sidekick image.  

That being said, I was told that all the builds would "potentially" use the same sidekick image and if that is the case I wouldn't expect to have to configure it for every single job therefore I'm confused as to where the two images are specified and what goes into this Docker image field. As I understand it there are two containers in the pod with the first one being the sidekick image and the other my build environment image therefore I would expect that if the sidekick image does have to be specified per job (not good as we have lots of jobs) there were be two field for image configuration and not just one.   

Now there is a section for Additional containers to run but my understanding is that would be for a third container in the pod.  

It seems to me that there should be a configuration option somewhere (maybe on the server side so I cannot see it) to indicate the location of the sidekick image so that the plan only has to enter the location for the image actually performing the tasks. Can someone please shed some light at to where the sidekick and my build environment images are referenced?


Answers:
author: Jason Templeman
body: Was able to confirm with those who have access that the PBC sidekick image is specified with the configuration of this plugin.
Detecting errors during build and deployment scripts
Asked by dguisinger:

Hello,

I'm working on a client's build server (a on prem Bamboo install) and the person who originally set it up never got the build and deployment scripts to detect errors from MSBuild or when deploying over the network.

This often leads to us deploying incomplete projects as a microservice may have failed to build, or sometimes our IIS reset doesn't clear file locks or we lose permissions to overwrite our Citrix applications. If you are watching the logs as they fly by, the errors are highlighted in red, but the scripts don't fail and Bamboo says either the build or the deploy was successful.

I am not that familiar with Bamboo myself. Does anyone have any good resources or tips for this particular issue and how I could go about resolving it?

Thanks,

Dan


Answers:
author: Mehmet A _Bloompeak_
body: Hi [@dguisinger](/t5/user/viewprofilepage/user-id/3984892) ,

If it is linux bash script you should set 'set -e' parameter, so that the script will exit on error.

    #!/bin/bashset -e# Any subsequent(*) commands which fail will cause the shell script to exit immediately

If it is Window PowerShell script, you should set $ErrorActionPreference = "Stop" parameter.
buildNumber=latest ?
Asked by abioneperhobby:

[https://my.self.hosted.bamboo/build/result/viewBuildResultsSuccessfulTests.action?buildKey=LSD-WS-JOB1\&pageSize=339\&buildNumber=421](https://bamboo.solutiondocondemand.com/build/result/viewBuildResultsSuccessfulTests.action?buildKey=LSD-WS-JOB1&pageSize=339&buildNumber=421)

i don't want to target the buildNumber=421, i would like to target every time the latest build.

[here](https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html) i don't find possibility to link to the latest build of the plan.


Answers:
author: Mehmet A _Bloompeak_
body: Hi [@abioneperhobby](/t5/user/viewprofilepage/user-id/3616131) ,

Try <https://my.self.hosted.bamboo/browse/LSD-WS-JOB1/latest/test>. It works on my bamboo installation.
Unable to access environment variable in Bamboo Build Plan
Asked by Maryo_David:

I have a Bamboo Build Plan, with the following set of tasks.

1. Source Code Checkout
2. Artifactory Generic Resolve (To Get the zip file from Artifactory)
3. Script (To Extract the contents of zip file and to set to CATALINA_HOME \& PATH environment variable)
4. Ant (For Build)

**Task 3 has the following content in it:**

    APP_HOME=${bamboo.build.working.directory}unzip $APP_HOME/tomcat/apache-tomcat-6.0.45-windows-x64.zipexport CATALINA_HOME=$APP_HOME/tomcat/apache-tomcat-6.0.45export PATH="$PATH:$CATALINA_HOME/bin"

But when I execute 4th Task (Ant), the Build is not considering the CATALINA_HOME \& PATH variable which is set as part of Task 3. What is wrong here? Why am I not able to access the environment variable that is set in Task 3?


Answers:
author: Boris Van Hardeveld
body: Cross-posted (and answered) at: <https://stackoverflow.com/questions/62539690/unable-to-access-environment-variable-in-bamboo-build-plan>
Bamboo build fails when tried to run Tests project visual studio
Asked by Sid Shrivastav:

Hi there,

So, even after installing Visual Studio 2019 on the bamboo build server, we are still running into the Tests project in Visual Studio throwing exceptions when trying to deploy the solution to our development server. To recap, the solution now has a new Tests project which uses .net framework 4.7.2 while all the other projects in the solution use 4.0 .net framework. In order to make sure the tests project run, I had the build server team install SDK .net framework 4.7.2 on the bamboo build server which he did by installing the VS 2019 and bringing back the most recent SDK with the install. Now, when I try to run the build from bamboo including the Tests project, the build fails. I get the error below.

Using shared compilation with compiler from directory: C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\BuildTools\\MSBuild\\Current\\Bin\\Roslyn  
Core\\Configuration\\ConfigurationTests.cs(1,17): error CS0234: The type or namespace name 'VisualStudio' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?) \[D:\\bamboo-home\\xml-data\\build-dir\\WA-BTSBOA-JOB1\\Source\\BOA.Tests\\BOA.Tests.csproj\]  
Core\\Configuration\\ConfigurationTests.cs(2,7): error CS0246: The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?) \[D:\\bamboo-home\\xml-data\\build-dir\\WA-BTSBOA-JOB1\\Source\\BOA.Tests\\BOA.Tests.csproj\]  
Core\\Configuration\\ConfigurationTests.cs(7,6): error CS0246: The type or namespace name 'TestClassAttribute' could not be found (are you missing a using directive or an assembly reference?) \[D:\\bamboo-home\\xml-data\\build-dir\\WA-BTSBOA-JOB1\\Source\\BOA.Tests\\BOA.Tests.csproj\]  
Core\\Configuration\\ConfigurationTests.cs(7,6): error CS0246: The type or namespace name 'TestClass' could not be found (are you missing a using directive or an assembly reference?) \[D:\\bamboo-home\\xml-data\\build-dir\\WA-BTSBOA-JOB1\\Source\\BOA.Tests\\BOA.Tests.csproj\]

When I exclude the Tests project, the build works just fine. What am I missing here? Sorry new to the bamboo.


Answers:
author: Amit Barik
body: Any answer to this ? Is it still open ?


Tags: .net

ms-build
Running Selenium IDE test in Bamboo
Asked by Mikolas Slama:

Hello,

I was wondering what are the steps I need to take run Selenium IDE tests in bamboo. I have read of a plug-in called Charlotte, but I was wondering if there are other methods possible.

Thank you for your replies!


Answers:
author: abioneperhobby
body: Selenium Ide tests can be runned by command line?
Date compare validator is not working for lessthan or equal condition on create transition
Asked by Shanmukha Badana:

Hi anyone,

I'm trying to put a date compare validator with the condition like it should be lessthan or equal to today. but ticket is getting created with future dates as well. How can i achieve this? please suggest.

- Shanmuk


Answers:
author: John Funk
body: Hi Shanmukha - Welcome to the Atlassian Community!

Can you share the validator that you have?


Tags: cloud

jira-service-management

jira-service-management-cloud
Closed and resolved status in JIRA
Asked by Smitha Joseph:

What is the major difference between closed and resolved status of issues in JIRA? Does the team move the story to Resolve state and PO on accepting the story moves it to Closed state? What state is the issue moved to when moved to Done state in Kanban board?


Answers:
author: Christopher Yen
body: in JSM, and my experience in ITSM, usually resolved is when the agent fulfills a request or resolves an incident, at my company we then have an automation that waits 3 business days to move it to Closed status. The purpose for us is to give the customer a window to reply and reopen the issue if unresolved but once a ticket is closed we have another automation that replies to the customer informing them the ticket has been closed and to please open a new ticket to avoid long running issues where customers continue to add on to past records.

but in Jira the workflow is flexible to your needs/requirements, I've some projects just use "Done" instead.


Tags: jira-service-desk-cloud

jira-service-management

jira-service-management-cloud
Microsoft Teams status creates email notifications to whole team
Asked by Carrie Coogan:

Hi,

we have started using the Microsoft Teams location status and have noticed when a team member sets it to 'Working Remotely' it means their Service Desk Tickets send email notifications to the whole team for things like comments.

Is there a way to stop the emails while using the status? The assignee is completing the work and the rest of the team do not need to be notified.

Thank,

CC


Answers:
author: Carrie Coogan
body: Never mind! We have an automation to email for team support when the team are out of office and a reporter comments on a ticket. This was still active and just a coincidence the comments happened as the Working Remotely status was used.


Tags: cloud

jira-service-management

jira-service-management-cloud
Imported tickets - Description not showing on the customer portal
Asked by Brooke Batchelor:

We moved across to Jira Service Management last week (yay for us, we are loving it!) and our customers cannot see the description or comments on the imported tickets. All they can see is the subject/ticket title.

What can I do to improve their visibility on the ticket details?

Thanks in advance for your help.


Answers:
author: Brooke Batchelor
body: Hi Manav,

Thanks for your response.

The customers couldn't see the description for the ticket they logged on a different ticketing system. I imported the tickets with all the information from the other ticketing system into JSM using .csv but they weren't able to see the description (although I could).

I figured out the solution. When setting up the request type, I removed the "Description" from the Request Form and put it in the issue view. This prevented the customer from being able to view the description of the issue in their portal. When I moved the description back to the request form (when configuring the request type) they were able to see it again.

Thanks for your quick response and willingness to help!

Brooke


author: Manav Shah
body: So, just to clarify, you or the customers are exporting the tickets from JIRA, maybe in excel? and they are unable to get the description/comments field?

If that is the case, you can change the default export values in the table view.


Tags: cloud

jira-service-management

jira-service-management-cloud
How customers can edit their comments on an issue through the portal screen
Asked by ?? ??:

Is it possible for customers to edit their comments entered in an issue on the portal screen? For example, can the permission scheme be changed to allow customers to edit their own comments?


Answers:
author: YY Brother
body: Hi [@?? ??](/t5/user/viewprofilepage/user-id/5530495)

Welcome to our community.

It's not permitted or feasible to let customers edit comments on the portal. They can add another comment to correct the previous comment contents.

Thanks,

YY?

comments: author: ?? ??
body: Thank you for your answer!! It was so helpful!!


Tags: cloud

jira

jira-service-management

jira-service-management-cloud