Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

All our bitbucket pipelines are failing with HTTP 426 when doing git push

Peter McEvoy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 4, 2024

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

1 answer

0 votes
Peter McEvoy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 8, 2024

Magically, this started working again...

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events