On pull request page, show links or messages from related Pipelines builds

Issue #15520 open
Ben Buchanan
created an issue

Context: we have a pipelines build that automatically publishes test cases when you raise a PR. To get that URL we currently have to go find the build number and update the description. Then if we push updates (invalidating the test cases) we have to update the link(s) to point to the next build's output, etc. Also if reviewers don't notice the very-subtle build status, they go to the URL before it's ready (build status being too subtle is a different issue).

What would be awesome: the ability to log information from Pipelines into a panel on the Pull Request screen.

In our case that would mean logging the test URL after the test cases have been deployed. In one hit that would provide the URL, make build status more promient, and auto-update for any subsequent builds.

What would still help: it would help even to just have an option to make Pipelines more prominent in some projects, ideally including the build number. It would also be cool to have an option to delay PR notifications until a successful build has run. (ie. The same panel that's on the project's homepage, but scoped to the PR's branch)

Official response

  • Matt Ryall staff

    Good suggestion, thanks for raising it. I've heard this request from some Atlassian teams internally this week too, who want to link to a test version/storyboard which is created by the build, and an essential part of the QA process.

    No immediate plans to jump on this, but we'll keep it in the list for future consideration.

    One possible workaround for this issue is to create a PR comment using the Bitbucket API inside your build. You also need to look up the relevant PR first, based on the $BITBUCKET_BRANCH. Here are a couple of links with useful information:

    Stringing these together isn't super easy, but should be possible.

Comments (7)

  1. Matt Ryall staff

    Good suggestion, thanks for raising it. I've heard this request from some Atlassian teams internally this week too, who want to link to a test version/storyboard which is created by the build, and an essential part of the QA process.

    No immediate plans to jump on this, but we'll keep it in the list for future consideration.

    One possible workaround for this issue is to create a PR comment using the Bitbucket API inside your build. You also need to look up the relevant PR first, based on the $BITBUCKET_BRANCH. Here are a couple of links with useful information:

    Stringing these together isn't super easy, but should be possible.

  2. Log in to comment