MDBF-801: Add github status link to full Buildbot results#743
Draft
grooverdan wants to merge 1 commit intoMariaDB:devfrom
Draft
MDBF-801: Add github status link to full Buildbot results#743grooverdan wants to merge 1 commit intoMariaDB:devfrom
grooverdan wants to merge 1 commit intoMariaDB:devfrom
Conversation
grooverdan
force-pushed
the
MDBF-801
branch
4 times, most recently
from
06391af to
8777add
Compare
Collaborator
|
Thanks for the contribution @grooverdan, we would really benefit from such a mechanism. I had an experiment with it at some point, and I think we can do it "cheaper" without putting buildbot to work. We have all the data in GitHub, the only URL data changing between PR's is the PR number of course. |
Member
Author
|
works for me. Sure. |
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With the change to head branch and the extensive focus on status builders only, lets try to make the full results more obvious to the user.
This uses a fixed comment message with the
context="pr_status_url"on just the tarball-docker builder so I'm hoping this limits to one message per PR (even if re-pushed).