-
Notifications
You must be signed in to change notification settings - Fork 136
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 7.15 RestAPI update #290
Comments
@scaytrase kindly check |
@swaragade currently I have neither bitbucket instance nor active jenkins installations, so It would be hard to implement this feature by myself. But any PR is welcome here |
@swaragade are you sure? The endpoint is still listed without any deprecation notice: https://developer.atlassian.com/server/bitbucket/how-tos/updating-build-status-for-commits/ |
This API is deprecated. However, it wasn't marked properly. https://jira.atlassian.com/browse/BSERV-13381 as such. I got marked properly as deprecated in 8.3: https://developer.atlassian.com/server/bitbucket/rest/v803/api-group-build-status/#api-build-status-latest-commits-commitid-get |
The new API requires the projectKey and repoSlug info. This isn't present in the plugin as it is designed now. So, using the new API would require some changes in the design or usage. That would need way more though and time than I can offer at this point in time. |
…api and fix missing "parent" property in JSON for required builds
…api and fix missing "parent" property in JSON for required builds
Updating to the new API would be more than just nice at this point. The old API is partly broken. Bitbucket will show the build status next to a commit. But even if the source branch tip shows a successful build, it will not allow merging a pull request (if the target branch is configured to require a successful build.) |
What feature do you want to see added?
StashNotifier plugin (v1.25) uses a Bitbucket API here for sending the build notifications.
This API has been deprecated by the Bitbucket.
Please add support for new BitBucket Notification API
Upstream changes
No response
The text was updated successfully, but these errors were encountered: