build-and-deploy: arm64 fixes for GPG signing
#8
Conversation
We were running into errors like: gpg-agent[768]: socket name '/d/actions-runner/_work/git-for-windows-automation/git-for-windows- automation/home/.gnupg/S.gpg-agent.extra' is too long By setting the runner path to /a instead of /actions-runner, we resolve this (and potential future) long path issues, just like GitHub does themselves for their hosted runners. Signed-off-by: Dennis Ameling <[email protected]>
|
Here's a successful CI run of building |
And here is a successful run that built and deployed Now https://wingit.blob.core.windows.net/aarch64/git-for-windows.db is ready to rumble. Thank you so much @dennisameling! |
Even more importantly, https://wingit.blob.core.windows.net/aarch64/git-for-windows-aarch64.db is ready to rumble. That means that we can finally add that |
|
Yay! That's great news! Thank you! 🎉 |
As reported here, the
Get GPG key(s)step wasn't working on arm64.After way too many (failed) attempts to fix things, I debugged by trying
gpg-agent --daemondirectly in the pipeline and found the following:Doh 🤦🏼♂️ I changed the path of the runner from
D:\actions-runnertoD:\ato get below the 100-character limit. Note that GH does this too on their hosted runners, that's why it didn't fail on the x86_64 job. See e.g. this x86_64 run.