youngmon/atlassian-qna huggingface dataset:
Team on call with 3 weeks rotation
Asked by Polna Yuliia:

We have 3 small teams and we would like to have all members of every team to be on call during the working hours for 1 week every 3 weeks. So team 1 is on call this week during working hours, team 2 is on call next week during working hours and so on.

How can such rotation be set up in opsgenie?


Answers:
author: Nick H
body: Hi [@Polna Yuliia](/t5/user/viewprofilepage/user-id/4588203) ,

You'd want to configure this through a "dummy" team. This dummy team would receive all alerts initially, then manage sending them to Team 1-3 through its on-call schedule.

If you were unaware, you can add teams as participants into a schedule's rotation. So you'd want to configure this dummy team's schedule to have all 3 teams as participants, and have alerts send to each team depending on the week they should be on call.

That entire setup might look something like this:

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

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

When a team is used as a participant in a schedule/rotation - and an alert is routed to that schedule with a team being on-call - the alert would flow through the added team's On-call tab; following that added team's routing rules, escalations, and on-call schedules.

You also have the ability to restrict rotations to business hours so this could either be done within the dummy team's schedule, or within Team 1-3's on-call schedules:

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

Here's an example of sending an alert to the dummy team - which then routes the alert to its schedule - and adds Team 1 as a responder since they are on-call. The alert would then notify Team 1's users based on what's configured in Team 1's On-call tab:

![dummy4.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/163927iC4254D3F27398593/image-size/large?v=v2&px=999 "dummy4.jpg")![dummy5.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/163928i7FD7386EB2AD1D1F/image-size/large?v=v2&px=999 "dummy5.jpg")

Hope this helps! Let us know if you have any other questions.
Is there an Opsgenie release roadmap?
Asked by Edmundo Rangel:

I am trying to figure out what is the release version of Opsgenie cloud service that is current running and if there is also a roadmap for future releases that we customers can look at.

The reason I ask to ensure I prepare my users in case there is a new release that changes the way they use Opsgenie on their day-to-date alert management experience.

Also to ensure which features get deprecated, what API changes will happen, etc.

Thanks!


Answers:
author: Mikael Sandberg
body: You can find the Cloud roadmap here, <https://www.atlassian.com/roadmap/cloud>

Note that none of the Atlassian Cloud products are using version numbers, they are constantly updated. You can find what is rolling out each week by checking out [Atlassian Cloud Documentation blog posts](https://confluence.atlassian.com/cloud/blog). If you are on the premium plan you will have the option to change the [release track](https://confluence.atlassian.com/x/mdjCP) you are on.


Tags: release

roadmap
Close Alert in zabbix from Opsgenie
Asked by Christopher Ravnborg:

Hi,

i have OpsGenie Edge Connector to ack in zabbix, when acked in OpsGenie.

I have configured OpsGenie to also close in Zabbix, if i press the close button.

I can't really find documentation on how i can do this.

But at this point it does not execute on the zabbix server.

I tried adding a maping like this:  

"Close": {  
"filepath": "path/to/actionExecutorForZabbix4.py",  
"sourceType": "local",  
"env": \[\],  
"stdout": "/home/opsgenie/oec/output.txt"  
}

This fails to start OEC at restart.

What am i missing ? :)

updated: action name was wrong on the mapping


Answers:
author: Christopher Ravnborg
body: Well, i talked to support, and if i need this, i need to add the function to the python script.

The thing is that zabbix does not really care if you resolve the issue.  
If it's resolved, you will, by default, receive a new alert if it's triggered again.

I guess the ackknowledge is what i need.  
Thanks :)

Closing.


Tags: cloud

zabbix
Unexpectedly closed a ticket which is not related to me what to do
Asked by Mohan Ajay Donga:

Hi,

I closed a ticket unexpectedly, which is not related to me and I was new to this tool. So, please help me in solving this issue.

thank you


Answers:
author: Nick H
body: Hi [@Mohan Ajay Donga](/t5/user/viewprofilepage/user-id/4586026) ,

Unfortunately it is not possible to reopen an alert once it's closed. We do have an open feature request for this that I'll get you added though.

In the meantime, it might be worth creating another alert in the Alerts tab, adding the teams / responder the initial alert was sent to, and linking the alert in the description - or something like this. Alert notification flow would then restart through that new alert.

Hope this helps! Let us know if you have any additional questions.

comments: author: Mohan Ajay Donga
body: thank you so much


Tags: cloud
Build warnings artifact location
Asked by Rasti:

Hello.

Following the tutorial at <https://developer.atlassian.com/server/bitbucket/tutorials-and-examples/code-insights-tutorial/> I want to parse clang-tidy build warnings to create code insight report and annotations and post them to Bitbucket.

The Bamboo's built-in feature "Build warnings parser" does a great job in parsing several output formats, including clang and creates a build artifact. That is a zip file containing a well-formatted JSON file with all parsed warnings. This I can download manually from Bamboo UI.

However, I have an issue to find out, how to access this artifact from within a task following my "Build warnings parser"-task. I want to create a task that calls a script to parse the JSON and post the data to Bitbucket as described in the tutorial. But, where is this artifact located? I cannot find it in the build directory on the build agent, nor on the Bamboo server.

I don't want to implement the same functionality as the Build warnings parser already does, namely parse a rather cryptical clang log file, but make use of the build warnings parser output format that is uniform for any build outputs (maven, javac, jslint etc.), so I can reuse my script for posting code insights to Bitbucket for our other projects using other programming languages and their linters.

So my question is - how can I access the "build warnings parser"-artifact from a task?

Any help appreciated.


Answers:
author: rafaelBauer
body: Hello Rasti,

Were you able to get the data from Clang and post it to the Bitbucket code insights?

comments: author: Rasti
body: Hello [@rafaelBauer](/t5/user/viewprofilepage/user-id/3619122) ,

unfortunately, as I didn't get any answer to this question, I'm still on the same stand.


Tags: build

code-insight
Bamboo Agent installation in AIX
Asked by konapala sabarish:

Hi All,

I am looking for a document on installing bamboo agents in IBM Aix server's. So, do we have anyone who installed the agents in Past on Aix servers.


Answers:
author: Michael
body: We have running 3 agents on AIX 7.2. As the user needs special permissions when building our jobs, we use a custom startup script. I did not create this setup but AFAIK if you want to register the agent as subsystem (mkssys, startsrc, stopsrc) you might need a process that doesn't go to background. Our start script launches the bamboo-agent-bootstrap.jar using java and waits for it to exit. You can register the agent as subsystem using this script. Hint: Replace {{ bamboo_agent_home }} with the installation directory path.

Our start script:

```
#!/bin/sh
set -e
trap 'kill $(jobs -p)' EXIT
export LIBPATH=/opt/freeware/lib:$LIBPATH
export LD_LIBRARY_PATH=/opt/freeware/lib:$LD_LIBRARY_PATH
export PATH=/opt/freeware/bin:$PATH

# Working diretory needs to be the path where bamboo-capabilities.properties file is located.
# see https://confluence.atlassian.com/bamboo/configuring-remote-agent-capabilities-using-bamboo-capabilities-properties-289276849.html
cd {{ bamboo_agent_home }}/bin

/usr/java8_64/jre/bin/java -Dcom.ibm.jsse2.overrideDefaultTLS=true -Dcom.ibm.jsse2.overrideDefaultProtocol=TLSv12 \
  -Dbamboo.home={{ bamboo_agent_home }} -Dbamboo.agent.ignoreServerCertName=true \
  -Dlog4j.configuration={{ bamboo_agent_home }}/log4j.properties \
  -jar {{ bamboo_agent_home }}/lib/bamboo-agent-bootstrap.jar {{ agent_server_url }} &
wait
```

