Looks like this job is running for the first time on a new Jenkins node, and some tools aren’t available. I’ll try to help it along.
-- Steve www.lucidworks.com > On Mar 24, 2018, at 9:05 AM, Apache Jenkins Server > <[email protected]> wrote: > > Build: https://builds.apache.org/job/Solr-reference-guide-master/6250/ > > Log: > Started by timer > [EnvInject] - Loading node environment variables. > Building remotely on websites1 (git-websites) in workspace > /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master > Cloning the remote Git repository > Cloning repository git://git.apache.org/lucene-solr.git >> git init /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-master # >> 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 config remote.origin.url git://git.apache.org/lucene-solr.git # >> timeout=10 >> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # >> timeout=10 >> git config remote.origin.url git://git.apache.org/lucene-solr.git # >> timeout=10 > Cleaning workspace >> git rev-parse --verify HEAD # timeout=10 > No valid HEAD. Skipping the resetting >> git clean -fdx # timeout=10 > Fetching upstream changes from git://git.apache.org/lucene-solr.git >> 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 ea504091e517b5a2941b76adef7270b3d6ecb34c > (refs/remotes/origin/master) >> git config core.sparsecheckout # timeout=10 >> git checkout -f ea504091e517b5a2941b76adef7270b3d6ecb34c > Commit message: "SOLR-10075: Remove test code." >> git rev-list --no-walk ea504091e517b5a2941b76adef7270b3d6ecb34c # timeout=10 > No emails were triggered. > [Solr-reference-guide-master] $ /usr/bin/env bash > /tmp/jenkins8093222934225188453.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.3.tar.gz > Downloading > https://github.com/rvm/rvm/releases/download/1.29.3/1.29.3.tar.gz.asc > gpg: directory `/home/jenkins/.gnupg' created > gpg: new configuration file `/home/jenkins/.gnupg/gpg.conf' created > gpg: WARNING: options in `/home/jenkins/.gnupg/gpg.conf' are not yet active > during this run > gpg: keyring `/home/jenkins/.gnupg/pubring.gpg' created > gpg: Signature made Sun 10 Sep 2017 08:59:21 PM UTC using RSA key ID BF04FF17 > 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/.rvm/archives/rvm-1.29.3.tgz' - > 'https://github.com/rvm/rvm/releases/download/1.29.3/1.29.3.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: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
