How does a Stash Pull Request identify relevant builds?

[Dan Rumney]

I have a Stash repository set up to require a successful build before it allows a merge.

Currently, I have a Pull Request that doesn't seem to know that there are Bamboo builds out there for the code in questions.

How does Stash determine which builds are relevant?

[cofarrell · Accepted solution]

Hi Dan,

When Bamboo completes a build it forwards any configured/connected Stash instances information about the build along with the latest commit. This information is then attached to the commits, and when viewing the pull request the latest commit determines what the build status is. That may include statuses from multilple builds, although only the most recent status is relevant for each one.

Are you seeing the build icons in your normal commit list?

https://confluence.atlassian.com/display/STASH/Bamboo+integration

Make sure you have configured Stash in your Bamboo builds:

https://confluence.atlassian.com/display/BAMBOO/Integrating+Bamboo+with+Stash

Let me know if that doesn't work. If you get stuck I would recommend creating a support ticket with your Stash and Bamboo logs, but hopefully the problem is just missing configuration.

Cheers,

Charles

[cofarrell]

We are hoping to improve the current Stash/Bamboo integration, and you may be interested in the following:

https://jira.atlassian.com/browse/BAM-11409

[Dan Rumney]

I reread your answer - looking at Stash again, I noticed that build icons are not appearing the the commit list of my repo. I'll investigate further and report back.

[Dan Rumney]

Thanks Charles,

We've had links between our apps working for a long time now, so I don't think it's that. Also, we've had build statuses appearing on pull requests for our other repos for months.

I'll open up a support ticket and see where we get to.