And register this script as subsystem:

```
mkssys -s bamboo-agent -p {{ bamboo_agent_home }}/start-bamboo-agent.sh -u bamboo -S -n15 -f9
```

CAUTION: This way the agent doesn't use the conf/wrapper.conf. That's why I want to create another solution. But actually this is working for us.

Bamboo Server v6.10
[SOLVED] Bamboo REST API call to enable/disable remote agent
Asked by David Schweizer:

I can see the following issue/feature request as closed and fixed for version 7.2.0, and it is mentioned in the release notes for version 7.2, but i can not find anything in the documentation/API reference about it:

<https://jira.atlassian.com/browse/BAM-18255>

Has this just been marked as resolved and then accidentally been put into the release notes, or was it implemented and not updated in the documentation/API reference?

SOLVED:

Looked in wrong (old) version API Reference, new version is here:

<https://docs.atlassian.com/atlassian-bamboo/REST/7.2.1/>


Answers:
author: Gonchik Tsymzhitov
body: Thank you [for mentioning to](https://docs.atlassian.com/atlassian-bamboo/REST/7.2.1/)

<https://jira.atlassian.com/browse/BAM-18255>

Time introduce it in our wrapper :) via

[https://docs.atlassian.com/atlassian-bamboo/REST/7.2.0/](https://docs.atlassian.com/atlassian-bamboo/REST/7.2.1/)
Issue with bamboo api calls
Asked by ewsscm:

When we are trying to make api calls to bamboo we get the following response

curl -k 'https://bambooxxxxxxx/rest/api/latest/deploy/project/all' -u username:password

\<html\>  
\<head\>  
\<title\>Internal server error\</title\>  
\<meta name="decorator" content="install" /\>  
\</head\>

\<body\>  
\<h1\>Internal server error\</h1\>

<br />

\<h4\>Go to...\</h4\>  
\<ul\>  
\<li\>\<a href="/"\>Site homepage\</a\>\</li\>  
\</ul\>  
A system error has occurred - our apologies!  
\<p\>  
Please create a problem report on our \<b\>support system\</b\> at \<a href="[https://support.atlassian.com/contact/"\>https://support.atlassian.com\</a]()\> with the following information:  
\<ol class="standard"\>  
\<li\>a description of your problem and what you were doing at the time it occurred  
\<li\>cut \&amp; paste the error and system information found below  
\<li\>attach the \<strong\>atlassian-bamboo.log\</strong\> log file found in your application home.  
\</ol\>  
We will respond as promptly as possible.\<br/\>Thank you!  
\</p\>

\<p\>  
\<b\>Version:\</b\> 6.9.1\<br\>  
\<b\>Build:\</b\> 60910\<br\>  
\<b\>Build Date:\</b\> 04 Jun 2019  
\</p\>

\<h4\>Request information:\</h4\>  
\<ul class="standard"\>  
\<li\>Request URL: https://bambooxxxxxx/500.action\</li\>  
\<li\>Scheme: https\</li\>  
\<li\>Server: bamboo-corp.ews.int\</li\>  
\<li\>Port: 443\</li\>  
\<li\>URI: /500.action\</li\>  
\<li\>Context path: \</li\>  
\<li\>Servlet path: /500.action\</li\>  
\<li\>Path info: \</li\>  
\<li\>Query string: \</li\>  
\</ul\>

<br />

\<p\>  
\<b\>Stack Trace:\</b\>

java.lang.IllegalStateException: XSRF: A mutative operation was attempted on InternalMembership within a non-mutative HTTP request: https://bambooxxxxx/rest/api/latest/deploy/ : \[null\]-\&gt;  
-\&gt;\[\[386695185, 328237456, GROUP_USER, GROUP, KeyLight_Access, keylight_access, , 2021-01-21 11:20:59.162, com.atlassian.crowd.model.directory.DirectoryImpl$HibernateProxy$xJR7flyF@4db106e7\[lowerName=crowd repository,description=


Answers:
author: Steffen Opel _Utoolity_
body: This seems to be related to an XSRF bug that has by chance just been fixed and published in [Bamboo 7.2.2](https://confluence.atlassian.com/bamboo/bamboo-7-2-release-notes-1026526751.html) yesterday:

* [XSRF failure for GET REST requests when Update group membership on login is enabled and user or group membership is updated (BAM-21051)](https://jira.atlassian.com/browse/BAM-21051)

If you are unable to upgrade to Bamboo 7.2.2 right away, the issue lists two workarounds:
>
> ###### Workaround 1 {#toc-hId-107836757}
>
> Use Personal Access Tokens to authenticate with the API instead:
>
> * [Personal access tokens](https://confluence.atlassian.com/bamboo/personal-access-tokens-976779873.html)
>
> ###### Workaround 2 {#toc-hId--1699617706}
>
> Login as the user via the UI so that updates are performed. REST calls will now work until theres another change to the user or their group membership.
bamboo agent installation stuck on windows at "waiting to register on server "
Asked by Rishi.Randhir:

Hello all,

I am trying to install on a windows VM the bamboo agent

- The installation starts normally , and at one point i see that the agent is waiting for registration , I approve the agent in request in the bamboo server websire in Agents section

- After 60 seconds , the agent comes to a standstill at "\[AgentRegistrationBean\] Registering agent on the server,"

2021-01-21 14:37:02,268 ERROR \[ActiveMQ Task-1\] \[FailoverTransport\] Failed to connect to \[ssl://bamboo.abc.com:60001?wireFormat.maxInactivityDuration=300000\&socket.verifyHostName=false\] after  
: 10 attempt(s)  
2021-01-21 14:37:02,278 INFO \[ActiveMQ Connection Executor: unconnected\] \[PooledConnectionFactory\] Expiring connection ActiveMQConnection {id=ID:VMO7222PA073-49537-1611239356960-1:1,clientId=ID:VMO722  
2PA073-49537-1611239356960-0:1,started=false} on IOException: Connection timed out: connect  
2021-01-21 14:37:02,281 WARN \[AgentRunnerThread\] \[RemoteAgent$1\] Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationExcepti  
on: Error creating bean with name 'agentRegistrationBean': Invocation of init method failed; nested exception is org.springframework.remoting.RemoteAccessException: Could not access JMS invoker queue  
\[queue://com.atlassian.bamboo.registrationQueue\]; nested exception is javax.jms.IllegalStateException: javax.jms.JMSException: Connection timed out: connect

I checked with IT and they have opened the port 54663, but the below tests show me otherwise.

I also tried to telnet using telnet bamboo.abc.com 54663 , but connection times out

Also tried ,

PS C:\\Users\\bharathkp-a\> Test-NetConnection -InformationLevel detailed -ComputerName 104.xx.xx.xxx -Port 54663  
WARNING: Ping to 104.214.227.230 failed -- Status: TimedOut  
WARNING: TCP connect to 104.214.227.230:54663 failed

<br />

ComputerName : 104.xx.xx.xxx  
RemoteAddress : 104.xx.xx.xxx  
RemotePort : 54663  
AllNameResolutionResults :  
MatchingIPsecRules :  
NetworkIsolationContext : Internet  
IsAdmin : False  
InterfaceAlias : Ethernet  
SourceAddress : 104.xx.xx.xxx  
NetRoute (NextHop) : 104.xx.xx.xxx  
PingSucceeded : False  
PingReplyDetails (RTT) : 0 ms  
TcpTestSucceeded : False

Should the port 60001 also be opened ?

What do you suggest i should do next ?


Answers:
author: Rishi.Randhir
body: Opening the port 60001 and also opening 54663 worked
bamboo, remote agent authenticated but missing from agent summary list
Asked by bfgcat:

I previously had 3 bamboo agents running on my linux "build" machine connecting to a bamboo server running on Windows. The directory for one of the build agents got corrupted and needed to be deleted. After downloading the installer jar and reinstalling the agent I went on the bamboo server and removed the old agent and authenticated the new agent. The agent is now visible on the authentication list as approved. From this point onward however, the new agent never shows up on the server's Agent Summary page.

Going forward I installed a new remote agent on another linux system, followed the same steps and authenticated it on the bamboo server agent page. At this point the new agent shows up as a remote agent.

Ideas? Suggestions on what logs to look at?

thanks in advance for any help.


Answers:
author: bfgcat
body: Here's an interesting, and frustrating, data point. After initially starting the agent on 1/14 and authenticating shortly thereafter. Now on the agent summary page the agent is there and this line is in the log on that page:

Jan 20, 2021 10:25:55 AM Remote agent "mcsbuild03.**xxxxxxx**.com" has registered.

SIx days??? What the ....?


Tags: remote-agent
Git tag name in variable
Asked by Petr Vejsada:

First - thank to Atlassian team for the feature build can be triggered by git tag. Works well for us.

Now I need to use the tag which triggered the build in shell script. Some variable probably exists:

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

Can I get the tag name "TESTTAG_v_9_9_9" in shell script? What is the variable name?

Thank you in advance.


Answers:
author: Sylwester Jeruzal
body: Unfortunately the tag name is not available as a variable. We've fixed this and it will be released in bamboo 7.2.2.  
This version will be released on 2021-01-25.

After upgrade you can use **bamboo.TagBuildTriggerReason.tagName** variable.

comments: author: Petr Vejsada
body: Just upgrading Bamboo to 7.2.2. It should fix the problem - I'll write a new comment if testing will success. Thanks a lot!

I've to upload compiled artifacts to version subdirectory. For example - if tag is v_6_3_0, I'll upload compiled software somewhere/releases/v_6_3_0/


author: Petr Vejsada
body: Works, perfect!


Tags: git

variable
Passing Argument to Bamboo Spec runner
Asked by Ananth Francis:

Hi,

I am trying to pass an argument to the bamboo spec.  
Unfortunately, my arguments are not passed to my planSpec.

I tried like this. But, its not passing the arguments to the PlanSpec.  
mvn -Ppublish-specs -Dbamboo.specs.log.level=DEBUG -Dexec.args="myArg1 myArg2"

Thanks and Regards!!!  
Ananth Francis.


Answers:
author: Alexey Chystoprudov
body: As Specs processing was designed to be executed at Bamboo Server it doesn't propagate any args to be as safe as possible from security point of view.

comments: author: Ananth Francis
body: Thanks Alexey for the answer.  
We would like to run from different server in our case and currently we are setting couple of environment variables and reading those env in the specs but it looks like it may not be a great idea to do.


author: Alexey Chystoprudov
body: If you use Bamboo Specs at repository and by different servers you mean Bamboo Server, then look at <https://docs.atlassian.com/bamboo-specs/7.2.2/com/atlassian/bamboo/specs/api/context/RssRuntimeContext.html#getServerName--> which allows you to get server name at Specs processing runtime.

We use it internally to setup different plans at different Bamboo Servers but same source code repository


Tags: spec
Separate plan for building Pull Requests
Asked by Rasti:

Hello,

we are using Bamboo 7.2.1 and were wondering if there is an option to create a build plan that only builds pull requests of a given repository. The thing is that a pull request build should not execute the maven deploy task, but only maven verify.

We make use of the built-in Bamboo feature to create plan branches when a pull request is created, the problem is, that we cannot distinguish within the plan, whether it is running for a branch or for the master.

Any help is really appreciated.

Thanks


Answers:
author: Alexey Chystoprudov
body: There's runtime variable which has branch name so you can check at some script task or task condition if it's master or dev branch. More details at [https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html](https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html?)

comments: author: E-Rock
body: Got a new link for this dead link?


Tags: branch

pull-request
Trigger build only if a PR is open
Asked by Mihails Kuzmins:

I use a Bitbucket server (7.7.1) with a Bamboo server (7.2.1), so there is a default trigger **Bitbucket server repository trigger** which is triggered whenever there is a push to the branch.

This is not the behaviour I expect because my required behaviour is that a build is triggered only when there is an open PR for this branch (e.g. merging the branch into develop). Is there any way it can be achieved?


Answers:
author: Mihails Kuzmins
body: Actually I have found a solution. I needed to go to *Edit plan* -\> *Branches* and select **When pull request is created**. In this case Bamboo creates a new sub-plan for the branch and triggers a build. This is exactly what I require

![aaa.JPG](https://community.atlassian.com/t5/image/serverpage/image-id/125994i55D7C6F2B01E8FB4/image-dimensions/684x167?v=v2 "aaa.JPG")
How to add delay between 2 bamboo plans without holding agent?
Asked by balu t:

Hi All,

I have a bamboo Plan A and Plan B.

Plan B needs to get executed 30 mins after Plan A. I don't want to hold any agents for this delay.

Any pointers on how to achieve this ?


Answers:
author: Ashish Agrawal
body: Hello [@balu t](/t5/user/viewprofilepage/user-id/4224105), I am looking for a solution to the exact same use case. Were you able to get a solution? Thanks.
Is there a way to update bamboo scheduler via API ?
Asked by balu t:

Hi All,

Is there a way to update bamboo scheduler(Trigger configuration) via API ?


Answers:
author: Pramodh M
body: Hi [@balu t](/t5/user/viewprofilepage/user-id/4224105)

Currently, there is an API for only to get the info of the scheduled build. <https://developer.atlassian.com/server/bamboo/bamboo-rest-resources>

Please see <https://docs.atlassian.com/atlassian-bamboo/7.2.1> - **ScheduledJob Class**if you are using custom scripts

Thanks,  
Pramodh


Tags: api

schedule
Whitelisting IP addresses for Statuspage
Asked by Der Dooley:

Ive searched through the site but cant find any detail on how to set up IP address whitelisting for Statsupage. How does this get set up?


Answers:
author: Jake Bartlett
body: IP Whitelisting is a legacy feature that we need to enable for you on our end. Can you send us an email at hi@statuspage.io with a link to your page? We'll be happy to get this turned on for you.
Atlassian Checkup down?
Asked by Stefan Niedermann:

Oops, an error occured {#toc-hId-1842290206}
============================================

This exception has been logged with id **6ffcpghnh**.

Tried with Chrome, Firefox, Android Browser...


Answers:
author: Joe Clark
body: It should be back online now.

comments: author: Stefan Niedermann
body: it's instable. a request takes several minutes.


author: Joe Clark
body: We're taking a look at it. Thanks for reporting!


author: Timothy
body: It's still down.


Tags: cloud
Not able to login to admin page
Asked by nincy james:

when i am trying this page [](http://localhost:8060/admin)<http://localhost:8060/admin>, Iam getting the error below. Everytime i leave my repository to be scanned i am facing issues with login into admin Page. kindly help urgently.

javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: javax.servlet.jsp.JspException: javax.el.ELException: Problems calling function 'cru:getWebItems'


Answers:
author: AafrinA
body: Hi Nincy,

The error indicate that insufficient memory available to execute the process in the Fisheye, you can override the default allocated memory in fisheye. Refer to the following [documentation](https://confluence.atlassian.com/display/FISHEYE/Environment+variables)on setting the FISH_OPTS to increase the JAVA Heap size.


author: nincy james
body: At the end of page.it Also says

Original error that caused this page {#toc-hId-1680637194}
----------------------------------------------------------

#### java.lang.OutOfMemoryError {#toc-hId--1264546777}


Tags: crowd-administration