youngmon/atlassian-qna huggingface dataset:
Is there a way to close an incident when associated alert is closed?
Asked by zahur don:

We use slack integration in order to notify/ack/close alerts via slack. It would be great if we could close an incident when its associated alert is closed from slack. is that possible?


Answers:
author: Samir
body: Hi [@zahur don](/t5/user/viewprofilepage/user-id/4308302) ,

There isn't a way to have the incident automatically be closed when an associated alert is closed. There can be several associated alerts for an incident, and more alerts can be associated to an incident after the incident is created.

We do have a feature request to be able to close the incident when all associated alerts for an incident are closed.

Thanks,

Samir

comments: author: Veiko J??ts
body: Hi [@Samir](/t5/user/viewprofilepage/user-id/2168284) ,

Does this also apply vice versa, i.e., when I close an incident, is it possible to make it also close the Associated Alerts altogether with Responder Alerts(that already are doing so). Or is there another approach for this workflow?

What I want to achieve is:

1. *An external integration creates an (Associated) Alarm*
2. *A Service Rule is triggered which creates an Incident(which itself creates a Responder Alert automatically)*
3. *We resolve and close the Incident*
4. *The Incident and all associated alerts(including Associated Alert(s), that triggered the Incident creation) get closed without us needing to manually close the Associated Alert(s) after already closing the Incident.*


author: Samir
body: Hi [@Veiko J??ts](/t5/user/viewprofilepage/user-id/4398337) ,

Currently it is not possible to have the associated alerts get closed when the incident is closed, although we do have a feature request for this!

What some users do is setup a webhook integration to trigger when the responder is closed, to trigger a script on AWS Lambda or something which will close the incident via [API](https://docs.opsgenie.com/docs/incident-api). You could also setup a similar solution using Opsgenie Edge Connector (OEC).

Thanks,

Samir


author: serge calderara
body: hello [@Veiko J](/t5/user/viewprofilepage/user-id/1263286) , I need to do the same thing actually but seems a lot of logical approach are a feature request so far.

By the way I would be interrresting to know what is your process of solving a Incident.

What I mean and what is not clear is the use of the Responder Alert created at same time of the Incident which is a copy of the source Alert.

Do you work on the incident starting from the responder Alert, or the incident itself ?

What is the use of this responder alert exactly as based on docuementation is nothing else than pulling notification to responders member.

But the source Alert can do the same , why not working on the source Alert then ?

Simply because it can be off at some time automatically ?

Thanks for advise

regards


Tags: cloud
How build C++ Application under Windows with MinGW?
Asked by Bruce Zhang:

We have a Qt c++ project and compiled with MinGW

How to config the Bamboo to do this?

Thanks.


Answers:
author: Jeyanthan I
body: Hi Bruce,

If you can run this project from a command prompt, you can use [Script task](https://confluence.atlassian.com/bamboo/script-289277046.html) to automate this in Bamboo and configure the plan as usual (like explained [here](https://confluence.atlassian.com/bamboo/getting-started-with-net-and-bamboo-289277288.html)). There is no dedicated task for Qt projects.

Cheers,  
Jey
Auto trigger for multiple repos
Asked by kpitch:

I have a single bamboo plan and added multiple repositories to this plan

and auto trigger is enabled.My plan contains Sourcecode checkout , Maven 3.x

and multiple repositories added to it. Each repo has its own pom file.

1. I need the build for only the committed repository .If my git hub REPO-A got committed ,my build plan should run build for only REPO-A , and not for REPO-B,C etc.,.

2. while i'm having multiple source code checkout how does maven 3.x tasks will work for each repository .

What is the best way to handle it


Answers:
author: Jimmy Seddon
body: Hi [@kpitch](/t5/user/viewprofilepage/user-id/1160021),

What you want to do isn't possible with a single build plan. What we ended up doing was creating one build plan per repo that built what needed to be executed (we are using MSBuild not maven) and we saved the artifacts.

We then have another build plan that aggregates all of the built artifacts into a single package for our release process. This "collector" build plan is triggered upon successful completion of one of the three triggering plans.

This way, you can have the actual build only run for when code is changed, but you will have a single plan you use for the rest of your deployment process that always has the most up to date build artifacts.

I hope that helps!

-Jimmy
Deploy customized
Asked by alvaro_martin:

Hello, I am building some pipelines to build and deploy Big Data jobs to spark. I was happy to see that there is an option of Run Customized for a build plan, but I was really surprised when that option is not available where I actually need it: In the deployment project.

My idea is to version the data, pass input and ouptut directories for the job as parameters, so I can run the same artifacts with different input and output to process different versions of the data.

When I have a chain of jobs (A -\> B) I don't want to re-build B when A outputs some version of the data, just to tell B that it has to run with that version. I would like to be able to specify to B that the latest deployment from A was version a1, so it has to take a1 as input parameter to deploy version b1.

I understand that this automatic linking may be a special use case for jobs, so I thought to make it manual: I will specify the version in a bamboo variable, that I can modify at deployment time. But I didn't find the option in bamboo to do that!, is there already a feature request to implement this? Am I missing something?

P.S. We are defining the pipelines as code with specs, so changing the code where we define the bamboo variables just to deploy with a different input is not what we really want. We need exactly the same pipeline, but with the ability to change the variable at deploy time, so we can say where to read and where to write.

Thanks for your help!


Answers:
author: Jimmy Seddon
body: Hi [@alvaro_martin](/t5/user/viewprofilepage/user-id/4075246),

Welcome to the Community!

We were in a similar situation and we ended up purchasing this marketplace app: [https://marketplace.atlassian.com/apps/1216138/custom-deployments-for-bamboo?hosting=server\&tab=overview](https://marketplace.atlassian.com/apps/1216138/custom-deployments-for-bamboo?hosting=server&tab=overview)

If you are looking for a solution that doesn't cost anything, we were investigating using extra deployment environments and using powershell scripts and some logic to determine which one should be triggered. We decided that the cost of maintaining that would be larger than spending some money on an app.

I hope that helps!

-Jimmy

comments: author: alvaro_martin
body: we don't directly manage our bamboo deployment, so this option is a bit complicated for us. I already thought that the only alternative was that plugin, and I wanted to confirm that. Sad that there isn't a better alternative.

Thanks for your answer.
bamboo.cfg.xml keeps changing ownership
Asked by Paul Farmer:

We have Bamboo (6.10.4 build 61009) installed on a Linux Server. However, we find that if we restart the server, the bamboo.cfg.xml file keeps changing to root:root permissions.

Can't see anything in the startup of the server that would cause this, so has anyone else come across this strange phenomenon?


Answers:
author: Jeremy Owen
body: G'day [@Paul Farmer](/t5/user/viewprofilepage/user-id/3588017)

The *bamboo.cfg.xml* is written to as part of the bootstrapping process, which means the owner of the file will be changed to whichever user is running the Bamboo process.

Is your Bamboo being started as root at any point? Because that will end up with the permissions on the file being changed to root:root (and a few other nasty root owned temporary files / caches being generated that can prevent it from starting under another user).

Cheers,

Jeremy
Upgrading from old version of Bamboo (5.12), cannot find necessary downloads
Asked by Brian Dignin:

I found a page that discusses the upgrade path from Bamboo 5.12 to 7.1, however I cannot find where to download the versions necessary.

Reportedly, I need to download versions 5.14 and 6.5 before going to 7.1. I cannot find the links. Does anyone have any insight?


Answers:
author: Alexey Chystoprudov
body: <https://www.atlassian.com/software/bamboo/download-archives>
How do you enable the viewing of code coverage for a Bamboo plan using Bamboo Specs in YAML
Asked by Tan Yi Long:

I would like to enable the viewing of code coverage using Bamboo specs in YAML as shown in the screenshot below

![Screenshot 2020-09-01 at 11.19.42 AM.png](/t5/image/serverpage/image-id/108649i450B5E99E25DA819/image-dimensions/495x262?v=v2 "Screenshot 2020-09-01 at 11.19.42 AM.png")

I referred to the topic of 'Miscellaneous plugins' in the Bamboo specs documentation but it does not specify the keys which I can use to enable this option. It only provides an example to enable clean working directory after each build

![Screenshot 2020-09-01 at 11.20.52 AM.png](/t5/image/serverpage/image-id/108648iE21A93DA095B32CC/image-dimensions/499x179?v=v2 "Screenshot 2020-09-01 at 11.20.52 AM.png")

Any help would be appreciated and thank you in advance!


Answers:
author: Alexey Chystoprudov
body: Hello, this functionality is not yet available for Code coverage. Please vote and watch progress at <https://jira.atlassian.com/browse/BAM-20990>

comments: author: Tan Yi Long
body: Hi Alexey, thank you for the swift reply! I have upvoted the issue.
How to find Server ID for existing License
Asked by Shawn Weeks:

While setting up Bamboo using Docker I accidentally deleted my volume after I had already created my license. How do I find the server id associated with my license key? I don't see the server id listed on the my licenses page and I have no way of getting back from the volume.


Answers:
author: Mikael Sandberg
body: Hi [@Shawn Weeks](/t5/user/viewprofilepage/user-id/4069508),

Welcome to Atlassian Community!

Your license should still work, it is not tied to the server ID. The server ID that you provide when first getting the license is only used internally by Atlassian.

comments: author: Shawn Weeks
body: After trying again that worked but when I first tried it I was getting a license error. I must have copied and pasted something wrong.
How to configure Bamboo to use a JNDI Location?
Asked by Prashasti Gupta:

I'm not able to understand this point given in the documentation : Configure Bamboo to use a **JNDI Location** of `java:comp/env/mail/GmailSmtpServer`. Note that the JNDI Location is case sensitive and must match the resource name specified in `server.xml`.


Answers:
author: Sujeet Kumar
body: In the drop down while setting up email server in 'Email Settings' use JNDI instead of SMTP. You have to enter "java:comp/env/mail/GmailSmtpServer" as is.

Just ensure that you enter the Gmail setup resource tag inside \<Context\> tag in Server.xml

and don't forget to restart server after making changes in Server.xml file
Different merging strategy for release branches in Bamboo Specs
Asked by Andreas Eriksson:

I have been trying to create a bamboo.yaml that both creates new plan branches for pull requests and plan branches for all release/.\* branches.

Is it possible to create a specification that has different integration for different plan branches?

```

branches:
? ? create:
? ? ? ? for-new-branch: release/.* 
? ? delete:
? ? ? ? after-deleted-days: 14
? ? ? ? after-inactive-days: 14
```

```
branches: 
    create: for-pull-request
    integration:
        merge-from: ${bamboo.repository.pr.targetBranch}
        push-on-success: false
    link-to-jira: true
    
```

I don't want the release branches to merge with anything when built but plan branches from PRs should always be merged with the target branch.


Answers:
author: Charlie Misonne
body: Hi Andreas

I'm looking for the same thing. Did you find any solution?

comments: author: Andreas Eriksson
body: I never did. We reverted back and are not using specs anymore.


author: Charlie Misonne
body: Oh ok. After digging deeper today I found Bamboo 7.1 supports branch overriding for several things including branch-config -\> integration.

<https://docs.atlassian.com/bamboo-specs-docs/7.1.4/specs.html?yaml#overriding-branch-settings-using-bamboo-specs>

I have to update to Bamboo 7.1 so I haven't tested yet.


author: jodyfanning
body: Did anyone get this to work? I want exactly the same thing.

Normal development branches are created by pull-request, and those have a merge strategy. But a release branch should be created just from a named branch, and it should not merge.

I have created the YAML spec from [how I understand it should be](https://docs.atlassian.com/bamboo-specs-docs/7.2.5/specs.html?yaml#overriding-branch-settings-using-bamboo-specs), but it doesn't do anything.

```
branches:
  create: for-pull-request
  delete:
    after-deleted-days: 0
    after-inactive-days: 60
  integration:
    push-on-success: false
    merge-from: core-build
  link-to-jira: true
branch-overrides:
  -
    ^test_.*$:
      branch-config:
        create:
          for-new-branch: ^test_.*$
        delete:
          after-deleted-days: 0
          after-inactive-days: 5
        link-to-jira: true
```

I create a branch in git matching the regex, but I still don't get any branch appearing automatically.


Tags: spec

yaml
Getting a Service Unavailable error after server startup
Asked by Derek Clarke:

Hi,

I installed bamboo on an EC2 instance using the bamboo-server-ec2-wizard.jar file. After installation I was able to configure bamboo and installed a couple of other plugins. I also was able to restart the EC2 instance and everything was working fine.

It's been a couple of months since I last logged onto the server and the Ec2 instance has been sitting in a stopped state. This morning I started the Ec2 Instance and tried to log onto the bamboo, however when I load the URL I get a Service Unavailable error page:

*The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.*

*Apache/2.4.18 (Ubuntu) Server at bamboo.\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*.com Port 443*

I have restored the earliest backup from of the EBS volumes from 2 weeks ago, but that hasn't made any difference. I also checked the storage on the server and both volumes still have loads of space on them.

I'm not an expert in Linux or Ubuntu, and I'm at a loss as to what to try next. Any pointers would be greatly appreciated.

I can also see that the bamboo service is up and running on the server:

**ubuntu@ip-10-0-4-113**:**/media/atlassian-data**$ systemctl status bamboo

**?** bamboo.service - LSB: Atlassian Bamboo Server

Loaded: loaded (/etc/init.d/bamboo; bad; vendor preset: enabled)

Active: **active (exited)** since Fri 2020-08-28 15:29:30 UTC; 12min ago

Docs: man:systemd-sysv-generator(8)

Tasks: 0

Memory: 0B

CPU: 0

Aug 28 15:29:29 ip-10-0-4-113 su\[1216\]: Successful su for bamboo by root

Aug 28 15:29:29 ip-10-0-4-113 su\[1216\]: + ??? root:bamboo

Aug 28 15:29:29 ip-10-0-4-113 su\[1216\]: pam_unix(su:session): session opened for user bamboo by (uid=0)

Aug 28 15:29:30 ip-10-0-4-113 bamboo\[1213\]: \[1B blob data\]

Aug 28 15:29:30 ip-10-0-4-113 bamboo\[1213\]: Bamboo Server Edition

Aug 28 15:29:30 ip-10-0-4-113 bamboo\[1213\]: Version : 7.0.4

Aug 28 15:29:30 ip-10-0-4-113 bamboo\[1213\]: \[19B blob data\]

Aug 28 15:29:30 ip-10-0-4-113 bamboo\[1213\]: If you encounter issues starting or stopping Bamboo Server, please see the Troubleshooting guide at <https://confluence.atlassian.c>

Aug 28 15:29:30 ip-10-0-4-113 bamboo\[1213\]: Tomcat started.

Aug 28 15:29:30 ip-10-0-4-113 systemd\[1\]: Started LSB: Atlassian Bamboo Server.


Answers:
author: Gonchik Tsymzhitov
body: Hi!

did you used the latest version?

We had almost the same, only on 7.2 is starting to work like a charm
Bamboo skips commits for building
Asked by danieldaeschle:

Our Bamboo plan has a configuration to trigger on every commit (Bitbucket Server repository triggered).

Sadly, some commits doesn't trigger the Bamboo plan to run.

You can see that there are two PullRequest merges which result in one build. But they should result in two builds, one for each.![bamboo-bug.png](https://community.atlassian.com/t5/image/serverpage/image-id/108308i8F769E2C1B1FDF63/image-size/large?v=v2&px=999 "bamboo-bug.png")

Does someone know why this could happen or how it could be fixed?


Answers:
author: Jeyanthan I
body: Hi [@danieldaeschle](/t5/user/viewprofilepage/user-id/3708021) ,

I can think of 2 possibilities:

* You might have **quiet period** configured in this linked repository. This is the time Bamboo should wait for any new change before initiating a build. If these 2 pull requests have happened consequtively, these both could have triggered just one build.
* You have configured Exclude changesets under this linked repository definition. If a [regular expression](http://docs.oracle.com/javase/6/docs/api/java/util/regex/Pattern.html) in this field matches the commit messages, it will be excluded from triggering a build.

There can be other factors like network problem influencing this. You may get more details from your atlassian-bamboo.log.

Cheers,  
Jey

comments: author: danieldaeschle
body: Both are deactivated.


author: danieldaeschle
body: Any other suggestion?
Example of splitting Bamboo Java Specs across multiple files
Asked by Thomas Stepp:

For example, I want to maintain a separate file per each Bamboo job. Then in a Bamboo plan file, import the job files and place job definitions withing stages. All of this using Java Specs. Can you please provide some simple examples including folder structure, import code, and code for using an imported job within a stage?

**EDIT:**

Just to clarify, I want my Bamboo Specs files stored in my BitBucket repository, and for Bamboo to scan/read them from BitBucket. I do not want to manually publish from my desktop.


Answers:
author: Thomas Stepp
body: Just to clarify, I want my Bamboo Specs files stored in my BitBucket repository, and for Bamboo to scan/read them from BitBucket. I do not want to manually publish from my desktop.
Crowd/Jira synchronization for newly created users
Asked by tmv:

We have a Crowd/Jira integration. Whenever we create a new user through the CrowdClient, the user doesn't show up in Jira until the specified Synchronisation Interval which can be set to as low as 1 minute. This situation is also true when creating a user through the Crowd admin console. We require that when a user is created, he is able to be able to log into Jira immediately after the registration process. Is there a way to tell Crowd to sync up with Jira immediately after a user is created in Crowd? Right now after the registration process, we have to ask the user to wait for at least 1 minute before he can access Jira.

I'm on Crowd version Version: 2.3.6 (Build:#528 - 12-12-2011) by the way, but the Affects Version said that version is invalid for some reason so I have to choose 2.4.0.


Answers:
author: Bruno BLAISE
body: Hi,

We have the same problem and after a long discussion around a support issue, the support team admitted that it is a bug and <https://jira.atlassian.com/browse/JRA-26882> has been created.

Please vote and watch.

Bruno
Changing the DN for groups of a Crowd MS AD directory: How to proceed?
Asked by Elvir Hadzic:

We use Crowd with an MS AD (LDAP connector) directory. Until now we had the users and user groups in the same location in our AD. For various reasons we now want to move the user groups to a different location. We **do not** want to create a new directory in Crowd however. If at all possible, we'd like to just reconfigure the one we use now. Do we have to expect any problems? How do we proceed?

Do we first move the groups within the Active Directory and then set the User DN in the Crowd directory configuration or do we first set the new Group DN in the Crowd directory configuration and then move the groups in the Active Directory?

The most crucial thing is that we don't have to reasign the users to the groups. The information concerning which user belongs to which group has to be preserved, no matter what.

Thanks in advance!


Answers:
author: fsim
body: Hey Yuk,

When you say move the user groups to a different location, will they still be sitting in the same Active Directory? If they are, then this should not be an issue (and if you are using an LDAP connector, the synchronization would preserve the memberships despite the new Group DN), but it's best that you do it this way:

1. Set the new Group DN in the Crowd directory configuration

2. Shutdown Crowd temporarily while you move the groups in AD

3. Start up Crowd, which will trigger a full AD sync.

Hope that helps.

Regards,

Foogie


author: Andrew Serff
body: We are in a simular situation. Our company has split, so we are migrating to a completely new AD forest. Is there a way to map the users within Crowd when we do this? I'm assuming we need to set up a new Directory in Crowd to authenticate to, but then all the users will look "new" when they are using the applications. It would be nice if we could map them to their old accounts somehow. Is this possible? Or are there other considerations we need to take into account when we do this migration?


Tags: active-directory

group

ldap
Importing Confluence linked to Crowd fails
Asked by Ray Scott:

I have previously tried to import a Confluence back up that was linked to a Crowd instance directory, but it would not import to OnDemand saying that it didn't know anything about the Crowd directory the backup was linked to. Is there a way to overcome this issue? Unfortunately, I cannot get into this Confluence instance to change settings as it was hosted on the Rackspace Cloud and I have long since shutdown the server, so that IP address has been assigned to a different Rackspace Cloud customer and Confluence won't migrate to another machine with a different IP address.


Answers:
author: LucasA
body: Hi,

Confluence imports to OnDemand have to be done space-by-space. Please check this document about Wiki importing inside OnDemand: <https://confluence.atlassian.com/display/AOD/Importing+wiki+data>

Lucas


Tags: cloud
Binding to multiple active directory domains with the same credentials
Asked by David Donn:

Hi,

I have multiple active directory domains. There is a trust relationship between these domains. I believe this should mean that I can bind to any directory with the same credentials. However, the credentials only work for the domain which has the authenticating user in its local domain and not for the other domains.

I am using regular binding, not SSL etc.

Sorry for my poor description of active directory. I don't have much knowledge in that area.

Is it possible to share credentials for binding in this way? Or will I need a separate user for each domain.

Cheers,

David


Answers:
author: Rodrigo Girardi Adami
body: Hi David,

I'm not sure if you have seen this improvement request opened for Crowd?

<https://jira.atlassian.com/browse/CWD-2978>

"Provide ability to sync objects (users/groups/memberships) from another forest through Active Directory's external/forest trust"

I do believe this would be part of your request as well to make it work while using multiple AD domains (forests)

I recommend to vote and ask your colleagues to vote as well to increase the chance to implemented in the future.

Cheers,

Rodrigo


author: Gajan UMAPATHY
body: Hi David, have you manged to work this out?

Cheers,

Gaj