youngmon/atlassian-qna huggingface dataset:
Elastic Bamboo builds on existing EC2 instances
Asked by Mark Lichtenberg:

Hi,

We currently do all our builds with Hudson on a permanent EC2 instance we own. Can Elastic Bamboo be configured to use this instance rather than creating a separate AMI just for elastic builds?

Thanks,

Mark Lichtenberg


Answers:
author: Michael Knight
body: Hi Mark,

You can configure Bamboo to use an elastic instance with your choice of AMI, however you will need to customise this instance to be able to work with Bamboo. Most people clone the default Bamboo AMI and make their changes on top of that.

The instructions you'll need to follow are on this page:

* <http://confluence.atlassian.com/display/BAMBOO/Creating+a+Custom+Elastic+Image>

comments: author: Mark Lichtenberg
body: I followed those instructions but ran into a few problems:

1) in section 5.4, it says to append the contents of /opt/bamboo-elastic-agent/rc.local to my /etc/rc.d/rc.local file. The rc.local file mentioned does not exist in /opt/bamboo-elastic-agent or anywhere in the 1.7 agent zip file.

2) Assuming the agent start script is 'bamboo-elastic-agent', I ran this but it complained with "Unable to access jarfile /opt/bamboo-elastic-agent/bin/\*installer\*.jar." I assumed it wanted the atlassian-bamboo-installer-3.4.4.jar, so I downloaded this jar from your maven repo and put it in /opt/bamboo-elastic-agent/bin. Again tried the bamboo-elastic-agent script, and got

Failed to load Main-Class manifest attribute from

/opt/bamboo-elastic-agent/bin/atlassian-bamboo-installer-3.4.4.jar

I could be doing something incorrect here, but it appears the documentation could use some updating.


Tags: cloud
How to clean up Bamboo agents regularly
Asked by Martin Burkhardt:

I'm running a set of Bamboo agents using standard Windows PCs. Apart from compilation, these agents are used for extensive UI testing controlled by Bamboo build plans. Since sometimes UI tests put the system into an inconsistant state, I have scheduled build plans which restart each agent PC three times a day.

Since during execution of such a restart build plan, an agent gets shut down and restarted, Bamboo looses track of this build run and logs an error in the "Administration / System Errors" (.../admin/systemErrors.action). I get a lot of such errors each day and it is difficult to keep track of real system errors.

Are there any recommendations on how to set up a clean and defined environment for automated UI tests? Or how to avoid these kind of system errors?

PS: It is not a solution to let the restart Bamboo job finish before the agent PC actually shuts down. If I do so, even the next build gets triggered on the agent and gives just the same sytem error.


Answers:
author: Przemek Bruski
body: The solution would be to first disable the agent by hitting:

<http://bamboo:8085/bamboo/admin/agent/disableAgent.action?agentId=99156140>

You can get the agent id e.g. from bamboo-agent-home/bamboo-agent.cfg.xml

Access that URL, and schedule a restart for \~1 minute later, let the build finish and all should be OK.

Just remember to enable the agent when the machine comes up:

<http://bamboo:8085/bamboo/admin/agent/enableAgent.action?agentId=99156140>
On Multiple Repositories' Revisions
Asked by Akira Tsuchiya:

I created a Plan which has tow Subversion Repositories: AccountWeb and OrderWeb.

The latest revision in AccountWeb is '6'.

The latest revision in OrderWeb is '8'.

The 'Build Result Summary' unexpectedly shows revisions below.

Revisions AccountWeb 8

OrderWeb 8

I think it must be like below.

Revisions AccountWeb 6

OrderWeb 8

I want the explanation on this issue.


Answers:
author: Jan Swaelens
body: This is probably related to \[<https://jira.atlassian.com/browse/BAM-10607>\]. There are some issues with getting the correct revision number when using multiple (in my case shared) repositories. A fix will probably be included in the 4.0 release.

I am not aware of a workaround.

comments: author: Jan Swaelens
body: Good news, I decided to create a plug-in to allow proper use of repository related properties when using multiple repositories on one plan. It allows you to specify a prefix per repository which is then applied on each property which allows you to access each property for a particluar repository independently.

It is enetered in Codegeist, please vote :-)

<https://marketplace.atlassian.com/manage/plugins/be.sofico.bamboo-repopropertymate-plugin>
Bamboo and Bitbucket
Asked by Simon Comley:

