nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bitbucket Pipe push back to repo

Michael Russell

I've been able to `git push ...` in Pipeline scripts for awhile now, however, I'm moving over to using the new "Pipe" variant of deployments and I'm finding it impossible to push updates back to the same repo.

Is this only supported in Pipelines and not Pipes

I receive the following error:

`<span>fatal: unable to access '<a href="http://bitbucket.org/username/repo_name/" target="_blank" rel="noopener noreferrer">http://bitbucket.org/username/the_repo_name/</a>': Failed to connect to localhost port 29418: Connection refused`</span>

Accepted answers

Alexander Zhukov_1bqyxb

@Michael Russell @Brett Mathe you can use the git auth proxy feature from withing the pipe. All you have to do is to add the following line somewhere in your script:

git config http.${BITBUCKET_GIT_HTTP_ORIGIN}.proxy http://host.docker.internal:29418/

This will route git traffic from the docker container to the same git auth proxy that is used to authenticate git push commands in pipelines. Make sure you use the BITBUCKET_GIT_HTTP_ORIGIN as your git origin as well.

More info about pushing back to a repo from pipelines: https://confluence.atlassian.com/bitbucket/push-back-to-your-repository-962352710.html

All comments

Michael Russell

My current work around is to do `git remote set-url origin "https://${BB_AUTH_STRING}@Bitbucket.org/${BITBUCKET_REPO_FULL_NAME}.git"` would be amazing for Pipes to work the same way as Pipelines.

Brett Mathe

I'm running into this issue too. Did you have to setup OAuth to get this to work?

Michael Russell

I just do the above in my comment, you can make a BB_AUTH_STRING via instructions here https://confluence.atlassian.com/bitbucket/deploy-build-artifacts-to-bitbucket-downloads-872124574.html

It's basically just a username/app-password mash up.

Alexander Zhukov_1bqyxb

@Michael Russell @Brett Mathe you can use the git auth proxy feature from withing the pipe. All you have to do is to add the following line somewhere in your script:

git config http.${BITBUCKET_GIT_HTTP_ORIGIN}.proxy http://host.docker.internal:29418/

More info about pushing back to a repo from pipelines: https://confluence.atlassian.com/bitbucket/push-back-to-your-repository-962352710.html

Michael Russell

Will that port always be the same? And if so, can we get this in the confluence doc you linked to as methods to push from a "Pipe" specifically; I read through that which lead me to the whole auth string bit but took a moment to get there.

This was a bit of a time sink for myself with no straight documentation on the internal workings of Pipes and git push back. It makes sense when you dig in, it was just bump in time when I was porting things over to Pipes.

Thanks for the feed back @Alexander Zhukov

Alexander Zhukov_1bqyxb

The host and port should be the same. We'll consider adding this to a confluence doc after we discuss this internally.

Michael Russell

OK, thanks @Alexander Zhukov it seems between your method, which appears to be what happens during build setup or using the BB auth string is the way to go.

Hopefully you all can get something on the docs for this

Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

bitbucket-pipelines