Some Java builds are stalling
We have an open source repo for a Java SDK which integrates with my company's REST APIs.
I'm the main author of the SDK, even though my Java skills are very weak. That may be problem, but the 3 AppVeyor builds have been working for a few years now.
https://github.com/AquaticInformatics/aquarius-sdk-java
The 3 YAML files in the root control 3 different builds. 2 of the 3 have stopped working recently, and I can't understand why.
- appveyor.yml - WORKING - Handles pull request builds from the
develop
branch. - appveyor-deploy.yml - STALLS - Deploys the
develop
branch every night to Maven SNAPSHOT repository - appveyor-mvn-release.yml - STALLS - Pushes a
master
branch build to Maven Central Repository
Both builds stall after executing the install
step, but before executing the build_script
step
The builds eventually time out after an hour, with no obvious error message. I'm not sure what has changed or what the problem might be.
The failures started on Jan 18 2020.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Feodor Fitsner on 02 Feb, 2020 04:33 AM
Hi Doug,
Looks like it hangs on
gpg
utility. There was an image update on January 18 which bumped Git version and by defaultgpg
is getting from Git installation.Could you please trying
gpg
from MSYS districution by prepending PATH withC:\msys64\usr\bin
:Let me know if that worked.
2 Posted by doug.schmidt on 02 Feb, 2020 11:26 PM
Hmm, I added the path modification
init:
statement as you suggested, to all 3 YAML configurations. I also added logging ofgpg --version
.That didn't seem to help.
The builds are still stalling after the gpg command
Support Staff 3 Posted by Feodor Fitsner on 03 Feb, 2020 01:36 AM
Could you add
where gpg
before calls togpg
just to make sure it's running from an alternative location? Also, you can login to VM via RDP to see what's going on on/after those commands: https://www.appveyor.com/docs/how-to/rdp-to-build-worker/ I bet there is some child process (gpg-agent
maybe?) preventinggpg
from exiting.Feodor Fitsner closed this discussion on 04 Apr, 2020 09:02 PM.
doug.schmidt re-opened this discussion on 22 Jul, 2020 04:43 PM
4 Posted by doug.schmidt on 22 Jul, 2020 04:43 PM
I just wanted to follow up on this closed discussion (it can be closed again).
I had not gotten around to following your last suggestion of RDP-ing into the worker, but when I finally did, the RDP session made the problem obvious.
The new version of GPG was prompting for a passphrase when importing a secret key. Apparently this was added in GPG 2.1 (the current version in the appveyor builds is GPG 2.2.20). There appear to be some command line options I can use to work around this, so I will try those. Apparently
gpg --batch --import pathToKey
instead ofgpg --import pathToKey
will do the trick, but I need to verify that.But in the worst case for now, I can RDP into the worker and manually enter the passphrase, since this deployment build needs to run only once every 3 months.
Support Staff 5 Posted by Feodor Fitsner on 22 Jul, 2020 11:37 PM
Thanks for sharing your findings!
6 Posted by doug.schmidt on 23 Jul, 2020 12:04 AM
I did confirm that adding the
--batch
to thegpg --batch --import pathToKey
blocked the first stall.There is however, and identical stall, again prompting for the passphrase, but I'm sure there is some XML voodoo that can make that prompt go away too.
doug.schmidt closed this discussion on 03 Sep, 2021 06:33 PM.