I use a CLI tool called Lerna, and I then have Lerna run another CLI tool called gitpkg. When gitpkg would attempt to push tags to BitBucket, it would error out with the following:
fatal: could not read Username for 'https://bitbucket.org': No such device or address
I tried many solutions listed here and elsewhere with setting up keys, app passwords, etc. but could not work around this issue. So I looked into the build process and noticed that BitBucket Pipelines sets its own git credentials ahead of time:
git config user.name bitbucket-pipelines
git config user.email commits-noreply@bitbucket.org
git config push.default current
git config http.${BITBUCKET_GIT_HTTP_ORIGIN}.proxy http://localhost:29418/
I noticed that git commands issued directly (as in not issued through another CLI tool within) ran perfectly. So I had a suspicion that there might be a permission issue or some walled garden at play when Gitpkg tries to push its tags.
I tested my theory by re-issuing the git config lines, but expanding the config scope globally in hopes Gitpkg would see it
branches:
master:
- step:
script:
- git config --global user.name bitbucket-pipelines
- git config --global user.email commits-noreply@bitbucket.org
- git config --global push.default current
- git config --global http.${BITBUCKET_GIT_HTTP_ORIGIN}.proxy http://localhost:29418/
- nvm install v12
- npm install
- lerna publish --yes
It worked! I know my issue might not be exactly the same as yours but maybe someone out here with the same as issue as me will come across this one day.
--
Edit: The above works so long as your branch isn't protected. In order to have this work with protected branches, you will need to look at "SSH Key pair managed by Bitbucket Pipelines": https://support.atlassian.com/bitbucket-cloud/docs/push-back-to-your-repository#SSH-Key-pair-managed-by-Bitbucket-Pipelines
Then set it like:
git config --global user.name bitbucket-pipelines
git config --global user.email commits-noreply@bitbucket.org
git remote set-url origin ${BITBUCKET_GIT_SSH_ORIGIN}
as in
branches:
master:
- step:
script:
- git config --global user.name bitbucket-pipelines
- git config --global user.email commits-noreply@bitbucket.org
- git remote set-url origin ${BITBUCKET_GIT_SSH_ORIGIN}
- nvm install v12
- npm install
- lerna publish --yes
and it should push without getting the "Permission denied to update branch" error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.