Make bitbucket ignore bamboo build result from particular build plan?

Jay McCure
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 23, 2019

Hi Atlassian community,

 

i have a repo, the repo has two build plans X and Y.

 

X is the normal build plan which tells me that the build for the repo is successful. I want this reflected in bitbucket pull requests.

 

Y is a small task that runs every 15 minutes and is not related to the build status of the repo.

 

My problem is that if a PR for the repo is raised and Y is run and succeeds, it looks as if the PR has been successfully built.

 

How can I ignore the build status from Y ?

1 answer

1 accepted

1 vote
Answer accepted
Steffen Opel _Utoolity_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 24, 2019

I'm not aware of any way to configure Bitbucket to ignore particular Bamboo build results.

That being said, the build status API for both Bitbucket Server and Bitbucket Cloud are based on associating the build status against a particular commit, so in case your auxiliary plan Y does not actually use the resp. source code, you might be able to achieve your goal by removing the Source Code Checkout task within that plan.

Nagomi February 3, 2022

Hi Steffen,

 

In par with above example, What if we still have the requirement of performing any task say (source code check out, build, sonar) in auxillary plan Y and need to ignore  the build results of plan Y ?

 

Can we do that in bamboo

Like Steffen Opel _Utoolity_ likes this
Steffen Opel _Utoolity_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 4, 2022

Hi @Nagomi , welcome to the Atlassian Community!

I haven't tried this and am just brainstorming here, but given "the build status APIs [...] are based on associating the build status against a particular commit", maybe you could forego the source code check out in plan Y and pass the source code from plan X as a Bamboo artifact instead (i.e. you can zip the source code, maybe even git archive works)?

Good luck,
Steffen

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events