youngmon/atlassian-qna huggingface dataset:
Pre-Post Build Command Runner plugin curl fail
Asked by Ian Vaughan:

I have installed <https://marketplace.atlassian.com/plugins/com.sysbliss.bamboo.plugins.prepost-build-command>

I added a command "curl ..."

But I get a error in the log output :

```
simple 16-May-2015 22:48:00 [BuildCommandRunner] running command: curl .... 
```

```
error 16-May-2015 22:48:00 Unable to find executable at curl. Will try to run it anyway. 
```

So I added an Executable via /admin/agent/viewBuilders.action

Named "curl", path "curl".

That didn't work, so I tried the linux path "/usr/bin/curl", that didn't work either.

Is the problem with the addon not finding the exec, or the exec?


Answers:
author: Krystian Brazulewicz
body: Use the full path to curl in prepost-build-command plugin.

comments: author: Ian Vaughan
body: Cheers, I actually worked it out by process of elimination, but still a valid post I think in case others run into this problem.


author: Kazi Rizwan
body: [@Krystian Brazulewicz](/t5/user/viewprofilepage/user-id/853277) can you explain in detail where the add the full path ?


author: Victor Debone
body: Hello [@Kazi Rizwan](/t5/user/viewprofilepage/user-id/3899108) ,

The full path is required on the field "Commands" in the plugin:

![CleanShot 2020-09-17 at 10.32.20@2x.png](https://community.atlassian.com/t5/image/serverpage/image-id/110681iFFB6BD4F9F043B0E/image-dimensions/451x211?v=v2 "CleanShot 2020-09-17 at 10.32.20@2x.png")

In the case of curl, you would not insert \`curl\` but the full path \`/usr/bin/curl\`

I hope that helped :)


author: Alexey Chystoprudov
body: Hello Ian,

Please check that curl executable is available at Bamboo server or agent machine via command line.

Create Script task with curl command to identify if issue is at Bamboo or plugin side.
What java version should be used with Bamboo 3.0.1
Asked by Tom Allen:


Answers:
author: Daniel Wester
body: According to <https://confluence.atlassian.com/display/BAMBOO030/Supported+Platforms> Java 1.5, or Java 1.6 (eek!). You might want to upgrade Bamboo if you can...

Java 1.5 was/is no longer support as of Bamboo 3.1.


author: Tom Allen
body: Thanks, Daniel - just what I was looking for. (And yes -- pursuing upgrading Bamboo from 3.0 to 5.8 in the near future).
Clearing Elastic Block Store Volumes
Asked by Jake Wasdin:

I don't recall this happening in the past, but it seems that each time an EC2 instance is being spun up, it is creating a EBS volume that is not being automatically deleted. This is taking up a lot of space, and has started to become an issue now that we can have 5 EC2 instances running at the same time and are often shutting these down and starting them up.

How can I make this volumes clear automatically when the instance is shut down?

Here is a screenshot showing what I am talking about.

image2015-5-11 10:21:56.png  
[](https://community.atlassian.com/t5/Bamboo-questions/Clearing-Elastic-Block-Store-Volumes/qaq-p/404479?attachment-id=3961){#link_117272d5ccdb46}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/12702/1/image2015-5-11%2010%3A21%3A56.png){#display_117272d5ccdb46_0}


Answers:
author: Przemek Bruski
body: Are these custom EBS AMIs? Did you tick off the "delete on termination" checkbox when creating them?

comments: author: Jake Wasdin
body: Ah! That was it. I had not noticed that. Another team member had unchecked that on our latest custom AMI which had been left checked prior. Thanks.


Tags: bamboo-administration
Build error with com.atlassian.bamboo.repository.RepositoryException : java.lang.RuntimeException:
Asked by Elee Yang:

Hi, I'm not sure what I did but I am now getting an error when trying to run any of my builds. Previously it worked until I ran some command line with Git to try to commit files back into BitBucket. Now all plans do not build. They fail with

System Error Details {#toc-hId-1817359080}
==========================================

*[Build OLR - OLR-Dev 47](http://bamboo.ccli.net:8085/browse/OLR-OLM-47) :* Errors getting changes for OLR-OLM-47  
(com.atlassian.bamboo.repository.RepositoryException : java.lang.RuntimeException: com.atlassian.bamboo.plugins.git.GitCommandException: command system.git.executable version failed with code -1. Working directory was \[\\\]., stderr: )  
javaerror.png  
I'm attaching screenshots and text output. Any idea as to why this would be failing? I'm able to setup repositories with the correct credentials.  
I think the only think I did that would have changed git is by setting

    git config --global user.name "Your Name"git config --global user.email "you@example.com"

```
I've since then removed these values but it's still not working.
```

<br />

Thanks in advance,  
eyang


Answers:
author: rsperafico
body: Hello Elee,

Thank you for your question.

Could you please make sure you have set up Git as a capability to the Bamboo agent where you are attempting to run the build OLR-OLM, please:

* "Bamboo administration \>\> Build resources \>\> Server Capabilities"
* "Bamboo administration \>\> Build resources \>\> Agents \>\> \<your agent\> \>\> Capabilities" tab

Please, refer to [Defining a new version control capability](https://confluence.atlassian.com/display/BAMBOO/Defining+a+new+version+control+capability) documentation for further information.

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

---

Kind regards,  
Rafael P. Sperafico  
Atlassian Support

comments: author: Amod Kaveeshwar
body: Hi Rafael,

I have similar issue getting while build running on bamboo.

*[Build BIOS - api0479-network-topology-api-v1 29](https://master2.ci.ae.sda.corp.telstra.com/browse/BIOS-API0479-29) :* Errors getting changes for BIOS-API0479-29   
(com.atlassian.bamboo.repository.RepositoryException : java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote git@git.okapi-np.in.telstra.com.au:BIOS/topology-service-okapi.git failed with code 128. Working directory was \[.\]., stderr: \[ssh: connect to host git.okapi-np.in.telstra.com.au port 22: Connection refused, fatal: Theremote end hung up unexpectedly\])

I have only access to link repositories under Bamboo Administrator. I am not able to see any other option under this.

Need your support to resolve the same.

Amod


author: Elee Yang
body: Thanks for the quick response! Yes you are correct. I entered the path for git.exe and it's now building.
Bamboo triggers not working
Asked by Lynn Walker:

We use Stash integrated with Bamboo (along with many other Atlassian products). I have created a build project that is triggered each time a Stash repository is updated. I have also created an associated deployment project that is triggered by the build project. This was all working fine dozens of times.

Yesterday the triggers stopped working. Checking code into Stash no longer triggered the build, and when I manually ran the build the deployment was no longer triggered. This was not just a problem for me, but for other projects in Bamboo by other developers who had also been using the system successfully for weeks.

The main admin for our Bamboo and Stash installation mentioned that this has occurred in the past. He has tried allocating more memory to Bamboo, has noticed that if he removed a project from Bamboo and then added it again that the issue was sometimes fixed. Generally he suggests that the issue has just fixed itself over time when it occurred in the past.

Obviously there is a specific reason or group of reasons for this issue. The fact that it has often cleared up on its own is a possible clue, but the fact that our CI was not working yesterday, is not working today, and may not be working until it "magically" fixes itself is not a situation we can live with. The fundamental purpose of the CI is defeated when this issue surfaces and we don't understand either the cause or the resolution.

How can you help us resolve this issue?


Answers:
author: Bruno Rosa
body: Lynn, I just noticed that you also posted your question here in *answers.atlassian.com*. Allow me to post my response to the community.

In this particular case, the problem was related to the application link configuration between *Bamboo* and *Stash*.

--

When connecting Bamboo **5.6+** to Stash **3.2+** via *application links*, please make sure that:

* Trusted Apps authentication is **disabled**
* OAuth authentication is **enabled** :
  * Allow 2-Legged OAuth is **enabled**
  * Allow user impersonation through 2-Legged OAuth is **disabled**
* Basic Auth authentication is **disabled**

The settings above can be found inside Bamboo and/or Stash, respectively, through:

* ++Bamboo administration \>\> Add-ons \>\> Application Links++
* ++Stash administration \>\> Settings \>\> Application Links++

In Stash, make sure you have ++Stash administration \>\> Settings \>\> Server Settings \>\> SSH access++ configured as follows:

**\[x\]** SSH enabled

**\[x\]** SSH access keys enabled

SSH Port: 7999

--

Please bear in mind that this is not the only possible cause to this kind of problem, if you're in doubt or if the above didn't help, please contact [support](https://support.atlassian.com/servicedesk/customer/bsp) (as Krystian mentioned).

Cheers,

Bruno Rosa


author: Krystian Brazulewicz
body: Please contact [Support](https://support.atlassian.com/servicedesk/customer/bsp)


Tags: bamboo-administration
Unable to SSH to elastic agent launched by Bamboo
Asked by adamgregory:

Hi,

I am in the process of configuring bamboo to perform nightly builds and tests for my project. In order to install and run my project I require some specialized software packages to be installed. Because of this, I am building a custom AMI based on the Atlassian Ubuntu 14.04 Elastic Bamboo micro instance.

In order to configure the base Ubuntu 14.04 instance with my required software, I launch the instance from the bamboo instances configuration page and attempt to connect using SSH to install my software packages.

When I start the instance from bamboo, I am given a private key (elasticbamboo.pk) to download which I assume corresponds to the keypair elasticbamboo in my AWS management console. I also see that the instance is created in the aws management console instances page and that I can view additional information about the instance there.

I use the command:

ssh i elasticbamboo.pk ec2user@publicDNS  

to connect to the instance and I get a prompt that the authenticity of the host can't be established the key fingerprint is x and asks if I want to continue. I select yes and the host is added to the list of known hosts and the connection is attempted. The connection fails with the message: permission denied (public key).  
I have noted that the fingerprint given in the terminal when connecting does not match the elasticbamboo keypair fingerprint in the aws console.

I have also attempted using puttygen to convert the pk file to a ppk file and using putty to connect via SSH in windows, but this has the same problem.

What steps am I missing to connect to my instance?  
Thanks for your help.


Answers:
author: Krystian Brazulewicz
body: It looks like elasticbamboo.pk key available on your instance doesn't match the keypair created on the server. You might try fixing the issue by removing the keypair on the server. If your Bamboo instance is hosted locally you should also remove the key from the local storage on the Bamboo server.

Then just simply run another EC2 agent and Bamboo will recreate security group and download the private key.

comments: author: adamgregory
body: I tried removing the keypair and security groups from the aws console and having bamboo re-generate them but I am still unable to ssh to any instance launched by bamboo.


Tags: ssh
Can I keep a minimum number of elastic instances always running on Bamboo cloud?
Asked by Jose Pacheco:

Im using Bamboo (Cloud version) - and I would like to keep at least 1 elastic instance always running. Is that possible?


Answers:
author: Cintia Calvo
body: Maybe you should be able to use the instance schedules for that.

Cog -\> Instance schedules.

Screen Shot 2015-05-11 at 1.31.08 pm.png

So, you can configure Bamboo to enforce that at least one instance of a certain type is running on that time. The cron I used above should check every 5 minutes from Monday-Friday.

I don't think it would prevent agents being shut down if it's being idle all the configured time, but it would bring a new one.

[](https://community.atlassian.com/t5/Bamboo-questions/Can-I-keep-a-minimum-number-of-elastic-instances-always-running/qaq-p/118945?attachment-id=5972){#link_1168b71f9d6e50}  
[](/tnckb94959/attachments/tnckb94959/bamboo-questions/3779/1/Screen%20Shot%202015-05-11%20at%201.31.08%20pm.png){#display_1168b71f9d6e50_0}


Tags: cloud
How to manually clean up bamboo artifacts\globalStorage
Asked by Camille Dominique:

Hi,

We are currently using bamboo 5.5.0 and running into disk space issues, mainly due to the artifacts\\globalStorage folder.

As of my understanding, there is a setting to expire files in globalStorage, but only as of bamboo 5.7.0

Until we do update to a newer version, what is the Right Way (TM) to get rid of old deployments under globalStorage?

1. Can it be done in bulk through the Web-GUI (without clicking through every single deployment release?
2. If not, can I simply delete the oldest folders from the filesystem?
3. Will this impact the deployment plans or the database in any way?
4. Do I have to stop the Bamboo service before I delete stuff in globalStorage?

Thanks


Answers:
author: Marcin Gardias
body: My recommendation would be to upgrade and use our supported method of artifact expiry, but since that might be difficult if you are tight on space already, here are the answers to your questions:

1. No, the expiry option we introduced in Bamboo 5.7 is the 'bulk' action you are looking for.
2. Yes with some caveats. You need to be sure none of those artifacts is something you might need later (and can't rebuild). But I guess I'm stating the obvious here.  
   Secondly, the folders in globalStorage are created when build result that originally produced the artifact is *removed*\*. So older file date doesn't translate automatically to older artifact (although there is a correlation)
3. You will not be able to deploy or download those artifacts (thank you Captain Obvious). The artifacts will still be listed in the DB and the UI, but I don't think you need to worry about it.
4. No.

\*) If you are interested, here's why: originally artifacts used to be always stored in appropriate Plan's folder. We wanted to keep that convention, but we needed to make deployments work even if the corresponding build result is removed. We also didn't want to duplicate artifacts without need. So here's how it works: as long as build result exists, deployment looks for artifacts in respective Plan's folder. When it is deleted, we move the artifacts we into "globalStorage" so that they are not lost.


Tags: bamboo-administration
Run tests on a remote windows machine
Asked by GN:

Hi there,

I am building a linux driver using bamboo Ci and I want to kick off tests from a different windows machine(As we already have the test framework built in that way and I am not willing to disrupt the mechanism),

I wanted to include this job as a part of build process so that when the test fails build fails as well.

Is there a way to achieve that, Please note that I don't want it to consume an extra license for the same plan.

Thanks,

GN


Answers:
author: dericleeyy
body: You can achieve this by using a Window remote agent.

As Bamboo dispatching is based on Jobs, you can configure your test tasks on a different job from your build. Example:

Stage 1: Build Job

Stage 2: Test Job

It's also important to have them in different stage as Jobs in the same stage runs in parallel. Capabilities are based on jobs. So it is possible to have your Linux agent running your build job and your Windows remote agent runs your test job after your build job have completed.
CAMBIAR MANAGER
Asked by Felipe Romeo De La Cruz Jim?nez:

Por favro nos pueden ayudar con cambio de Manager: NOMBRE: CRISTIAN OTTONIEL GARCIA PAREDES, EL ES EL NUEVO SUPERVISOR.


Answers:
author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

Please, don't SHOUT - it is hard to read, and a lot of people find it rude.

You will need to talk to your Atlassian admins about this, the Community here has less access to your Jira system than you do, and you are asking about giving someone more rights in your systems.


Tags: cloud

jira-service-management

jira-service-management-cloud
How can I open up my service desk so customers do not have to log in?
Asked by Laura McWilliams:

We have a service desk where customers can open tickets or access the knowledge base. The knowledge base is linked to a Confluence space that allows anonymous access. I understand that customers should have to log in to use the ticketing system. But they should not have to log in just to access the portal.

However, if you go directly to our portal, you can't even see anything until you log in. I have found a number of docs about this but I can't make head or tails of any of it. It's possible that I don't have enough administrator permissions to actually fix this problem. But it would be good to know where to even start.


Answers:
author: Laura McWilliams
body: I FINALLY FIGURED IT OUT!!!!

![2023-12-06_15-29-24.png](https://community.atlassian.com/t5/image/serverpage/image-id/295651iAD9E1496FDD03C6D/image-size/large?v=v2&px=999 "2023-12-06_15-29-24.png")

Then, do this:

![2023-12-06_15-31-10.png](https://community.atlassian.com/t5/image/serverpage/image-id/295652i2170124637FA91E2/image-size/large?v=v2&px=999 "2023-12-06_15-31-10.png")

Now, I can open a private browser tab and access the portal. NO LOGIN PROMPT!! Woo-hoo!


author: Jack Brickey
body: Hi [@Laura McWilliams](/t5/user/viewprofilepage/user-id/4041155) , what info would you need/want customer's to access without logging in? One option is to use the [widget](https://support.atlassian.com/jira-service-management-cloud/docs/embed-a-widget-onto-a-web-page/) and embed into your company's webpage.

comments: author: Laura McWilliams
body: I mainly want them to be able to access the Knowledge base. They currently already have access to all of the information already, but it's on Confluence and it looks pretty crummy. The knowledge base is a much cleaner presentation of the same info.

It would also be nice for them to be able to open tickets without logging in. It's already possible for them to do so via email, so why not let them do it directly on the portal anyways? based on some other posts i have found, it does seem to be possible.

I don't manage the company's web page, but I have already been thinking that we should integrate the support portal and the knowledge base with it, so I will definitely look into the widget, thanks.


Tags: cloud

jira-service-management

jira-service-management-cloud
Automation: Keeping on top of SLA's not triggering
Asked by Emmanuelle Guia:

We have the **SLA espera informacion cliente** (waiting for client information), a rule that creates a comment when the sla is about to breach, and a rule that triggers when is breached that comments and closes the isue.

According with this article [JSM Jira Automation: How to Send SLA Breached Noti... - Atlassian Community](https://community.atlassian.com/t5/Jira-Service-Management-articles/JSM-Jira-Automation-How-to-Send-SLA-Breached-Notifications/ba-p/1894625), my implementation is ok, but I found out that if the notification rule is processed, the other rule does not work in the same issue.

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

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

There are no errors in the logs. And both rules allow another rule to trigger them. Someone else had this problem?


Answers:
author: Kateryna_v_SaaSJet_
body: Hi [@Emmanuelle Guia](/t5/user/viewprofilepage/user-id/5063649)   
I once saw a similar request in the community, but unfortunately, I can't find it now. I didn't have such a problem because we use the **SLA Time and Report for Jira** add-on (which we developed), where in one window, you can configure the conditions for SLA execution and immediately SLA goals with automatic actions. Below is an example of how it looks in the add-on.  

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

You can also configure the automation rules described in the request: comment on the task, status change, and others. The app has a [30-day trial](https://marketplace.atlassian.com/apps/1220741/sla-time-and-report-for-jira?tab=overview&hosting=cloud&utm_source=Atlassian_Community&utm_medium=referral&utm_campaign=Comment_Automation-Keeping-on-top-of-SLAs-not-triggering+&utm_term=20240116), so give it a try.


Tags: cloud

jira-service-management

jira-service-management-cloud
Integrate Instagram/Facebook with Jira Service Management?
Asked by Edgardo Ibarra:

Hey there!

I'm Looking for a tool or plugin to streamline social media support in Jira Service Management?

I'm exploring options to manage Instagram and Facebook comments/DMs directly within JSM, but haven't found the perfect solution yet.

Anyone have experience with such integrations? Recommendations appreciated!


Answers:
author: James Jade
body: To streamline social media support in Jira Service Management (JSM), I recommend using the [Instander app](https://theinstander.com/) for Instagram. It offers advanced features for managing comments and DMs, and can be configured to work with JSM.

For Facebook, \*\*Meta Business Suite\*\* is ideal. It efficiently handles comments and messages and integrates well with JSM through various third-party tools like Zapier or Automate.io for custom workflows.

Hope this helps! Any further questions, feel free to ask.


Tags: cloud

jira-service-management

jira-service-management-cloud
Connect 2 Slack workspaces to Jira Chat feature
Asked by Mara Kaspers:

I have connected a slack workspace with Jira chat to automatically create tickets from Slack by adding an emoji to a message. However, in the chat setting I can't seem to set up a connection to another slack workspace. Is there a way to connect Jira chat to 2 workspaces at the same time?


Answers:
author: Aysun ?zg?n
body: Hey [@Mara Kaspers](/t5/user/viewprofilepage/user-id/5244952)   

I wanted to share that Actioner provides a Slack app for Jira that lets you create issues with emojis. It is also possible to connect multiple Slack instances with the same Jira project.  

If you can't figure out a way to connect multiple Slacks with Jira chat, Actioner's solution might be worth to check out. You can find the [app](https://marketplace.atlassian.com/apps/1230509/jira-for-slack-by-actioner?tab=overview&hosting=cloud) on Atlassian Marketplace.  

Please feel free to ping me anytime if you'd be interested or if you have any questions.  

Aysun from Actioner


Tags: cloud

jira-service-management

jira-service-management-cloud