youngmon/atlassian-qna huggingface dataset:
Can I disable ALL builds BEFORE startup of migrated secondary test instance via config settings?
Asked by timothy schmidt:

I want to test the import of a primary bamboo server instance's data.

However, I do NOT want all the plans to start checking and building on restart of the test instance.

Is there a config file setting that I can set to affect a PAUSE as it were before starting up the BAMBOO windows service after a successful IMPORT?

I could do a BULK PLAN disable before exporting, but in cases where some plans are already disabled, this is not a good methology, as it requires saving the state of all plans so one can accurately set them all back correctly after the IMPORT.

I could try to PAUSE the test server via REST API ++**immediately**++after starting up the test instance but I'm not sure this guarantees that no plans would get started during that window of time during startup.

Thanks!

T.S.


Answers:
author: Steffen Opel _Utoolity_
body: You can achieve this via the [BUILDING_DISABLED](https://docs.atlassian.com/atlassian-bamboo/6.7.2/com/atlassian/bamboo/utils/SystemProperty.html#BUILDING_DISABLED) system property (usually by passing *-Datlassian.bamboo.build.disable=true*at startup):
> Disable triggering plans globally in Bamboo. Plan can be started manually only.

Please note that this only works as expected for Bamboo \>= 6.3.1, see the following issue for details:

* [-Datlassian.bamboo.build.disable=true does not disable building plans globally in Bamboo (BAM-18595)](https://jira.atlassian.com/browse/BAM-18595)

comments: author: timothy schmidt
body: Perfect!

BTW .. Other than modifying my startup config as shown here :

![config.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/43136i2B75C2E22C59EE82/image-size/large?v=v2&px=999 "config.PNG")

Do you know if I add \& modify the atlassian.bamboo.build.disable="true" definition to a config file to achieve the same effect?

Thank you again...

T.S.


author: timothy schmidt
body: It's looking like for a windows' service it could only be the bamboo\\bin\\service.bat file.

One would modify the --JvmOptions string as appropriate and de-install/re-install the service. Kinda belabored for just that one change...

So I guess the the "properties" interface way IS actually simpler (with a service stop/start) thrown in too ...( :-)

Cheers!

T.S.


author: Steffen Opel _Utoolity_
body: Agreed - it's kinda weird that the only alternative option seems to be the service startup wrapper itself (also on Linux), but that's were we stand apparently.


Tags: disable

import
Obtain BitBucket PR destination branch from related Bamboo build
Asked by patryk_bartoszek:

How can I get PRs destination branch name inside Bamboo build?  
I looked at bamboo variables in docs, but there doesn't seem to be anything related to bitbucket.  

My plan branches are created with:  
"Branches / Create plan branch: When pull request is created"  

Bamboo shows a different icon next to plan branches created this way. It knows branch plan was created with PR. Is there any way to access this metadata?


Answers:
author: Alexey Chystoprudov
body: Look at metadata tab of job result. It shows branch name

comments: author: patryk_bartoszek
body: Under which key? All I can see is **source** branch name under "repository.branch.name" and "repository.git.branch". What I'm interested in is **destination** branch.


author: Alexey Chystoprudov
body: Oh, I've missed word **destination.**

Created <https://jira.atlassian.com/browse/BAM-20253> to track interest at this feature.


Tags: bitbucket

bitbucket-server

server
Deploy git tag / Bitbucket symbol after successful deployment
Asked by Stefan Wendelmann:

Hi, is it possible to tag the commit after a successful deployment with the release-id, or even to get a symbol like the build ok/fail symbols to idecate in the Bitbucket / git repo what has been deployed to what env. ?

Using Bamboo 6.7.1 and Bitbucket 5.15.0


Answers:
author: Steffen Opel _Utoolity_
body: As of [Bamboo 6.7](https://confluence.atlassian.com/bamboo/bamboo-6-7-release-notes-959795979.html) it is possible to use the extended/new [Repository Tag](https://confluence.atlassian.com/bamboo/configuring-a-source-control-task-956167494.html) (previously known as VCS Tagging, which only worked for Subversion) to create a Git tag and push it to a remote repository.

If you configure the task after the deployment task(s), it will only execute if the preceding tasks succeed.

The task label is also automatically visible on the commit in the Bitbucket Server repository, and so is the build status when [Bamboo has been integrated with Bitbucket Server](https://confluence.atlassian.com/bamboo/integrating-bamboo-with-bitbucket-server-779302772.html) via an application link.

comments: author: Stefan Wendelmann
body: Hey Steffen,

thanks for your quick response.

I saw the Repository Tag Task, but when i see my Pipeline i dont know if its fitting.

1. Test Branch on git Repo -\> bamboo build (with branches) -\> Branch Test Build ok -\> Deploy to Test env.

2. Prod Branch on git Repo -\> bambo build (prod) -\> Branch Prod Build ok -\> deploy to Prod env.

what i want to see is in my bitbucket / git commit log, what commit is on which env.?

I hope that makes my request more clear :)


author: Steffen Opel _Utoolity_
body: Ah, I see - if I get this correctly now, you could use the *${bamboo.deploy.environment}* [deployment variable](https://confluence.atlassian.com/bamboo/variables-for-deployment-environments-342754180.html#Variablesfordeploymentenvironments-Deploymentvariables) as (part of) the Git tag name. Tags are visible in the commit log view, albeit admittedly not as rich and prominent as you might have envisioned for a build status symbol.

I'm not aware of the latter being readily available somehow, though IIRC the columns are integration points so that one could probably implement a more granular 'Environment' column alongside the existing 'Builds' column to automatically surface the information you are looking for in a more user friendly way (i.e. easier to identify and foregoing the tagging needs).


author: sharmalalitcloud
body: Can we do it with Jenkins and Bitbucket also ?


Tags: bitbucket-server
permissions for creating Jira tickets from bamboo
Asked by Robert Kulyassa:

Hi all,  

I have an issue with creating Jira tickets directly from Bamboo. Some of our users just don't see the option to do that, therefor they can't. (E.g: you open a specific test and you have the option to (un)quarantine or create a jira ticket for the test.)

the action menu for a specific test for me:  
![Screenshot from 2019-01-21 14-19-33.png](/t5/image/serverpage/image-id/43074i9D9A9107798CEAA1/image-size/large?v=v2&px=999 "Screenshot from 2019-01-21 14-19-33.png")

The same for a non admin user:  
![Screenshot from 2019-01-21 14-20-38.png](/t5/image/serverpage/image-id/43075iA4BCA2F770DA777B/image-size/large?v=v2&px=999 "Screenshot from 2019-01-21 14-20-38.png")  

After playing a bit I gave them admin rights (on bamboo, no changes on jira), and that fixed the problem! Obviously I don't want to give admin rights to everyone, so I need another solution. I am anyway really surprise it depends on the permissions.  
So what to do? What permissions/settings users need to be able to create/link a jira ticket from bamboo?

Additional info: if I have an already linked ticket on bamboo, these non admin users see it and can open it.

<br />

Bamboo server: 6.6.3


Answers:
author: Steffen Opel _Utoolity_
body: Unfortunately Bamboo currently lacks sufficiently fine grained permissions to properly address this - please watch and vote for the following issue to raise Atlassian's priority for addressing this notable limitation:

* [Create JIRA Issue from failed test is only available to Plan Admins (BAM-15060)](https://jira.atlassian.com/browse/BAM-15060)

That being said, it sounds like you have only considered global admin rights and are not yet using the new [project permissions](https://confluence.atlassian.com/bamboo/configuring-project-permissions-938840042.html) (introduced with [Bamboo 6.2](https://confluence.atlassian.com/bamboo/bamboo-6-2-release-notes-938641951.html)), which *might* mitigate the impact a bit (depends on your particular team composition and workflows of course).


Tags: jira

jira-server

server
Test for colorized output
Asked by Steffen Ehrlichmann:

How can I test for colorized output using Bamboo? I run unit tests to check if output is colorized. Using Bamboo's shell script no colors are printed and unit tests fail. If I login on the machine using ssh and run unit test manually, then all run well. In build log I can see expected output is colorized but system output is not colorized.

I tried to insert *TERM=xterm-256color* and *CLICOLOR=1* in Bamboo's shell script but didn't work.

**How can I enable color support for Bamboo's shell script?**

Environment:

\* Mac OS X 10.14.2 (18C54)

\* Bamboo version 6.7.1 build 60705 - 18 Oct 18

\* rspec (3.8.0)

\* ruby 2.5.0p0

Build log

![Bildschirmfoto 2019-01-21 um 14.02.28.png](/t5/image/serverpage/image-id/43073iBB274F15656C7414/image-size/large?v=v2&px=999 "Bildschirmfoto 2019-01-21 um 14.02.28.png")


Answers:
author: Steffen Ehrlichmann
body: Colorized output works for bamboo's shell. The framework I used, checks if current environment is a tty. And if is not, then do not print colors.
SVN checkout unexpectedly forcing clean build
Asked by christok:

I have a visual studio solution that includes a core project and several shared projects in an SVN repository. As such, building this solution requires several checkouts.

My problem is that the logs are reporting "Clean checkout enforced by repository configuration" after each checkout even though I have not selected "Force Clean Build" in the build plan's repository configuration. So predictably the build fails due to dependencies not being found as each checkout is deleted from the working directory before the next one is checked out.

Any insight on why I am experiencing this behavior?


Answers:
author: Gonchik Tsymzhitov
body: Hi!

I have not met with same problem, but it will be good to check for related version on next releases

<https://confluence.atlassian.com/bamboo/bamboo-releases-671089224.html>

Cheers,

Gonchik Tsymzhitov
Where can I find a list of dependicies for Atlassian Stack tools?
Asked by Daniel Trask:

I am running Bamboo 5.14. While we wish to eventually (in next six months) upgrade all of our Atlassian tools to the latest versions. I am exploring whether I can just upgrade my Bamboo to 6.3 to take advantage of the YAML capabilities in the meantime. I am trying to find any dependencies for Bitbucket, Jira (Software and Service Desk), Crucible/Fisheye, even Confluence or Hipchat.

I saw a doc that said I could use Bamboo 6.3 with my current stack, but I think there may be an issue with the Appliance links-I know I will have to upgrade the appliance links plugin, which would break the the links with my older programs. Any help is greatly appreciated!

Atlassian Bitbucket v4.14.4

Confluence 6.1.1

JIRA v7.8.0

FishEye and Crucible 4.5.3


Answers:
author: Jobin Kuruvilla [Adaptavist]
body: This page details the version compatibility of app links plugin: <https://confluence.atlassian.com/applinks/application-links-version-matrix-779174762.html>

Hope that helps.


Tags: application-link

dependency
Eclipse not recognizing Atlassian SDK artifactId as project
Asked by Ashish:

Hi,

I've followed instructions in <https://developer.atlassian.com/server/bamboo/introduction-to-writing-tasks/> to create a sample bamboo plugin and created a folder set on my Windows machine.

1) Installed SDK

2) Ran atlas-create-bamboo-plugin from SDK repository folder. Details entered were as:

GroupId: BambooTest  
Define value for artifactId: : bamboo1  
Define value for version: 1.0.0-SNAPSHOT: : 1.0.0-SNAPSHOT  
Define value for package: BambooTest: : bamboop

Build was successful and can see the folders.

3) Opened Eclipse and tried to import. problem here is that Eclipse is not recognising bamboo1 as of type project. Hence I cannot add any classes or packages which are needed if I have to modify or write more plugins.

Please advise if there is any step I am missing to configure Eclipse for Atlassian SDK integration ?


Answers:
author: Marco Paleani
body: see here: [Put the final polish on the project in Eclipse (atlassian.com)](https://developer.atlassian.com/server/framework/atlassian-sdk/put-the-final-polish-on-the-project-in-eclipse/)

atlas-mvn eclipse:eclipse


author: Ashish
body: I figured out the answer myself. I had missed executing atlas-mvn command which writes as a project.


Tags: sdk
How can I prevent Bamboo branch plans from executing upon creation?
Asked by Jeff_Schaeffer:

I want a release branch to be created from my release build so it's available for developers to create any needed hotfix branches. However, I don't want the (newly created release branch) branch plan to execute just upon branch creation. Only upon the first commit (via pull request from hotfix branch)

How can I stop that execution upon creation?


Answers:
author: Steffen Opel _Utoolity_
body: Unfortunately the option to "Don't execute upon initial branch detection" is not yet available - please watch and vote for the following issue to raise Atlassian's priority to address this limitation:

* [Prevent first build on new branch/plan until change detection occurs (BAM-17048)](https://jira.atlassian.com/browse/BAM-17048)


author: Foong
body: The latest Bamboo have the option **When pull request is created** for Automatic branch creation.

Which mean the release branch plan will only be created in Bamboo if there is a pull request created.

For more information, refer to [Automatic branch management](https://confluence.atlassian.com/bamboo/using-plan-branches-289276872.html#Usingplanbranches-Automaticbranchmanagement)

comments: author: Jeff_Schaeffer
body: Understand and thanks for the thought but that doesn't do the job. My release branch (created upon merge with master) is to be 'branched from' for any potential hotfix branches. This release branch needs to be present to avoid confusion if hotfixes are needed (creating a hotfix branch from the release branch). I want the new release branch plan created upon release branch creation but not executed. Then upon hotfix pull request merge into the release branch, I want the branch plan to execute automatically.

I attempted your change, making the branch plan to be created only upon pull request. The results were not what I wanted and a little concerning:

- A branch plan was created... from the hotfix branch, not the release branch.

- No branch plan was created for the release branch

This leaves me with having multiple hotfix branches/plans (which may not ever be integrated back to master) and each coming from the base release .vs. building upon each other in a release branch (without additional scripting).

I just want a 'Don't execute upon initial branch detection' option


Tags: branch

build

plan
Bamboo Gradle build fails with ?fatal: No names found, cannot describe anything"
Asked by Brian Mansfield:

I've inherited a Bamboo build that runs deploys on a remote agent. When I run it, the build in Bamboo is marked as "successful," but the `deploy` task is eventually skipped due to a fatal exception - here's a snippet of the logs:

    build   17-Jan-2019 10:25:33    Starting a Gradle Daemon (subsequent builds will be faster)build   17-Jan-2019 10:25:39    :cleanPackage UP-TO-DATEbuild   17-Jan-2019 10:25:39    :copyFilesbuild   17-Jan-2019 10:25:39    diffTarget: SITerror   17-Jan-2019 10:25:39    fatal: No names found, cannot describe anything.build   17-Jan-2019 10:25:39    build.gradlebuild   17-Jan-2019 10:25:39    :deploy SKIPPEDbuild   17-Jan-2019 10:25:39    build   17-Jan-2019 10:25:39    BUILD SUCCESSFUL

The Bamboo build is setup to check out a repository, then run a task called `deploy`:

![Capture.PNG](/t5/image/serverpage/image-id/42794iD0C0DD34D21F1DB9/image-size/large?v=v2&px=999 "Capture.PNG")

It looks like the issue may be happening when checking out the repository (I am completely new to Gradle, so would be happy to even have this validated/refuted). One other thing to note is that in the build.gradle file, I have Bitbucket creds, but I intentionally switched bewteen invalid credentials and working credentials, and the output was the same - so I'm thinking it's not something specific to this repository itself.

Does anyone have any suggestions/where I should look to troubleshoot? Anything is helpful, even if it's validating that this is likely a Git config issue, and not something else. Let me know if there's any other information I should include - like I said, I'm a total novice with this :)


Answers:
author: Brian Mansfield
body: To anyone that stumbles across this, the issue had nothing to do with Bamboo itself - the Gradle script was making a \`git describe --tags\` call, but the repository had no tags defined.

(I failed to include the necessary Gradle snippet in the original question, here it is for reference):

```

 result = exec{
   commandLine "git", "describe", "--tags", "--match", "$diffTarget-*", "--abbrev=0"
   standardOutput = stdout
   ignoreExitValue = true
 }
```


author: Daniel Santos
body: Hi [@Brian Mansfield](/t5/user/viewprofilepage/user-id/2578422),

I was searching for that error

    No names found, cannot describe anything.

and found that could be related to a **shallow clone** configuration in repository configuration. Do you mind checking the repository configuration for this plan and making sure you have the option **\[ \]Use shallow clones** unchecked?  

Other question:

Have you tried to run the same gradle build from outside Bamboo (on server terminal) to make sure this problem is only happening when you run within Bamboo?

comments: author: Brian Mansfield
body: I really appreciate you answering - "use shallow clones" was unchecked, yes. It wasn't a problem with Bamboo - the build script was making a \`git describe --tags\` call, but the repository had no tags defined.


Tags: git

gradle
How to update servicedesk issue type portal text?
Asked by Ian Walker:

Hello Everyone.

I have a service desk that looks like this:  

![Screenshot 2024-04-30 104625.png](https://community.atlassian.com/t5/image/serverpage/image-id/321223i144F5496EEC34B75/image-size/large?v=v2&px=999 "Screenshot 2024-04-30 104625.png")  

How can I make this look a bit nicer? I know how to change the title (e.g. 'Incident Requests' to 'Click here to raise an incident', but how can I then change the other text so that I have something like this?  

Incident Requests  
Need a to raise an incident? Click here to start - instead of 'Incidents'.  

Many thanks.


Answers:
author: Ian Walker
body: Nevermind, I fixed this, it was caused by having separate portal groups. I just made one portal group with all request types.


Tags: cloud

jira-service-management

jira-service-management-cloud
Automation Rules for 3 Strike Rule in jira cloud
Asked by Kishor Mudhili:

hello Team,

I'm new to JSM :):):)

i have checked few articals which is related to 3 Strike rules but these diff senarios.

i want to make it simple Rules.

when ticket status in Pending ( waiting for customer), we need to send 1st notifcation after update pending 24 Hrs

2nd notification 4 hrs

3rd notification 48 hrs exculde week-ends.

please help me to configure


Answers:
author: Darryl Lee
body: Hi Kishor - I'm not sure which articles you looked at, but this one is pretty comprehensive:

* [Automation email](https://community.atlassian.com/t5/Jira-Service-Management/Re-Automation-email/qaq-p/2501795/comment-id/149540)

It talks about both creating custom notifications using Automation, as well as the option to use the SLA functionality. There's a lot of great links there, but I will highlight a particular rule in Jira's Automation Library:

* [When an issue remains for 5 days without an update ? send a notification to the Assignee](https://www.atlassian.com/software/jira/automation-template-library#/rule/9918920)

Hopefully that will give you a good idea on how you might be able to implement what you are trying to do.


author: Kishor Mudhili
body: ?


Tags: cloud

jira-service-management

jira-service-management-cloud
Can I add Sections to Forms in JSM Cloud?
Asked by Jenny O_Connell:

I have a longish form which I would like to break into 5 sections (I am copying from an existing PDF form). How do I do this I Jira, I have just spent hours looking.


Answers:
author: Vijay Dadi
body: Dear [@Jenny O_Connell](/t5/user/viewprofilepage/user-id/5486818) ,

Yes, you can build your dynamic forms using Forms in Jira Service Management. Here is the guide for the same. If any more details needed, please do let me know.

[What are forms? \| Jira Service Management Cloud \| Atlassian Support](https://support.atlassian.com/jira-service-management-cloud/docs/what-are-forms/)

Hope this helps!

Vijay

comments: author: Jenny O_Connell
body: Thanks Vijay, but that isn't quite what I was asking. Yes, I have already created some forms, but I am finding they are a bit long and cumbersome. My question is, can I break it up into subsections with subheading?

eg

1 General Information - customer name, contact details, date etc

2 Product Information - product name, part number, version number

3 Description of Event - what went wrong?


author: Vijay Dadi
body: Hi,

Is this what you are looking for ?

![hard.png](https://community.atlassian.com/t5/image/serverpage/image-id/321809i3735A7E19334B536/image-size/large?v=v2&px=999 "hard.png")

Vijay

comments: author: Jenny O_Connell
body: Hi Vijay,

Yes, that would be great. Perhaps the answer is something really simple but I hadn't been able to find it easily.

Jenny


author: Vijay Dadi
body: This is simple, just add the text in between your fields to make sections.

Vijay


author: Jenny O_Connell
body: Hmm, I can't edit between the fields.

Jenny


Tags: jira-service-desk-cloud

jira-service-management

jira-service-management-cloud
How to create a cascading dropdown using values from another field?
Asked by Ian Walker:

Hello Everyone.  

I have a cascading drop-down field called Project that has categories inside it (e.g. Microsoft \> MS365).

I want to create another cascading drop-down field, called 'Sub-category' that first gets the values of the category list that is tied to the Project custom field and then, based on that, displays the relevant sub-categories.

For example:

Project (Microsoft) \> Category (MS365) \> Sub-category (Excel)  

Is this possible?

Regards.


Answers:
author: Vijay Dadi
body: It has limitation only till 2 levels. But it would be nice to have more levels if needed.


Tags: cloud

jira-service-management

jira-service-management-cloud