We want to manually add git tags to some of our builds, and for reasons that are out of scope for this question, we cannot use the built-in VCS Labeling build feature. We want to manually do this as part of a script. The tag is an optional parameter the user can supply after pressing "Run", which is then picked up by the shell script like this in the build configuration's command line script:
export TAG=%system.TagName%
export BUILD_NUMBER=%dep.Company_Project1.build.number%
export SHA=$(git rev-parse --short %dep.Company_Project1.build.vcs.number%)
scripts/release/ci-release-build.sh
Everything in the script works except for the final git push --tags, which results in this error and an exit code of 128:
[11:20:48][Step 1/1] fatal: could not read Password for 'https://company_machine_account@github.com': No such device or address
[11:20:48][Step 1/1] Process exited with code 128
[11:20:48][Step 1/1] Process exited with code 128 (Step: Command Line)
[11:20:48][Step 1/1] Step Command Line failed
The error is due to how Git is configured in TeamCity and how this works with the script. The TC build config uses a VCS Configuration that uses HTTPS authentication (username and password). It seems that no "session" that would cache the password is stored anywhere, so git fails when prompted for a password.
- Is it possible to use a remote configured as using a HTTPS transport when it needs to be invoked from a script?
- Is there another way of configuring this script so that the CI invoked script can do
git push --tags originand successfully push locally created tags to the remote?
I see there are tons of ways of getting around this if you are a normal user with a normal git repo, but I am not sure how to apply this in this situation. I want to avoid stuff like the script dynamically modifying the remote to use a personal access token, for instance. It should re-use some existing, pre-configured access method.
I have also found the article TeamCity to Access Private GitHub Repositories Securely, which mentions Deploy Keys and Oauth, but neither of these seem to be available in my TC 2019 VCS Config settings.
