-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitbucket Build Status Empty #27
Comments
fix: lets use the version env var instead
@blopker I was wondering if you could create a working example with CURL for creating a status that I could reference? We have both
You can find the code here (note that Bitbucket Server is in the Unfortunately, I do not have the option to Bitbucket Labs for my installation (trying to figure that out too). But in the meantime, if there is a CURL I can use to replicate I should be able to fix. Thanks! |
ah, thanks, I was making the wrong assumptions. Thank you for clarifying, as this should now be much easier to track down :) |
What about drone/24? Build is already written below it so it's redundant. |
I'm trying to think of what other info would be useful there. Maybe the branch name? Something like: |
we will make this customizable in the server. In the meantime, we have this resolved in master and in |
Hello, I found a small issue with the way the Bitbucket build statuses are being posted. The issue, I think, is that the "name" field isn't being supplied to the Bitbucket API. The effect is that although the build is green in the PR UI, there's no link to Drone. This only affects the new (beta) PR UI, which can be enabled in a user's settings (Bitbucket Labs).
Expected behavior is that a link shows up next to the build status in the new PR UI. Example from a Jenkins build:
The observed behavior is that the build status is shown, but there's no link:
The string I see from our Jenkins builds is from the optional "name" field, so I think that's all that needs to be added. As far as I can tell, this is in the
CreateStatus
function in https://github.com/drone/go-scm/blob/master/scm/driver/bitbucket/repo.go. AddingName: input.Label
to thestatus
struct should do the trick, although it might be nicer to have "name" set to the label plus the build number.Cheers!
The text was updated successfully, but these errors were encountered: