The ref guide builds have been failing because somebody just installed gpg on the H19 Jenkins node (where the 7.x and master jobs run). As a result, RVM (the Ruby package manager used to download components needed for the build) will try to verify the GPG signature on the downloaded software. Since gpg was never available, it wasn’t possible to import the key required to do this before now. I did that (with gpg2 first, as in the error message below, and then when that failed because gpg2 isn’t installed, with gpg) by temporarily adding the command to the build script in the job’s config and then removing it once it succeeded:
> On Sep 9, 2017, at 5:08 PM, Apache Jenkins Server <[email protected]> > wrote: > > Build: https://builds.apache.org/job/Solr-reference-guide-master/1796/ [...] > gpg2 --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 The 7.0 ref guide build jobs (hosted on Jenkins node H20) haven’t failed, because that node previously had gpg installed; when I set these jobs up I imported the key on H20 via the same mechanism described above. -- Steve www.lucidworks.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
