The bitbucket-pipe-release pipe ignores SSH_KEY when pushing a tag

Edoardo Pirovano

I'm in the process of trying to release a custom pipe using this automation that you provide, but I'm running into some issues. In particular, I've set the SSH_KEY variable to a base64 encoded key with the right permissions as outlined by the instructions, which is working well for letting the pipe push commits. It is not, however, letting it push new tags. I believe the issue is that the git-tag.sh script in that pipe doesn't actually use the SSH_KEY: only the git-commit.sh one does. I believe copying the logic over to that script (as I've done in this commit on my fork: feel free to use it) would get things working again.

Oday Rafeh_2jhprw

@Edoardo Pirovano 

The issue you're facing is due to the git-tag. sh script not utilizing the SSH_KEY.

To resolve this, you can update the git-tag. sh script by incorporating the logic from the git-commit. sh script.

You can use the commit you've made on your fork as a reference.

The steps:

Clone the bitbucket-pipe-release repository.

Modify the git-tag. sh script to use the SSH key.

Copy the relevant logic from the git-commit. sh script.

Test your changes locally to ensure that the script is working correctly with the SSH key.

Commit your changes and push them to your fork.