youngmon/atlassian-qna huggingface dataset:
Virtual Agents For Bamboo shuts down VMs 2 minutes after startup
Asked by Ashley Lewis:

With Virtual Agents For Bamboo enabled I cannot use some of my connected VMs, they shut down two minutes after they initialize. I can get them to stay up by disabling this Bamboo plugin. I do have one VM that appears to be unaffected. The effected VMs share nothing but the host. I've tried migrating one of the affected VMs to another host it still shuts down 2 minutes after startup.

I have read [the Virtual Agents for Bamboo admin guide](https://docs.stiltsoft.com/display/BAMBOOVM/Administrator%27s+Guide)

Where are the log files for Virtual Agents For Bamboo? What other trouble shooting steps should I pursue before logging this as a bug?


Answers:
author: Ashley Lewis
body: Note on the agent mappings section of the configuration page for Virtual Machines for Bamboo: "Note about enabling/disabling remote agents.

The add-on will automatically enable remote agents upon start of the dedicated virtual machines. The add-on will also automatically disable remote agents and then shut down the dedicated virtual machines when there are no tasks in the queue for the running agents."

This is the cause of my problem and I have worked around it by removing the mappings.


Tags: bamboo-administration
TFS plugin on Hosted Bamboo
Asked by Yoram Elhav:

Does TFS plugin work on hosted Bamboo


Answers:
author: Steffen Opel _Utoolity_
body: Unfortunately 3rd party add-ons are still not supported in Bamboo Cloud - Utoolity's [Tasks for AWS](https://marketplace.atlassian.com/plugins/net.utoolity.atlassian.bamboo.tasks-for-aws) is also affected by this policy, please see our resp. FAQ [Will Tasks for AWS be available for Bamboo Cloud (Atlassian OnDemand)?](https://utoolity.atlassian.net/wiki/questions/36306948/will-tasks-for-aws-be-available-for-bamboo-cloud-atlassian-ondemand) for more details on the background and state of affairs, which conceptually also apply to Stellarity Software's [TFS Repository](https://marketplace.atlassian.com/plugins/com.stellarity.bamboo.tfs-repository-plugin) add-on:
> \[...\], Atlassian doesn't allow classic add-ons to be installed in their cloud offerings for security and scalability reasons, rather only those build with the new add-on framework [Atlassian Connect](https://developer.atlassian.com/static/connect/docs/index.html) - ironically Connect doesn't yet support Bamboo in turn, so we cannot do anything about it at this point and rely on Atlassian closing this gap first \[...\]

Please watch/vote/comment on the following issue to raise awareness for this increasingly relevant limitation:

* <https://ecosystem.atlassian.net/browse/AC-1193>  

comments: author: Sergey Podobry _Stellarity Software_
body: Yes, it's true. Thanks for the response.


Tags: addon-com.stellarity.bamboo.tfs-repository-plugin

cloud
Why does Bamboo wait to start a build when commanded manually?
Asked by Neal Culiner:

Hello,

Using the latest bamboo on Windows Server 2012 R2 - all working great. 5 agents setup, powerful server with multi-procs and 128 GB RAM. When I click the play button to command a build, I see it show three dots ... and I have to wait somethings several minutes for the build to start. Nothing else is in progress. Why is there a delay and how can I have this fire immediately or more efficiently?

Thank you.


Answers:
author: Pawel Skierczynski
body: First thing that comes to mind - maybe you have big source repository (or many of them in one plan).

When starting manual build it gets to queue but Bamboo server is updating every repository to find out set of commits to build. If there is big repository/many changes/many repositories it can take a lot of time...

If this is your case there is not much that can be done. If you can switch to Linux on server side it could help. There are known performance issues with windows and for example git (I don't know what repository type you are using). (as a side node Bamboo best works with PostgreSql database - but it's irrelevant for this case)

If you must use windows you can try log in and manually clone repository to see how long does it take. Then experiment with different git implementations (assuming you are using git). This one is new and promising: <https://git-for-windows.github.io/>

If you have one big repo (let's say \> 1GB) you could also consider splitting it.

comments: author: Neal Culiner
body: Thank you for the reply @Pawel Skierczynski I am using Windows Server 2012 R2 against SQL Server 2014 STD with Git. No large repo's, about 20 repo's in total, all set to use shallow clones, etc.


author: Neal Culiner
body: I do have quiet periods on the linked repositories, but there was no activity in the past 5 minutes on them which is their quiet period. Even if no activity would a commanded build action still way a quiet period amount of time? That may be the culprit.


author: Pawel Skierczynski
body: Quiet period is not connected to manual build in any way. Nevertheless I would strongly discourage using quiet period feature. It will have performance problems with anything bigger than very small instance. Shallow clones will not help with change detection much.SQL Server requires specific configuration. I hope you've seen this <https://confluence.atlassian.com/bamboo/microsoft-sql-server-289276827.html>.Try running git clone manually on server to see how long doest it take.Also check what git implementation does server use?If using native git (recommended) setting logs to debug on com.atlassian.bamboo.plugins.git could tell us more (like if git fetch command is called early and just very slow). Logs can be tuned runtime from system admin menu.


Tags: bamboo-administration
Bamboo build hangs even though the build steps are completed
Asked by Mafaz Udayar:

We are using bamboo cloud version, and the build agents are on Amazon EC2.

For a specific build plan, the bamboo build keeps running even though the build steps are completed. The logs in the build agent does not have any entries related to the incident. Every time a build runs, it keeps on running and does not finish, the user has to manually stop it.

Anyways to troubleshoot this issue?


Answers:
author: Nirmal Shankar
body: Not actually releated to this problem, but there is a way to kill hung builds

<https://marketplace.atlassian.com/plugins/com.atlassian.buildeng.hung-build-killer>

comments: author: Mafaz Udayar
body: As i check through this add-on, it does not show up under Add-on's in the bamboo cloud administrator panel. Is it used only for the locally hosted bamboo?Is there any other way to kill the hanging builds in bamboo. Please note that we are using bamboo cloud version, and the build agents are on Amazon EC2.


author: Nirmal Shankar
body: Oh ok. I was talking in terms on standalone bamboo. Not reallly sure on bamboo cloud. Will get back if I find something


Tags: cloud
Bamboo Cloud Evaluation Change
Asked by Joshua Day:

I am wanting to see if it's cost effective running our bamboo instance in the cloud rather than on premise. I am trying to add more than 10 jobs in order to replicated our current on premise set up but I cannot for the life of me find where to increaqse the max build jobs avaliable.

Using Evaluation Bamboo Cloud (with paid JIRA / Confluence / Bitbucket - I can find and change the license for these)


Answers:
author: Bruno Rosa
body: Joshua, users are only allowed to run 10 jobs during the Bamboo Cloud evaluation period, that's probably why you're unable to create more jobs and increase the max build jobs available.


Tags: cloud
Node.js Add-On: Plans to support bamboo 5.9.4
Asked by K:

Any news about releasing a new version of Node.js plugin which supports bamboo 5.9.4.


Answers:
author: Bruno Rosa
body: Karthik, are you referring to the [Bamboo Node.js Support](https://marketplace.atlassian.com/plugins/com.atlassian.bamboo.plugins.bamboo-nodejs-plugin) plugin? The latest version available of this plugin is **1.7** . I believe there's some confusion here, the Marketplace listing says it is only available from 5.6.1 to 5.8.2, but this is only because the plugin is bundled after that. For example, if you happen to have a Bamboo 5.6.1 instance running, you will have to download the plugin from Marketplace, because back then the plugin was not bundled. On the other hand, if you download\&install Bamboo 5.9.4, the **Bamboo Node.js Support** **1.7** plugin will be there, no extra steps are needed.

comments: author: Charlie Misonne
body: oh thanks for this info. This was the only reason I was not upgrading to the latest Bamboo version
Making task success optional
Asked by kridan:

Hi there,

We have been using Bamboo for a few years, and one thing that often fails our build is a problem attaching to our SAN to copy the nightly build to an archive area we have.

While the build works fine, the last step is the copy to the archive, and when it fails, the entire plan fails (as designed of course).

My question is, is there a way to mark the success of a task or stage as "optional". i.e. if the build worked but the copy to the archive area fails I still want it to pass.

Or should I really be looking at splitting this into two separate plans, in which case I could have notification ON on the build, but OFF on the "archive task". If that's the case, how can I chain one plan to run after the other?

Thanks in advance.


Answers:
author: kridan
body: Thank you Nirmal. I'll give that a try. I think we're just packing too much into the individual plan and should use the dependencies more as you suggest.


author: Nirmal Shankar
body: Easiest way is probably split them into say build and copy plans. In the dependency tab you can mark the "copy" plan as a child build. That was on every succesful build it triggers the copy plan. That way even if the copy fails the build plan would show as a success.


Tags: bamboo-administration
Bamboo build plan's release version is ${bamboo.branchName}-${bamboo.buildNumber} instead of deployment plan's release version
Asked by vinaycardoza:

Hi Guys,

I have a bamboo build plan say 'B' which is connected to a deployment project 'D'.

The deployment project has release versioning set to '1.0.50-SNAPSHOT-1'.

The build plan has 2 plan branches 'master' and 'develop'. 'master' is the default branch.

When I run the plan 'B' against branch 'develop', the release version deployed on 'D' is 'develop-200'. 200 is the build number. This does not happen when the plan is run against 'master'.

I require your help and suggestions to understand what is the problem and a way to solve this.

Please upvote my question so I have min. 3 points to provide feedback.

Regards

Vinay Cardoza


Answers:
author: Nirmal Shankar
body: One possible reason is that the deployment pipleine that you have is off staging branch. So everytime you run the deploy pipleline its possibly picking off just the changes from staging.


Tags: bamboo-administration
Bamboo Build Times Charts
Asked by Cynthia Fehr:

Hello,

We would like to create a chart showing the Bamboo Build Times per release in Confluence.

Is there a Bamboo widget that does that?

Cynthia


Answers:
author: Cynthia Fehr
body: I have decided just to get the information manually from the Bamboo database and create a chart through excel.


Tags: bamboo-administration
How can you backup plan settings for Bamboo Cloud?
Asked by grantreidnz:

Like a twit, I accidentally deleted a new deployment plan we were working on.

In the process, I realised that I can't find a way to export the settings, or even do a backup in Bamboo Cloud.

How do you backup and restore plans in Bamboo Cloud?

How can I keep my settings under change control?


Answers:
author: Steffen Opel _Utoolity_
body: Unfortunately neither of those features are available as of today:

* *How do you backup and restore plans in Bamboo Cloud?* - this is one of the highest voted and longest standing feature requests:  
  <https://jira.atlassian.com/browse/BAM-1223>
  * While you can export an entire Bamboo Server instance as at least, this isn't available in Bamboo Cloud either:  
    <https://jira.atlassian.com/browse/BAM-13079>
* *How can I keep my settings under change control?* - this would ideally be implied in BAM-1223 above, but might also be partially addressed by a related and likewise popular feature request for both Bamboo Server and Bamboo Cloud:  
  <https://jira.atlassian.com/browse/BAM-13600>  

As you can see in the last comments on each issue, both seem to be on the top of the backlog now, but are also classified as comparatively complex so it might take a while still.

comments: author: grantreidnz
body: Thanks for your excellent answer Steffen. For now I (cough) resorted to taking screenshots of key config pages for build and deploy. I pity the fool that accidentally deletes our the build plan.


author: Bob Swift (personal)
body: [Plan Creation Scripting](https://bobswift.atlassian.net/wiki/display/BCLI/Plan+Creation+Scripting) using [Bamboo Command Line Interface (CLI)](https://bobswift.atlassian.net/wiki/display/BCLI) allows us to source control all of our plans. This works well for Server, but not so much for Cloud as ![sad](/html/@C495B4504065515364EB1894F812B34C/images/emoticons/sad.png "sad") as we needed to provide extended REST APIs which are not allowed on Cloud.

comments: author: grantreidnz
body: Thanks Bob. I see you have solved it neatly for server. What a bummer you don't have the hooks you need for Cloud.


Tags: cloud
What "executable type" should I use for bamboo-capabilities.properties for the Node.JS plugin
Asked by John Rutherford:

I use the bamboo-capabilities.properties to manage my remote agents capabilities in bamboo. I have not been able to figure out what the Node.js bamboo plugin expects as the "executable type" (system.builder.\<executable type\>.Node)


Answers:
author: Marcin Oles
body: It's node. So as an example:

```
system.builder.node.Node.js\ 0.10=/opt/node-0.10/bin/node
```

Also remember, that Node.js plugin expects the capability to point to an executable and not installation directory, and that's why there is the "/bin/node" part. On windows, it can be something like this:

```
system.builder.node.Node.js\ 0.10=C:\\opt\\node-0.10\\node.exe
```

(system.builder.node.\<name\> = \<path\>)


Tags: node.js
Error error MSB4019:
Asked by ahmer khan:

error MSB4019: The imported project "E:\\Microsoft\\VisualStudio\\v10.0\\WebApplications\\Microsoft.WebApplication.targets" was not found

I have been given the task to import a project from TFS to Bamboo. Everything is going smoothly until I come across this error

error MSB4019: The imported project "E:\\Microsoft\\VisualStudio\\v10.0\\WebApplications\\Microsoft.WebApplication.targets" was not found

I went into my C Drive and ensure this file was there. Any Ideas \>?


Answers:
author: ahmer khan
body: Anyone? Do you think it is a version issue ?


Tags: cloud
How to check test count?
Asked by Mark Hirota:

Let's say that I have a script that is invoked that runs my tests and produces a JUnit compatible results XML file. Because I want to be able to quarantine failing tests in Bamboo, I therefore ignore the return code from the command invoked in the script.

However, this creates a scenario whereby the test runner could exit prematurely (say, due to an exception), without necessarily causing a test failure (an issue during test fixture?)

The overall test count would drop in this case.

Also, someone could cut out tests (let's assume unintentionally) so that they no longer run at all -- also reducing the overall test count.

How can I enable a check for this in Bamboo, and cause a failure?


Answers:
author: Marcin Oles
body: Hi Mark,

I don't think there is such an option in Bamboo to verify the number of tests. In your case I'd recommend writing another script task which would analyze the JUnit report and fail if the number of tests is incorrect or if the file was not generated at all. Then after such script task you can add "JUnit Parser" task to allow browsing test results in Bamboo.

You can consider using tools like xmlstarlet to achieve this.

To fail a script task simply call "exit 1". Also, the script task and JUnit Parser task probably should be "final" tasks, to always run.

Cheers,  
Marcin

comments: author: Mark Hirota
body: Hi Marcin,I'm looking for a feature like this: <https://confluence.jetbrains.com/display/TCD9/Build+Failure+Conditions#BuildFailureConditions-Failbuildonmetricchange>Is anything in the works like this?


author: Marcin Oles
body: I haven't heard of such a feature or a plugin that introduces it. However, this feature sounds pluggable, as Bamboo already has extendable post build processors. So maybe it's worth to look through Atlassian Marketplace for a plugin that does it?You can also create a feature request under <https://jira.atlassian.com/browse/BAM>.
Create template from existing request type
Asked by flim:

I have a request type that is shared among different projects. Is it possible to create a template from the request type?


Answers:
author: Marc - Devoteam
body: Hi [@flim](/t5/user/viewprofilepage/user-id/5360322)

There are off-course the Atlassian templates that are in the system by default you can use and modify to your needs, but the changes you make can't be saved.

There are no options to template request types, also not with apps. (at least I have never encountered one)

There are only marketplace apps available for issue type templates.


Tags: cloud

jira-service-management

jira-service-management-cloud
Filter column setting
Asked by flim:

The Filters 'Save as' function saves only the filter criteria, not the column settings. Is it possible to have different filter layouts with different columns? I need to export data with different column layout for different filter criteria.


Answers:
author: flim
body: I found the solution here

<https://community.atlassian.com/t5/Jira-Software-questions/How-can-I-save-a-filter-specific-column-configuration/qaq-p/1683851>


Tags: cloud

jira-service-management

jira-service-management-cloud
Is it possible to hide linked JWM issues on JSM side tickets
Asked by Bradley Wills:

I have a personal JWM project that keeps track of small tasks that relate to JSM issues that are assigned to me. When the two are linked, the JWM issues appear in JSM on the linked issue.

Is it possible to change a setting to hide all JWM issues that are linked to an issue in JSM?


Answers:
author: Brant Schroeder
body: [@Bradley Wills](/t5/user/viewprofilepage/user-id/5390979) Welcome to the Atlassian community

If you link the issues the link will show on both issues and there is no way to hide them.

comments: author: Marc - Devoteam
body: Hi [@Brant Schroeder](/t5/user/viewprofilepage/user-id/769100)

I would link them instead of liking them! :)


Tags: cloud

jira-service-management

jira-service-management-cloud
Is there any impact if we directly upgrade to Xray Dc version of 7.2.2-i9 t o 7.4.1-i9 in Jira Dev v
Asked by Siddharam Pujari:

we are upgrading to Jira Dev version: 9.4.14. but we have currently installed with Xray DC of the version of 7.2.2 -i9. after upgrading to Dev version 9.4.14, can we directly update to Xray DC version 7.2.2-i9 to 7.4.1-i9?

Is there any impact if we directly upgrade to Xray Dc version of 7.2.2-i9 t o 7.4.1-i9 in Jira Dev version:9.4.14


Answers:
author: BHUSHAN PATIL
body: Hi [@Siddharam Pujari](/t5/user/viewprofilepage/user-id/5390957) ,

Absolutely, you're on the right track. You can directly upgrade Xray DC from version 7.2.2-i9 to 7.4.1-i9 after upgrading Jira to version 9.4.14. The good news is that the both i.e 7.2.2-i9 and 7.4.1-i9 Xray version is indeed compatible with Jira 9.4.14.

[Xray Version history](https://marketplace.atlassian.com/apps/1211769/xray-test-management-for-jira/version-history)

![Screenshot 2023-12-21 091719.png](https://community.atlassian.com/t5/image/serverpage/image-id/297688i634C3CC4218C47E2/image-size/large?v=v2&px=999 "Screenshot 2023-12-21 091719.png")![Screenshot 2023-12-21 091618.png](https://community.atlassian.com/t5/image/serverpage/image-id/297689i7A0AA6EF6356FA1C/image-size/large?v=v2&px=999 "Screenshot 2023-12-21 091618.png")It's a best practice to verify compatibility and upgrade Xray to the compatible version accordingly.

Also, if you feel my input help you please accept the answer.

Regards,  
Bhushan

comments: author: Siddharam Pujari
body: Hi Bhushan,

Thanks for your input which almost solved my problem. continue to this . do I have any impact when I upgrade to 9.2.2-i9 to 9.4.1-i9?

Regards.

Siddharam Pujari.


author: BHUSHAN PATIL
body: Hi [@Siddharam Pujari](/t5/user/viewprofilepage/user-id/5390957) ,

When upgrading from Xray version 7.2.2-i9 to 7.4.1-i9, it's essential to consider a few aspects:

**Feature Enhancements:** Review the release notes or changelogs between these versions. Check for any new features, improvements, or changes that might affect your current workflows or configurations.

* [Xray 7.4.1 Release Notes](https://docs.getxray.app/display/XRAY/Xray+7.4.1+Release+Notes)
* [Xray 7.2.2 Release Notes](https://docs.getxray.app/display/XRAY/Xray+7.2.2+Release+Notes)

**Compatibility:** Ensure that any integrations, customizations, or other plugins used alongside Xray are compatible with the new version (7.4.1-i9).

**Testing Environment:** Before the actual upgrade, simulate the upgrade in a testing environment if possible. This allows you to validate the upgrade process and identify any potential issues before applying it to the live environment.

**Backup and Rollback Plan:** Always back up your current system before performing any upgrades. Have a contingency plan or a rollback strategy in place in case the upgrade encounters unexpected issues.

Also, if you feel my input help you please accept the answer.

Regards,  
Bhushan


author: Siddharam Pujari
body: Thank a lot .this solve the my queries.

Regards,

Siddharam pujari


Tags: jira-service-desk-server

jira-service-management

jira-service-management-server
How to use JSA Linking - Since ticket merging is not an option
Asked by Jarrod:

Hi,

**Summary**

I'm in the process of planning out a JSM implementation and want to get guidance on how to correctly implement ticket linking since JSM does not have the merge feature like other service delivery ticketing systems.

**What I am trying to solve.**

I want to do a JSM implementation where my SD Tech's can link tickets to one another in a parent child relationship.  

When the parent ticket is closed, all child tickets will be closed.  

++Examples++ :  
We have a P1 incident where a server is offline.

1. Staff Member calls, reports system unavailable

2. SD Team Links User issues to incident (Fields are merged, reported staff member get's added to incident ticket as a contact)

3. Incident is resolved

4. Child tickets are resolved

5. All contacts listed in the Incident ticket received a resolution email

The second use case you would see a merge situation for is:

1. Received alert from network monitoring that a switch has gone offline.

2. Engineer investigates and resolves.

3. Alert received from network monitoring, switch has come back online.

4. Merge Online alert into offline line alert, marking incident as resolved.

<br />

<br />

I've reviewed the feature guide on [Issue linking](https://community.atlassian.com/t5/App-Central/Linking-Issues-in-Jira-for-Beginners-Jira-Guru/ba-p/2502049), I suspect I would need to use the block/blocking type to achieve this.

Any guidance would be apricated.


Answers:
author: Mikael Sandberg
body: Hi [@Jarrod Lovas](/t5/user/viewprofilepage/user-id/5388824),

Welcome to Atlassian Community!

No, you are not limited to just use the block/blocking link type. You can either use one of the default ones, parent/child is one of them, or you have the option to create your own. And you can use automation to close child requests and copy information between requests if needed.

comments: author: Mikael Sandberg
body: And if you are looking for merge functionality there is an app in the Marketplace that can do that, [Merge agent for Jira](https://marketplace.atlassian.com/apps/1219514/merge-agent-for-jira?hosting=cloud&tab=overview).


Tags: cloud

jira-service-management

jira-service-management-cloud