Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

ethomson
Copy link
Member

At present, we have three online tests against bitbucket: one which
specifies the credentials in the payload, one which specifies the
correct credentials in the URL and a final one that specifies the
incorrect credentials in the URL. Bitbucket has begun responding to the
latter test with a 403, which causes us to fail.

Break these three tests into separate tests so that we can skip the
latter until this is resolved on Bitbucket's end or until we can change
the test to a different provider.

@ethomson
Copy link
Member Author

I don't love resorting to this, but I was hoping that this was just a temporary problem for bitbucket (it seems like it only affects some requests). I opened #4585 to ensure that we didn't forget about this.

g_options.fetch_opts.callbacks.credentials = git_cred_userpass;
g_options.fetch_opts.callbacks.payload = &user_pass;

cl_skip();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please add a comment stating why this test is skipped? It's easy enough to dig it up via git blame, but I think it's good to have anyway

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a comment.

@pks-t
Copy link
Member

pks-t commented Mar 19, 2018

The fix is not ideal, but I guess we cannot do any better without known breakages from #4500, which I definitely don't want to merge for v0.27.0. So I agree with your solution here

At present, we have three online tests against bitbucket: one which
specifies the credentials in the payload, one which specifies the
correct credentials in the URL and a final one that specifies the
incorrect credentials in the URL.  Bitbucket has begun responding to the
latter test with a 403, which causes us to fail.

Break these three tests into separate tests so that we can skip the
latter until this is resolved on Bitbucket's end or until we can change
the test to a different provider.
@ethomson ethomson force-pushed the ethomson/bitbucket branch from 3363613 to 03c5877 Compare March 19, 2018 22:45
@ethomson ethomson merged commit 3198577 into master Mar 19, 2018
@pks-t pks-t mentioned this pull request Jun 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants