During the install.sh script, GPG is used to verify the integrity of the downloaded release, which is great.
There are some reports of stalled builds in Travis CI when yarn is installed during build process - particularly on the windows platform, but potentially also with linux platforms.
In many environments, spinning up a gpg-agent process is harmless and won't cause any problems after installation completes, but for Travis the fact that processes are still running is probably causing the build to 'wait' until all steps are complete (which in fact, they are - the gpg-agent process is just a side effect).
It looks like gpgconf --kill gpg-agent is one possible way to clean up the daemon once it's no longer required. Perhaps this can be added after the verify command runs, so that the process is removed once no longer required.
During the
install.shscript, GPG is used to verify the integrity of the downloaded release, which is great.There are some reports of stalled builds in Travis CI when
yarnis installed during build process - particularly on the windows platform, but potentially also with linux platforms.In many environments, spinning up a
gpg-agentprocess is harmless and won't cause any problems after installation completes, but for Travis the fact that processes are still running is probably causing the build to 'wait' until all steps are complete (which in fact, they are - thegpg-agentprocess is just a side effect).It looks like
gpgconf --kill gpg-agentis one possible way to clean up the daemon once it's no longer required. Perhaps this can be added after the verify command runs, so that the process is removed once no longer required.