Since this morning our pipelines are failing with HTTP 426 (Upgrade Required) when doing a git push back to the containing respository:
+ git push
fatal: unable to access 'http://bitbucket.org/dingeng/otu/': The requested URL returned error: 426
Documentation indicates that HTTP push should be "seamless":
"If you want to make changes to your repository from within your pipeline, you can push your changes back. We recommend using an HTTP git origin, which we set for you by default. As it's preconfigured, pushing back using HTTP will work seamlessly."
From https://support.atlassian.com/bitbucket-cloud/docs/push-back-to-your-repository/
We have changed nothing in our pipelines - they have been running successfully hourly for quite some time. Has something happened serverside that has not been notified or updated in the docs?
Pete
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.