I've read a few questions on this forum mentioning that bitbucket isn't supported by Bamboo OnDemand, they are all a little outdated and most reference this year end of feb as the time when they are rolloing out support.

I've looked in the config and the SVN repo looks hardcoded and I certainly haven't found an easy way to configure it.

Does it support it? If not when is it likely to support it.

Thanks

Simon


Answers:
author: Azwandi Mohd Aris
body: As per the [restricted functions](http://confluence.atlassian.com/display/AOD/Restricted+Functions+in+Atlassian+OnDemand) page, Bamboo OnDemand can only use the internal Subversion repository. You might want to keep an eye on <https://studio.atlassian.com/browse/JST-4488>, however.


author: lingbo
body: Bamboo OnDemand has added the support for Bitbucket starting from July 2012. See: <https://confluence.atlassian.com/display/AOD/July+2012#July2012-Bambooupgrade>


Tags: cloud
Cannot Install Atlassian Connector for Eclipse 3.0.3 on Zend Studio 9
Asked by Panagiotis Kosmidis:

Hello, I try to install Atlassian Connector for Eclipse 3.0.3 on Zend Studio 9 from this repository: <http://update.atlassian.com/atlassian-eclipse-plugin/weekly/e3.6>

but when I try to install it I'm getting this error message:

Cannot complete the install because one or more required items could not be found.

Software being installed: Atlassian Connector for Eclipse (Required) 3.0.3.I20120304-0900 (com.atlassian.connector.eclipse.feature.group 3.0.3.I20120304-0900)

Missing requirement: Atlassian Connector for Eclipse Bamboo UI 3.0.3.I20120304-0900 (com.atlassian.connector.eclipse.bamboo.ui 3.0.3.I20120304-0900) requires 'bundle org.eclipse.mylyn.commons.notifications.ui 0.0.0' but it could not be found

Cannot satisfy dependency:

From: Atlassian Bamboo Integration 3.0.3.I20120304-0900 (com.atlassian.connector.eclipse.bamboo.feature.group 3.0.3.I20120304-0900)

To: com.atlassian.connector.eclipse.bamboo.ui 3.0.3.I20120304-0900

Cannot satisfy dependency:

From: Atlassian Connector for Eclipse (Required) 3.0.3.I20120304-0900 (com.atlassian.connector.eclipse.feature.group 3.0.3.I20120304-0900)

To: com.atlassian.connector.eclipse.bamboo.feature.group 3.0.3.I20120304-0900

I tried to find Atlassian Connector for Eclipse bamboo UI 3.0.3 but seems that is not there :/

Check a screenshot here: <http://o7.no/wLgFTv> and the issue here: <http://o7.no/zem3Sx>


Answers:
author: jjaroczynski
body: Hi,

What I can see is that Atlassian Connector for Eclipse Bamboo UI 3.0.3.I20120304-0900 cannot be installed because it depends on org.eclipse.mylyn.commons.notifications.ui which cannot be found.

The most probable reason is that Atlassian Connector for Eclipse 3.0.3 is not a stable version. It is a weekly snapshot which requires also the snapshot of Mylyn 3.7 (not released yet).   
The release of Mylyn 3.7 is planned for the end of March and right after that Atlassian Connector for Eclipse 3.0.3 stable will be released.

Please try to install Atlassian Connector for Eclipse **3.0.2** which is the official and stable version. Here is the update site link: <http://update.atlassian.com/atlassian-eclipse-plugin/e3.6>

Cheers,  
Jacek
Can Bamboo ignore certain conditions when triggering builds?
Asked by Dan McKean:

I've got a few infrequently updating projects in Bamboo. These are libraries, and I'd like them to build with the rest of our nightly builds, so they're included with the rest of our bits when push to pre-production enviroment overnight and run integration tests.

In Bamboo, I'd like those libraries to be built on these conditions:

"At 1:00am each morning, if there's been a checkin to the single Mercurial repository for the project."

That's fine, and it works--but it always builds, even if no code's been committed.

Why? These builds are done with the Maven release plugin to update version numbers, and the Maven release plugin always checks updated POM files back into Mercurial. This means that every day there's check-ins.

Thus Bamboo runs that job, because it sees these semi-bogus checkins from the Maven release plugin, and thus there's something new to build.

Is there a way I can tell Bamboo to either ignore a certain user's checkins (a 'builder' account does our builds) or ignore changes to certain files when determining if a build should be done?

I've considered adding a simple 'hg pull -u' at the end of my Bamboo job, but that feels a bit hacky, and was wondering if anyone else has suggestions.

Thanks.


Answers:
author: Dan McKean
body: Thanks Piotr... I'll be looking forward to it.


author: PiotrA
body: There is "include/exclude files pattern" in the repository configuration advanced options - I don't expect it will fit to your need, but thought I'd point it out anyway.

AFAIK in Bamboo 4.0 there will be a feature to ignore commits per message name (or user name, I'm not sure) - and it should do what you expect - at least we, Bamboo developers, had similar issue with Mercurial-based builds being triggered by Maven release plugin and currently the issue is not occuring.

comments: author: PiotrA
body: Just as a reference: <https://jira.atlassian.com/browse/BAM-10693> \<-- this is the feature I was talking about. So it will be/is filtering per commit message, not per user.
Bamboo - Variable Executable Path
Asked by Chris G:

I have several windows batch files that I use to perform various CI tasks (run parameterized MSBuild, etc.). Those batch files sit in the root of my repo. Is it possible to run these batch files from the repo pull that Bamboo does in my Bamboo plan? Or do I need to put them in a location outside of the plan folders and reference them as static fixed locations?


Answers:
author: Przemek Bruski
body: You can run them from the repo pull. Just use them in a ScripTask.

comments: author: Chris G
body: Can you provide a little more detail as to how a ScriptTask would remedy this problem?


author: Chris G
body: Can you provide more detail on how exactly to accomplish this? Adding the script task as \\Source\\File.bat doesn't work.
Is there a way for Bamboo to expose information about the specifics of a failed test using the REST API?
Asked by David Corley:

We're running Bamboo 3.4.4, and we can't find a way to get the class/method name information from a failing test via the REST API.

We're using:

<http://bamboo.123.com/rest/api/latest/result/PROJ-PLAN-JOB-NUM?expand=testResults.failed.testResult.errors>

, but the most information we get back from this is:

```
<testResults fixed="0" existingFailed="0" newFailed="46" failed="46" successful="149" all="195" expand="allTests,successfulTests,failedTests,newFailedTests,existingFailedTests,fixedTests"><allTests size="195" max-result="195" start-index="0"/><successfulTests size="149" max-result="149" start-index="0"/><failedTests size="46" max-result="46" start-index="0"/><newFailedTests size="46" max-result="46" start-index="0"/><existingFailedTests size="0" max-result="0" start-index="0"/><fixedTests size="0" max-result="0" start-index="0"/></testResults>
```

Are we doing something wrong, or is this the most information that can be exposed from the REST API around test information?


Answers:
author: bmccoy
body: I realise this is an old post. But just in case someone else is having the same problem...

\* The expand parameters look incorrect. It should be "testResults.failedTests".

\* Also, you can only get test results at the JOB level. Not at the plan level. (The above example is correct, but often a common mistake)

Cheers,  
Brydie
Configure Bamboo with Git repository
Asked by Balrajb:

Hi,

We have Jira 5 ondemand which comes with Bamboo.

Now how can we configure Bamboo with Git repository, there is no information on <http://confluence.atlassian.com/display/AOD/Getting+started+with+Bamboo+OnDemand>

Please help


Answers:
author: Michael Knight
body: The feature request for this is [here](https://studio.atlassian.com/browse/JST-4488) and is definitely something that will happen, although I don't have a firm ETA for it yet.


author: Matt Young
body: I want to second this request for an answer. SVN is on it's way out kids. ;)


Tags: cloud
I can not login from Visual studio to Bitbucket
Asked by BES1:

I try to login from Visual studio to Bitbucket I can not login. Coming error : Operation is forbidden

\<image removed for security reasons\>


Answers:
author: Caroline R
body: Hi, [@BES1](/t5/user/viewprofilepage/user-id/4566882)! Welcome to the community!

I noticed that your Bitbucket account was created some days ago. In this case, could you confirm if you are using your regular password or an App password to log in to Visual Studio?

The reason I'm asking this is that we [announced in June](https://bitbucket.org/blog/deprecating-atlassian-account-password-for-git-and-bitbucket-api-activity) that we are phasing out the use of user login passwords for REST APIs and git over HTTPS.

We [recently announced](https://bitbucket.org/blog/deprecating-atlassian-account-password-for-bitbucket-api-and-git-activity) the first phase of this, where any user with an Atlassian account created on or after UTC 00:00 on **13 September 2021** must use a Bitbucket Cloud generated [App Password](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/) for all git operations over HTTPS and for REST API authentication. In this case, could you please try to access Visual Studio using an App password?

If you have any problems using or configuring an app password, please do let me know and I will be happy to assist.

Kind regards,  
Caroline


Tags: bitbucket-cloud

cloud
Filter conflicted pull requests in list
Asked by Serhii Sobchuk:

Hello! Is there any way to filter or mark conflicted pull requests in pull requests list?


Answers:
author: Theodora Boudale
body: Hi [@Serhii Sobchuk](/t5/user/viewprofilepage/user-id/4566827) and welcome to the community!

I'm afraid that this is not possible at the moment. We have a feature request about this in our issue tracker:

* <https://jira.atlassian.com/browse/BCLOUD-6645>

and another one for the ability to add labels to PRs, which would allow marking PRs as having conflicts:

* <https://jira.atlassian.com/browse/BCLOUD-11976>

Our team has been working on improving the PR experience and the latter request is under evaluation, as you can see here:

* <https://confluence.atlassian.com/bitbucket/try-the-new-pull-request-experience-in-bitbucket-958455255.html#ThenewpullrequestexperienceinBitbucket-RecentReleasesandUpcomingFeatureInvestments>

You can add yourself as a watcher in either or both of the feature requests (by selecting the **Start watching this issue** link) if you'd like to receive an email on updates, and also add your vote there.

Implementation of new features is done as per our policy [here](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html) and any updates will be posted in the feature request.

Please feel free to let me know if you have any questions.

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud
I cannot log in into bitbucket
Asked by Santiago Lopez:

Yesterday I was working on bitbucket and suddenly it log out

I tried to log in again but I cant

I am able to access to the main altassian page with my acconut and home bitbucket page also loads.

I cant log in and i don't know why.

When I try in mozilla it says: Unknown error happened

When I am in chrome it simply doesnt works

help :c


Answers:
author: Theodora Boudale
body: Hi Santiago,

You mentioned that the home Bitbucket page loads.

Are you able to access the following workspace, and the public repo in that workspace, while being logged out?

* <https://bitbucket.org/teamfortesting/>

I'd like to understand if you're able to view other public Bitbucket content and the error occurs only with login, or if there are issues with other pages as well.

- Are you able to log in to Bitbucket from a Private window of Firefox or an Incognito window of Chrome?  
- Could you also please attach a screenshot of the page you see when you try to log in?

Kind regards,  
Theodora


Tags: bitbucket-cloud

cloud

login
How can I add custom or standard variables in the following pipe: jira-create-issue:0.2.0
Asked by Rohan Bhardwaj:

I integrated jira-create-issue:0.2.0 in my pipeline. Defined IssueType is getting created successfully in my project.

My query is, how can I add more variables in the following snippet? I want to use as many fields as possible while creation.

```
script:  - pipe: atlassian/jira-create-issue:0.2.0    variables:      JIRA_BASE_URL: "<string>"      JIRA_USER_EMAIL: "<string>"      JIRA_API_TOKEN: "<string>"      JIRA_PROJECT: "<string>"      JIRA_ISSUE_SUMMARY: "<string>"
```

I tried to add one Standard variable "assignee":"\<accountID\>", but after the issue is created, the Assignee field remains blank. (There is not error returned though after script)


Answers:
author: Igor Stoyanov
body: Hi [@Rohan Bhardwaj](/t5/user/viewprofilepage/user-id/3514773) . Thanks for your question.  

As far as i understand according to [jira-rest-api-examples](https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/#creating-an-issue-examples) and [jira-api-python](https://jira.readthedocs.io/en/master/api.html) you can add assignee only on update request, not on create.  

Custom fields are supported by the api but not on the pipe.   

We will think about implementing custom fields logic and example, assignee logic and example. We will notify you when these features becomes available.  

Regards, Igor.

comments: author: Rohan Bhardwaj
body: Thank you very much [@Igor Stoyanov](/t5/user/viewprofilepage/user-id/4550492) I am eagerly waiting for the implementation


author: Igor Stoyanov
body: Hi [@Rohan Bhardwaj](/t5/user/viewprofilepage/user-id/3514773) . We released a [new version of the pipe](https://bitbucket.org/atlassian/jira-create-issue/src/0.6.0/) with support of JIRA_ASSIGNEE and JIRA_CUSTOM_FIELDS.  

Create an issue with assignee:  

```
script:  - pipe: atlassian/jira-create-issue:0.6.0    variables:      JIRA_BASE_URL: $JIRA_BASE_URL      JIRA_USER_EMAIL: $JIRA_USER_EMAIL      JIRA_API_TOKEN: $JIRA_API_TOKEN      JIRA_PROJECT: "PROJ"      JIRA_ISSUE_SUMMARY: "This is a sample issue summary"      JIRA_ASSIGNEE: "<accountId>"
```

Create an issue with custom fields (look at the `Prerequisites` to get info about how to add/retrieve custom fields):  

```
script:  - pipe: atlassian/jira-create-issue:0.6.0    variables:      JIRA_BASE_URL: $JIRA_BASE_URL      JIRA_USER_EMAIL: $JIRA_USER_EMAIL      JIRA_API_TOKEN: $JIRA_API_TOKEN      JIRA_PROJECT: "PROJ"      JIRA_ISSUE_SUMMARY: "This is a sample issue summary"      JIRA_CUSTOM_FIELDS: >        {            "customfield_10034": "Free text goes here.  Type away!",            "customfield_10035": 42.07        }
```

Regards, Igor


Tags: bitbucket-pipelines

jira
bash: docker: command not found
Asked by Folke Byfors:

According to the documentation -\>   

<https://support.atlassian.com/bitbucket-cloud/docs/run-docker-commands-in-bitbucket-pipelines/>  

it says that there is two ways to use docker in your pipeline. I have tested both of them,

both having set

```
options:
  docker: true
```

as well as

```
services:
  - postgres
  - elasticsearch
  - redis
  - jobqueue
  - docker
```

but still when using

```
script:
  - docker version
```

I still get the message "bash: docker: command not found".   

According to the documentation this should work out of the box, or what am I missing?  

I am using a self hosted runner. Could this be a culprit to my issues?   


Answers:
author: Caroline R
body: Hi, [@Folke Byfors](/t5/user/viewprofilepage/user-id/4566312)! Welcome to the community!

Based on the details you shared with us, it seems that the PATH variable is the issue. Could you please check if you have set up the PATH variable as Workspace/Repository or deployment variable?

As you can see in [this documentation](https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/), if we configure a pipeline variable with the name PATH, we might break all the pipeline steps. This happens because the shell uses PATH to find commands, so if we replace its usual list of locations, then commands like docker won't work anymore.

A simple solution is to rename the variable 'PATH' to something else, for example, 'PIPELINE_PATH'.

Please try this and let me know how it goes.

Kind regards,  
Caroline

comments: author: Folke Byfors
body: Unfortunately the path was not the issue. I have since then moved in a different direction.   

Regards  
Folke


author: Caroline R
body: Hi, [@Folke Byfors](/t5/user/viewprofilepage/user-id/4566312).

In case it hasn't been resolved, I see you have access to a Premium workspace, so if the repository in question is under this workspace, you can open a ticket with us through the following link:

* <https://support.atlassian.com/contact/#/>

In "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as the product. In "What is your workspace URL?", make sure to give the URL of the premium workspace.

The support ticket will be visible only to you and Atlassian staff, and with an open support ticket, the engineer handling your case will be able to access the repository and investigate this issue.

If you have any other questions regarding this matter, please let us know.

Kind regards,  
Caroline


Tags: bitbucket-cloud

bitbucket-pipelines

bitbucket-runners

cloud
Problem cloning repository in opensuse
Asked by Luan Medeiros:

Hello,

I'm trying to clone a repository with HHTPS on OpenSUSE 15.3 of a new user (user account created today).

But always getting the message

git clone <https://lucasacastro@bitbucket.org/hgcompro/scripts.git>

remote: You'll need to authenticate with a valid app password. You can create an app password from your account at <https://bitbucket.org/account/admin/app-passwords>  
fatal: unable to access '[https://bitbucket.org/hgcompro/scripts.git/](https://bitbucket.org/hgcompro/virtualcockpit.git/)': The requested URL returned error: 403

Even doing what the return of the clone command asks the error persists.

Somebody could help?

Thanks!


Answers:
author: Luan Medeiros
body: I was able to identify and fix my problem after see these topics:

<https://community.atlassian.com/t5/Bitbucket-questions/Problem-with-cloning-repository-in-ubuntu/qaq-p/1807569>

<https://bitbucket.org/blog/deprecating-atlassian-account-password-for-bitbucket-api-and-git-activity>


Tags: bitbucket-cloud

cloud