youngmon/atlassian-qna huggingface dataset:
Slack integration advanced alert filtering based on multiple tags
Asked by Stanislav Udartsev:

Hello,   

I'm trying to configure Slack integration to send Kubernetes alerts to different Slack channels based on different set of tags.   

I would like to implement something like:

```
IF cluster=staging AND (namespace=airflow OR namespace=kafka OR namespace=flink)
```

<br />

Alert Filter with **Match all conditions below** is not working with "OR" operator:  
![image.png](/t5/image/serverpage/image-id/333273i8597EFFAFBCF1D45/image-size/large?v=v2&px=999 "image.png")

<br />

Alert Filter with **Match one or more conditions below** leads to receiving all alerts from staging cluster that not meet the initial requirement.   

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

Is it possible to configure Slack integration with advanced filtering that can combine "AND" and "OR" operators?


Answers:
author: Tejaswi G
body: Hey

Thank you for reaching out to Atlassian Community. This is Tejaswi from the Opsgenie Team.

You can't achieve your use case with a single integration, so you need to use multiple Slack integrations. In Opsgenie, we cannot combine "AND" and "OR" operators.  
You can split your conditions like the below and add the below condition in the alert filters of the slack integration.

Slack integration 1:  
cluster=staging AND namespace=airflow
![2024-07-05_16-17-23.png](https://community.atlassian.com/t5/image/serverpage/image-id/333679i40CC9B2613AD95CD/image-size/large?v=v2&px=999 "2024-07-05_16-17-23.png")  
Slack integration 2:  
cluster=staging AND namespace=kafka  
![2024-07-05_16-18-47.png](https://community.atlassian.com/t5/image/serverpage/image-id/333680i511F8D6CEFEC57CE/image-size/large?v=v2&px=999 "2024-07-05_16-18-47.png")

Slack integration 3:  
cluster=staging AND namespace=flink  
![2024-07-05_16-19-40.png](https://community.atlassian.com/t5/image/serverpage/image-id/333681i847F7FEBC7975149/image-size/large?v=v2&px=999 "2024-07-05_16-19-40.png")  
Kind Regards,  
Tejaswi


Tags: alert

cloud

filter

integration

opsgenie-cloud

slack
Git tag a specific commit hash
Asked by Philipp:

Requirements:

- Build runs in a docker container

Usecase:

1. I have 10 builds that builds an artifact that is shared with the deployment

2. In the deployment I download the artifact and want to upload it into an artifact repository.

3. Now I deploy build #7 out of the 10 builds.

4. I want to tag the commit that was used at build #7 to build my artifact but the tagging needs to happen in the deployment.

How do I do that?

I am able to tag in an deployment but I have no way to push the tag.

That code is able to create a tag on my specific commit:  

```
export TAG_HASH=384a34eaa1c1ee58ce198fabd95831dddd3cc4b8

export TAG_NAME=0.0.1

git tag -a ${TAG_NAME} ${TAG_HASH} -m "${TAG_HASH}"

echo "Tag done"
```

Hence our bamboo uses ssh keys with bitbucket and I use a container build I am not able to push via my script.

The only way to push is with the bamboo task vsc push. But with that task it does not push git tags as well.

And the other option to use the bamboo task "git tag" I can only tag the latest commit, so that is also no option for me.

How can I solve this?


Answers:
author: Jyothi Charupalli
body: Hi [@Philipp](/t5/user/viewprofilepage/user-id/4561330) ,

Welcome to Atlassian Community!

We understand that you want to tag a specific commit in the remote repository from Bamboo through a script task.

We have a below Bamboo KB article which explains the same and how to setup ssh keys to authenticate remote repository through script task.

[How-to-push-a-repository-tag-for-a-specific-commit-from-bamboo-to-a-remote-repository-1333329967.html](https://confluence.atlassian.com/bamkb/how-to-push-a-repository-tag-for-a-specific-commit-from-bamboo-to-a-remote-repository-1333329967.html)

Please also refer to the KB article for a more detailed explanation of [How to set up an SSH key-pair for a Bitbucket repository from Bamboo](https://confluence.atlassian.com/bamkb/how-to-set-up-an-ssh-key-pair-for-a-bitbucket-cloud-repository-from-bamboo-1115153587.html). Even though it explains for the Bitbucket Cloud repository same steps mentioned under the section **To generate SSH key-pair:** can be followed for generating SSH key pair for the Bitbucket server repository as well.

I hope this helps!

Best Regards,

Jyothi  
**\*please don't forget to Accept the answer if your query was answered\*\***

comments: author: Philipp
body: I know that is an option but than I have to handle a secret myself and make sure the keys are in all repos that I want to tag.

A more comfortable way would be to enable the internal bamboo task "Repository Tag" to have a parameter that uses the hash to tag of a specific commit. So bamboo can use the existing keys generated by the linked repository.

Is there maybe already a ticket for that feature that I can upvote?


Tags: git-tag
Where is the information about Git caches taken from?
Asked by Udo Hagemann _Decadis AG_:

Hi,

hope there is an answer out there:

In Bamboo Data Center, you find in *Bamboo administration / Repository settings / Manage caches / Git* information about cache directory locations.

After migrating to a test instance and moving from local agents to remote agents, we still find cache directory locations, but they do not exist at all. Trying to delete them doesn't work, even if you create a fake directory on the server - in that case, the directory is removed, but the cache directory location still doesn't go away.

Where is this information retrieved from? I couldn't find anything in the database, not in the shared-home.


Answers:
author: Jyothi Charupalli
body: Hi [@Udo Hagemann _Decadis AG_](/t5/user/viewprofilepage/user-id/4357514) ,

Welcome to Atlassian Community!

Below is the Bamboo source code, how it figures out the list of cached dirs:

```

for (final ImmutablePlan plan : cachedPlanManager.getPlans(ImmutableChain.class)) {
customVariableContext.withVariableSubstitutor(customVariableContext.getVariableSubstitutorFactory().newSubstitutorForPlan(plan), () -> {
for (final GitRepository gitRepository : GitRepositoryFacade.GIT_REPOSITORIES_OF_PLAN.apply(plan)) {
final File cacheDir = gitRepository.getCacheDirectory();

plans.put(cacheDir, plan);
repositories.computeIfAbsent(cacheDir, key -> gitRepository.getSubstitutedAccessData());
}
});
}

```

The code goes through plans, checks what repositories they are connected to and computes the stuff you see on the cache page based on the configuration.

The cache dir (the hash part) is calculated based on repository data (URL + auth data IIRC).

In short: it looks like there must be a reference to the repository URL somewhere. Perhaps an override in PROJ \> PLAN?

So, there must be a repository that resolves to that particular magic string(hash code) and where that URL shown in the description comes from. We also know that it's somehow referenced from PROJ -\> PLAN.

We suggest you check if any of the repository configurations referring to the repository URL still exist.

Could you please try deleting the old repositories(Plan or Project or Global Linked Repos) linked to those git repositories caches and see if the entry disappears from the Bamboo Overview \>Repository setting tab?

I hope this helps. Please let us know in case of any further queries.

Thanks and Regards,

Jyothi  
**\*\*please don't forget to Accept the answer if your query was answered\*\***

comments: author: Udo Hagemann _Decadis AG_
body: Hi [@Jyothi Charupalli](/t5/user/viewprofilepage/user-id/4655226) ,

thank you so much, that gave me a much better understanding of what the page is meant for and where the data is retrieved!
Plans are going in queue only in new created Bamboo DC with LTS 9.6
Asked by Abhishek Bebni:

I created new Bamboo DC with LTS 9.6 and I can see some remote agents are already running in online mods but still when I run any plan, plan is not running and going into queue only and showing message that none agent is in online mode. Please suggest how we can run any plan or make the remote agents online so that plan can be run in Bamboo DC.

Thanks \& regards

Abhishek Bebni


Answers:
author: Anik Sengupta
body: Hi Abhishek,

Thanks for contacting Atlassian community .

Looks like after upgrading to Bamboo DC 9.6 the build plans are been queued for building for an extended duration and is not showing on the Build activity dashboard as queued. You have Agents capable of processing the build available but it remains queued for an excessive period.

A large delay between queueing and it appearing in the build queue suggests that the server-side change detection process is taking longer (see further down for more information on the build workflow). It's helpful to understand the basics of the Bamboo build plan workflow to understand where the issue might be when the symptoms present:

A build plan is triggered.  
Plan changes status to queued.  
Change detection happens on the server-side. This is where it will reach out to the repository to determine if there are any changes it needs for the build and is the most likely breakdown point when observing queued builds that aren't yet in the build queue.  
Plan is then added to the build queue. This is when it shows up on the Build activity dashboard.  
Server assigns an agent for it and sends an event to the agent.  
Agent receives the event and starts building.

It's important to note that this behavior is normal however we've observed a few causes for abnormally long server-side change detection:

This has been described here - <https://confluence.atlassian.com/bamkb/build-plan-queued-for-extended-duration-and-not-showing-on-build-activity-dashboard-as-queued-in-bamboo-834220865.html>

Also please check on the agrnt dedication if the p;lan had few dedicated agents and if those agents are online ready to acceot the build.

Please note local agents have been removed from Bamboo 9.6 if you have any plans which were previously build in local agents you need to switch them to remote agents to make sure they have the right capabilities for building.

Thanks

Anik Sengupta

**\*\*please don't forget to Accept the answer if your query was answered\*\***


Tags: bamboo-plugin-development

data-center
About Bamboo using 54664 Port
Asked by Owen Chen:

Hi,

I currently need to explain the Port used by Bamboo to the security department. I saw that Port 54664 is used in Atlassian's document, but I still don't quite understand the description in the article. Here are my questions:

1. Under what circumstances is Port 54664 used? Is this necessary to open?
2. The description mentions "only required for remote agents connection over SSL". How do I know what version of SSL it is?

Hope someone can assist me, thanks.

Owen


Answers:
author: Shashank Kumar
body: Hello Owen,

Welcome to Atlassian community
> 1. Under what circumstances is Port 54664 used? Is this necessary to open?

Bamboo will use 54664 when SSL is enabled for **bamboo.jms.broker.client.uri** in bamboo.cfg.xml file for SSL communication with the remote agent. if SSL is not used in **bamboo.jms.broker.client.uri**then there is no need to open port 54664

\<property name="bamboo.jms.broker.client.uri"\>failover:(tcp://bamboo921:54663?wireFormat.maxInactivityDuration=300000)?initialReconnectDelay=15000\&amp;maxReconnectAttempts=10\</property\>

Bamboo spins up two additional JMS connectors to handle SSL and elastic agent traffic. Bamboo looks at the primary JMS connector port number to determine the port numbers it will use for the additional connectors. This is the formula used by Bamboo:

* SSL JMS connector = primary JMS connector port number + 1. If the primary JMS connector is 54663, then Bamboo will use **54664** for the SSL JMS connector.
* Elastic agents JMS connector = primary JMS connector port number + 2. If the primary JMS connector is 54663, then Bamboo will use **54665** for the elastic agents JMS connector. This connector is bound to **localhost**, by default.

> 2. The description mentions "only required for remote agents connection over SSL". How do I know what version of SSL it is?

I think this depends upon what version of SSL is installed in your machine, you can check this using command \> openssl version

Regards,

Shashank Kumar

**\*\*please don't forget to Accept the answer if your query was answered\*\***


author: Owen Chen
body: Documentation: <https://confluence.atlassian.com/kb/ports-used-by-atlassian-applications-960136309.html>


Tags: jms

port
cannot access Bamboo at present
Asked by dixith kumar bura:

Bamboo bootstrap failed: Your Bamboo instance could not start because health check failed.


Answers:
author: Shashank Kumar
body: Hello Dixith,

Welcome to Atlassian community.

You can check the error inside **\<bamboo-home\>logs\>atlassian-bamboo.log** file and see why this error message is coming.

Regards,

Shashank kumar

**\*\*please don't forget to Accept the answer if your query was answered\*\***
remote agent went offline while building
Asked by Dale Binkley:

I have 3 remote agents installed on a single server. During a build the remote agent that was running the build just went offline without an apparent reason. The job result summary page shows the status as 'not built'. The other 2 agents were unaffected and remained online. The agent was manually restarted using systemctl.

Any ideas what happened? And more importantly how can this be prevented in future?


Answers:
author: Shashank Kumar
body: Hello Dale,

Welcome to Atlassian community.

You can check the below 2 files on the remote agent to understand what happened when the agent was running possibly memory issue would have caused it to fail.

\* \<bamboo-agent-home\>logs\>atlassian-bamboo.log

\* \<bamboo-agent-home\>atlassian-bamboo-agent.log

Regards,

Shashank Kumar
Have a Bamboo build Plan attempting to run frontend-maven-plugin to execute npm (node-npm-install)
Asked by GSHerber:

We have a Bamboo build Plan attempting to run frontend-maven-plugin to execute npm (node-npm-install). Attempts to pass the Nexus npm proxy URL like '-DproxyHost=proxy.url' have been unsuccessful. Our environment has no direct internet access so the builds have to go to internal Nexus for dependencies. It seems like params passed to Maven don't get passed to the plugin. Has anyone encountered this issue? Any help would be appreciated.

Bamboo log snippet below of the failed plugin run.

```
build	09-Apr-2024 11:29:29	[INFO] --- frontend-maven-plugin:1.15.0:install-node-and-npm (node-npm-install) @ radsAdminWeb ---build	09-Apr-2024 11:29:29	[INFO] Installing node version v20.11.0build	09-Apr-2024 11:29:29	[INFO] Downloading https://nodejs.org/dist/v20.11.0/node-v20.11.0-win-x64.zip to C:\Users\SVC-GDIT-PROD-Bamboo\.m2\repository\com\github\eirslett\node\20.11.0\node-20.11.0-win-x64.zipbuild	09-Apr-2024 11:29:29	[INFO] No proxies configuredbuild	09-Apr-2024 11:29:29	[INFO] No proxy was configured, downloading directlyerror	09-Apr-2024 11:29:29	Apr 09, 2024 11:29:29 AM org.apache.http.impl.execchain.RetryExec executeerror	09-Apr-2024 11:29:29	INFO: I/O exception (java.net.SocketException) caught when processing request to {s}->https://nodejs.org:443: Connection reseterror	09-Apr-2024 11:29:29	Apr 09, 2024 11:29:29 AM org.apache.http.impl.execchain.RetryExec executeerror	09-Apr-2024 11:29:29	INFO: Retrying request to {s}->https://nodejs.org:443error	09-Apr-2024 11:29:29	Apr 09, 2024 11:29:29 AM org.apache.http.impl.execchain.RetryExec executeerror	09-Apr-2024 11:29:29	INFO: I/O exception (java.net.SocketException) caught when processing request to {s}->https://nodejs.org:443: Connection reseterror	09-Apr-2024 11:29:29	Apr 09, 2024 11:29:29 AM org.apache.http.impl.execchain.RetryExec executeerror	09-Apr-2024 11:29:29	INFO: Retrying request to {s}->https://nodejs.org:443error	09-Apr-2024 11:29:29	Apr 09, 2024 11:29:29 AM org.apache.http.impl.execchain.RetryExec executeerror	09-Apr-2024 11:29:29	INFO: I/O exception (java.net.SocketException) caught when processing request to {s}->https://nodejs.org:443: Connection reseterror	09-Apr-2024 11:29:29	Apr 09, 2024 11:29:29 AM org.apache.http.impl.execchain.RetryExec executeerror	09-Apr-2024 11:29:29	INFO: Retrying request to {s}->https://nodejs.org:443
```


Answers:
author: Shashank Kumar
body: Hello [GSHerber](https://community.atlassian.com/t5/user/viewprofilepage/user-id/2093058)

Welcome to Atlassian community.

Can you tell me which exact task you are using in Bamboo and in which field you are passing -DproxyHost=proxy.url the parameter?

If you can provide a screenshot it will be easy ti understand.

Regards,

Shashank Kumar


Tags: server
Does the "Sleep" command only affect that thread or anything else on the server?
Asked by Phumelele Mthimunye:

So in a project i am deploying through bamboo, there is code to add a record to the database should it not exist on startup. Problem is both servers that we deploy to start up at almost the exact same time (milliseconds apart) so after the one server starts up and adds the record, the other server would add the same record as the check to see if it record exists happens too early.  

so a solution i thought of was adding an ssh task with a sleep command in-between the tasks deploying the project onto the servers. i did do some testing to see if other API calls on the server would be affected while the deploy is sleeping but it seems that they work fine as the deploy is sleeping.  

is there any other possible issues i should be aware of and/or testing for when implementing this sleep command?


Answers:
author: Ayrijit Swain
body: Hi Phumelele,

Welcome to Atlassian community.

If i understand your concern correctly, you wanted to confirm if using "sleep" in bamboo task will only affect the build job in which it is configured OR any other process in Bamboo.

To answer your questions, it will only affect the build job and will pause the execution of that job. Other build jobs being executed in parallel will not be affected by this.

Regards,

Ayrijit Swain

**\*\*please don't forget to Accept the answer if your query was answered\*\***
How to get Server ID on Bamboo DataCenter without the server running
Asked by Stuart Jarriel:

I am trying to upgrade a Bamboo server to Bamboo DataCenter.

I made a VM clone of the Bamboo Server (8.2) and am working on the clone.

I need to get the server ID from the clone so I can request a trial DC license, but the bamboo server on the clone will not start. Is there a way to get the server ID from bamboo without a running server?


Answers:
author: Ayrijit Swain
body: Hi Stuart,

Welcome to Atlassian community.

You can get the server ID from the *\<bamboo-home\>/bamboo.cfg.xml* file against the *\<property name="serverId"\>* parameter.

Regards,

Ayrijit Swain

**\*\*please don't forget to Accept the answer if your query was answered\*\***


author: Anik Sengupta
body: Hi Stuart,

Thanks for reaching out to Atlassian community.

Please follow the below KB which talks about how to get the server ID in Bamboo.

<https://confluence.atlassian.com/bamkb/how-to-find-the-server-id-in-bamboo-1209876913.html>

### Manually in the filesystem {#toc-hId-2117773945}

1. Go to **\<bamboo-home-directory\>** and open the **bamboo.cfg.xml**file.
2. The Server ID can be found at the **\<property name="serverId"\>** line:

**Best Regards,**

**Anik Sengupta**

**\*please don't forget to Accept the answer if your query was answered\***
"Something went wrong" when trying to delete application link
Asked by rahul sharma:

How to enable the DELETE function in the apache proxy so we can send API and normal web requests that include delete tasks.


Answers:
author: Shashank Kumar
body: Hello Rahul,

Welcome to Atlassian community

I am not sure I got your question, can you explain with an example what you are trying to do and what error you got?

Regards,

Shashank Kumar
Is it possible to upgrade from Bamboo v9.2.11 LTS to v9.6.0 LTS?
Asked by Sneh Patel:

I was wondering if it was possible to upgrade directly to Bamboo v9.6.0 LTS from v9.2.x LTS directly? According to <https://confluence.atlassian.com/bamboo/bamboo-upgrade-guide-720411366.html> , it says "If you're on **Bamboo 8.x.x through 9.4.x**, upgrade to 9.5.x directly." I was wondering if we needed to upgrade to 9.5.x first and then 9.6.0.


Answers:
author: Shashank Kumar
body: Hello Sneh,

Welcome to Atlassian community.

Yes you can upgrade to Bamboo 9.6 directly if you are on Bamboo 9.2, the documentation will be updated shortly, we have a raised a documentation bug for that.

Regards,

Shashank Kumar

**\*please don't forget to Accept the answer if your query was answered\*\***


Tags: upgrade
SAML SSO is incompatible with bamboo version 9.6.0 LTS
Asked by Archana Pathak:

We are using SAML SSO for bamboo login.

We have upgraded bamboo qa instance from 9.2.7 LTS to 9.6.0 LTS. I can see SAML SSO is incompatible with 9.6.0.

Please refer attached screenshot:

![sso.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/315075i4F98024D0A7C6DD0/image-size/large?v=v2&px=999 "sso.jpg")

If this is the case we are unable to upgrade our bamboo prod instance to 9.6.0

It will be better if you can guide us how we troubleshoot

Thanks in advance!


Answers:
author: Anik Sengupta
body: Hi Archana,

Welcome to Atlassian community.

If you are referring to third party plugin - <https://marketplace.atlassian.com/apps/1217672/saml-sso-single-sign-on-bamboo-sso-oauth-user-sync/version-history> i see its compatible with Bamboo 9.6.

![Screenshot 2024-03-28 at 4.24.10 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/315081i8EA4100DB324C0A2/image-size/large?v=v2&px=999 "Screenshot 2024-03-28 at 4.24.10 PM.png")  
Additionally from Bamboo 8.1+ Bamboo Data Center support for single sign-on was introduced.From Bamboo 8.1 we provide support for SAML 2.0, OpenID Connect, and Crowd single sign-on right out of the box. All of these solutions integrate into your existing infrastructure, providing developers with a more secure and hassle-free way to log in.

We support a large list of popular identity management providers including Okta, OneLogin, Azure, Active Directory (ADFS), Bitium, and PingOne.

On top of that, you can also use just-in-time user provisioning and blocking authentication with username and password in the login portal and API calls.

Please find below release notes for more details.

<https://confluence.atlassian.com/bambooreleases/bamboo-8-1-release-notes-1189793877.html>

<https://confluence.atlassian.com/enterprise/saml-single-sign-on-for-atlassian-data-center-applications-857050705.html>

<br />

Best Regards,

Anik Sengupta

comments: author: Archana Pathak
body: Hi [@Anik Sengupta](/t5/user/viewprofilepage/user-id/4672627) ,

After upgrading bamboo to 9.6.0, I can see below error in Manage Apps for SAML SSO.  

![SAMLsso.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/315086iB0E5D56EF0341F59/image-size/large?v=v2&px=999 "SAMLsso.jpg")


author: Anik Sengupta
body: Hi Archana,

That is because you are using version 6.8.4 of the plugin , please upgrade the plugin to 6.9.0 which is compatible with Bamboo 9.6.0 LTS

Thanks

Anik Sengupta

**\*please don't forget to Accept the answer if your query was answered\***


author: Archana Pathak
body: I have upgraded version to 6.9.0. Issue is resolved.

Thanks [@Anik Sengupta](/t5/user/viewprofilepage/user-id/4672627)


Tags: upgrade