Skip to content
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

Broken mergeable status - Bitbucket pull request conflict-status API v1.0 removed #672

Closed
JoshiiSinfield opened this issue Jun 12, 2019 · 1 comment · Fixed by #673
Closed
Labels
bug Something isn't working provider/bitbucket

Comments

@JoshiiSinfield
Copy link
Contributor

Hi,

It looks as if Bitbucket have now removed the v1.0 pullrequests/#/conflict-status api, meaning that mergeable no longer works when you specify the following in the atlantis.yaml.

apply_requirements:
  - mergeable

It seems that atlantis defaults the mergeable status to false.

Here's the logs:
2019/06/12 07:34:33+0000 [WARN] command_runner.go:193 REDACTED_REPO#460: Unable to get mergeable status: making request "GET https://api.bitbucket.org/1.0/repositories/REDACTED_REPO/pullrequests/460/conflict-status" unexpected status code: 410, body:
{
"type": "error",
"error": {
"message": "Resource removed",
"detail": "This API is no longer supported.\n\nFor information about its removal, please refer to the deprecation notice at: https://developer.atlassian.com/cloud/bitbucket/deprecation-notice-v1-apis/"
}
}
. Continuing with mergeable assumed false
2019/06/12 07:34:33+0000 [INFO] command_runner.go:195 REDACTED_REPO#460: Pull request mergeable status: false

Cheers,
Josh

@lkysow lkysow added the bug Something isn't working label Jun 12, 2019
@lkysow
Copy link
Member

lkysow commented Jun 12, 2019

Fixed in 0.8.2 https://github.com/runatlantis/atlantis/releases/tag/v0.8.2 thanks for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working provider/bitbucket
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants