Looks like the newly updated "stable" version of RVM has been signed by a new 
release manager, and their public key hasn't been installed on the websites1 
Jenkins VM yet.  I (temporarily) changed the build script to download the key, 
first using the documented mechanism printed in the log, which failed on manual 
job kickoff, and then by downloading the key gpg says is the release is signed 
by; built manually (success!); and then commented out the key download lines.

Steve

> On Dec 12, 2018, at 1:04 PM, Apache Jenkins Server 
> <jenk...@builds.apache.org> wrote:
> 
> Build: https://builds.apache.org/job/Solr-reference-guide-master/12309/
> 
> Log: 
> Started by timer
> [EnvInject] - Loading node environment variables.
> Building remotely on websites1 (git-websites svn-websites) in workspace 
> /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master
>> git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>> git config remote.origin.url git://git.apache.org/lucene-solr.git # 
>> timeout=10
> Cleaning workspace
>> git rev-parse --verify HEAD # timeout=10
> Resetting working tree
>> git reset --hard # timeout=10
>> git clean -fdx # timeout=10
> Fetching upstream changes from git://git.apache.org/lucene-solr.git
>> git --version # timeout=10
>> git fetch --tags --progress git://git.apache.org/lucene-solr.git 
>> +refs/heads/*:refs/remotes/origin/*
>> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
>> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
> Checking out Revision 1e687268316369102306085f8c5410d62b5dafaf 
> (refs/remotes/origin/master)
>> git config core.sparsecheckout # timeout=10
>> git checkout -f 1e687268316369102306085f8c5410d62b5dafaf
> Commit message: "SOLR-12801: Suppress SSL and older codecs"
>> git rev-list --no-walk 1e687268316369102306085f8c5410d62b5dafaf # timeout=10
> No emails were triggered.
> [Solr-reference-guide-master] $ /bin/bash -xe 
> /tmp/jenkins9204071449082796145.sh
> + gpg2 --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
> /tmp/jenkins9204071449082796145.sh: line 2: gpg2: command not found
> + command curl -sSL https://rvm.io/mpapis.asc
> + curl -sSL https://rvm.io/mpapis.asc
> + gpg --import -
> gpg: key D39DC0E3: "Michal Papis (RVM signing) <mpa...@gmail.com>" not changed
> gpg: Total number processed: 1
> gpg:              unchanged: 1
> + bash dev-tools/scripts/jenkins.build.ref.guide.sh
> + set -e
> + RVM_PATH=/home/jenkins/.rvm
> + RUBY_VERSION=ruby-2.3.3
> + GEMSET=solr-refguide-gemset
> + curl -sSL https://get.rvm.io
> + bash -s -- --ignore-dotfiles stable
> Turning on ignore dotfiles mode.
> Downloading https://github.com/rvm/rvm/archive/1.29.5.tar.gz
> Downloading 
> https://github.com/rvm/rvm/releases/download/1.29.5/1.29.5.tar.gz.asc
> gpg: Signature made Wed 12 Dec 2018 11:25:22 AM UTC using RSA key ID 39499BDB
> gpg: Can't check signature: public key not found
> Warning, RVM 1.26.0 introduces signed releases and automated check of 
> signatures when GPG software found. Assuming you trust Michal Papis import 
> the mpapis public key (downloading the signatures).
> 
> GPG signature verification failed for 
> '/home/jenkins/shared/.rvm/archives/rvm-1.29.5.tgz' - 
> 'https://github.com/rvm/rvm/releases/download/1.29.5/1.29.5.tar.gz.asc'! Try 
> to install GPG v2 and then fetch the public key:
> 
>    gpg2 --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
> 
> or if it fails:
> 
>    command curl -sSL https://rvm.io/mpapis.asc | gpg --import -
> 
> the key can be compared with:
> 
>    https://rvm.io/mpapis.asc
>    https://keybase.io/mpapis
> 
> NOTE: GPG version 2.1.17 have a bug which cause failures during fetching keys 
> from remote server. Please downgrade or upgrade to newer version (if 
> available) or use the second method described above.
> 
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> Publishing Javadoc
> Email was triggered for: Failure - Any
> Sending email for trigger: Failure - Any
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to