For some reason the checked-out commit is the one just before Cassandra cherry-picked the ref guide squash merge onto branch_6_6, so the solr/solr-ref-guide/ directory isn’t present. I don’t see anything in the job config that would cause this.
Thinking the issue was maybe timing, I manually restarted the job a couple times, but there’s no change. Next I’ll try deleting the job and re-cloning. -- Steve www.lucidworks.com > On May 12, 2017, at 11:42 AM, Apache Jenkins Server > <[email protected]> wrote: > > Build: https://builds.apache.org/job/Solr-reference-guide-6.6/3/ > > Log: > Started by user sarowe > [EnvInject] - Loading node environment variables. > Building remotely on H19 (git-websites) in workspace > /home/jenkins/jenkins-slave/workspace/Solr-reference-guide-6.6 >> 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 > 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/branch_6_6^{commit} # timeout=10 >> git rev-parse refs/remotes/origin/origin/branch_6_6^{commit} # timeout=10 > Checking out Revision 506485c4403bce29cc06272f3341c6afc2f1d479 > (refs/remotes/origin/branch_6_6) >> git config core.sparsecheckout # timeout=10 >> git checkout -f 506485c4403bce29cc06272f3341c6afc2f1d479 >> git rev-list 506485c4403bce29cc06272f3341c6afc2f1d479 # timeout=10 > No emails were triggered. > [Solr-reference-guide-6.6] $ /bin/bash -xe /tmp/hudson7016357499441274446.sh > + echo 'Set ruby path to avoid writing to /usr directory' > Set ruby path to avoid writing to /usr directory > + export RUBY_PATH=/home/jenkins/shared/.rvm > + RUBY_PATH=/home/jenkins/shared/.rvm > + export GEM_HOME=/home/jenkins/shared/.rvm/gems > + GEM_HOME=/home/jenkins/shared/.rvm/gems > + curl -sSL https://get.rvm.io > + bash -s -- --path /home/jenkins/shared/.rvm > Downloading https://github.com/rvm/rvm/archive/master.tar.gz > > Upgrading the RVM installation in /home/jenkins/shared/.rvm/ > RVM PATH line found in /home/jenkins/.mkshrc /home/jenkins/.profile > /home/jenkins/.bashrc /home/jenkins/.zshrc. > RVM sourcing line found in /home/jenkins/.profile > /home/jenkins/.bash_profile /home/jenkins/.zlogin. > Upgrade of RVM in /home/jenkins/shared/.rvm/ is complete. > > # jenkins, > # > # Thank you for using RVM! > # We sincerely hope that RVM helps to make your life easier and more > enjoyable!!! > # > # ~Wayne, Michal & team. > > In case of problems: https://rvm.io/help and https://twitter.com/rvm_io > > Upgrade Notes: > > * It looks like some old stuff is laying around RVM, you can cleanup with: > rvm cleanup all > > * No new notes to display. > > + mkdir -p /home/jenkins/shared/.rvm/gems/gems > + gem install --install-dir /home/jenkins/shared/.rvm/gems jekyll > jekyll-asciidoc pygments.rb > Successfully installed jekyll-3.4.3 > Successfully installed jekyll-asciidoc-2.0.1 > Successfully installed pygments.rb-1.1.2 > 3 gems installed > + export > PATH=/home/jenkins/shared/.rvm/gems/bin:/home/jenkins/tools/java/latest1.8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games > + > PATH=/home/jenkins/shared/.rvm/gems/bin:/home/jenkins/tools/java/latest1.8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games > + cd solr/solr-ref-guide > /tmp/hudson7016357499441274446.sh: line 10: cd: solr/solr-ref-guide: No such > file or directory > Build step 'Execute shell' marked build as failure > Archiving artifacts > 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]
