disabling yarn gpg in Travis to fix hanging

disabling yarn gpg in Travis to fix windows hanging
was submitted in Pull Request #64 (resubmitting in #65)

as per https://travis-ci.community/t/build-doesnt-finish-after-completing-tests/288/9

Oct '18
@AviVahl
Checked it without my before_install. Still got stuck. It appears the yarn installation (and pgp verification) occurs anyway, because my repo contains a yarn.lock.

The repo is setup using yarn workspaces, so I have no proper matching alternative in npm land yet. 😦

EDIT:
tried setting env variable YARN_GPG=no (via [Travis's] configuration) to force no gpg validation, but the container appears to be stuck on: Worker information

I’ve used secure env tokens (via Travis config- “hide from log”), which seems to be broken with Windows containers. Trying regular env var to see if [the behaviour] is different.

EDIT:
Yes! It was the gpg that install.sh of yarn runs. Build now passes, after setting the YARN_GPG=no environment variable.

and as per https://travis-ci.community/t/build-doesnt-finish-after-completing-tests/288/13

Oct '18
josh (@joshk) Josh Kalderimis
Travis CI Staff (Head of Product at @travis-ci)

Hi @chrisdothtml

Could you please try adding YARN_GPG=no to your .travis.yml config to see if this helps?

@BanzaiMan do we currently detect and kill rogue processes when a build finishes?

.travis.yml

@@ -15,6 +15,9 @@ matrix:
     - os: mac
     - os: windows
 
+env:
+  - YARN_GPG=no
+  
 install:
   - npm install 
   - (cd e2e ; npm install)
@@ -26,4 +29,4 @@ script:
   - npm run lint
 
 after_failure:
-  - cat e2e/server-fixture/server.log
+  - cat e2e/server-fixture/server.log