How to enable and use git push command in the Linux Shell Runner?

[Illya Kuzmych]

I have been using a runner using Docker, and was able to execute my pipeline successfully each time. I have recently switched to Linux Shell as I do not want to reinstall dependencies each time I need to run the pipeline (no company artifactory available to store Docker images) and it is easier to just use the bash shell to do all the same commands.

I was able to set up the Linux Shell fine and it did all of my commands in my scripts successfully and as expected, however it is not able to do a git push, causing the pipeline to fail. I get this error in my pipeline that kills it:

fatal: could not read Username for 'https://bitbucket.org': No such device or address

What can I fix in my pipeline configuration or in my runner to allow for this to work successfully?

[Patrik S · Accepted solution]

Hey @Illya Kuzmych !

Thanks for reaching out to the Community :) 

Based on the error message being returned : 

fatal: could not read Username for 'https://bitbucket.org': No such device or address

Git does not have the credentials configured for the authentication to the repository, causing the push to fail.

When trying to push back to the repository from within the pipeline using self-hosted linux shell runners, you will need to first set the credentials that will be used by git to authenticate with Bitbucket Cloud. This can be done by executing the following command as part of your pipeline before the push: 

git remote set-url origin https://$USERNAME:$APP_PASS@bitbucket.org/WORKSPACE/RESPOSITORY.git

In this example we are considering the creation of environment variables named USERNAME  and APP_PASS, where : 

• USERNAME : Your bitbucket account username. You can check it under your bitbucket profile
• APP_PASS : An app password used to authenticate to bitbucket. If you haven't already, you will need to create an app password with at least repository:write permission for being able to push.

Following is an example pipeline using the command above : 

pipelines:
  default:
      - step:
          name: Test
          runs-on:
           - 'self.hosted'
           - 'linux.shell'
          script:
            - git remote set-url origin https://$USERNAME:$APP_PASS@bitbucket.org/WORKSPACE/REPOSITORY.git 
            - touch fileA.txt
            - git add .
            - git commit -m "[skip ci] testing push from linux shell"
            - git push

The [skip ci] label can be used in the commit message so this commit does not trigger a new pipeline build, which could cause pipelines to get into a loop.

Hope that helps! Let me know in case you have any questions.

Thank you, @Illya Kuzmych !

Patrik S