Thanks Vihang (and others who helped) -Andrew
On Tue, Jun 26, 2018 at 1:16 PM Vihang Karajgaonkar <vih...@cloudera.com.invalid> wrote: > After updating to jdk-8 on the jenkins side and making some change on the > server side, it looks like its chugging along again. Will keep an eye. > > On Tue, Jun 26, 2018 at 11:56 AM, Vihang Karajgaonkar <vih...@cloudera.com > > > wrote: > > > Interesting.. the jenkins job on the client side does use Java 7. Let me > > try updating it to use Java 8. > > > > On Tue, Jun 26, 2018 at 11:52 AM, Sergey Shelukhin < > ser...@hortonworks.com > > > wrote: > > > >> Might be related to > >> https://stackoverflow.com/questions/50946420/could-not-trans > >> fer-artifact-ht > >> tps-repo-maven-apache-org-maven2-received-fat > >> < > https://stackoverflow.com/questions/50946420/could-not-transfer-artifact-https-repo-maven-apache-org-maven2-received-fat > >, > >> similar issue in > >> https://blog.gradle.org/unable-to-download-maven-central-bintray > >> > >> On 18/6/26, 11:51, "Sergey Shelukhin" <ser...@hortonworks.com> wrote: > >> > >> >Was some change made w/versions? > >> > > >> >RROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of > >> >its dependencies could not be resolved: Failed to read artifact > >> >descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.5: > >> Could > >> >not transfer artifact org.apache.maven.plugins:maven > >> -clean-plugin:pom:2.5 > >> >from/to central (https://repo.maven.apache.org/maven2): Received fatal > >> >alert: protocol_version -> [Help 1] > >> >[ERROR] > >> >[ERROR] To see the full stack trace of the errors, re-run Maven with > the > >> >-e switch. > >> >[ERROR] Re-run Maven using the -X switch to enable full debug logging. > >> >[ERROR] > >> >[ERROR] For more information about the errors and possible solutions, > >> >please read the following articles: > >> >[ERROR] [Help 1] > >> >http://cwiki.apache.org/confluence/display/MAVEN/PluginReso > >> lutionException > >> >+ return 1 > >> >+ ret=1 > >> >+ unpack_test_results > >> >+ '[' -z > >> >/home/jenkins/jenkins-slave/workspace/PreCommit-HIVE-Build/hive/build > >> ']' > >> >+ cd > >> >/home/jenkins/jenkins-slave/workspace/PreCommit-HIVE-Build/ > >> hive/build/hive > >> >/testutils/ptest2/target > >> >jenkins-execute-build.sh: line 61: cd: > >> >/home/jenkins/jenkins-slave/workspace/PreCommit-HIVE-Build/ > >> hive/build/hive > >> >/testutils/ptest2/target: No such file or directory > >> >+ [[ -f test-results.tar.gz ]] > >> >+ exit 1 > >> >+ rm -f /tmp/tmp.evhJJyv3A1 > >> >Build step 'Execute shell' marked build as failure > >> >Recording test results > >> >ERROR: Step ‘Publish JUnit test result report’ failed: No test report > >> >files were found. Configuration error? > >> >[description-setter] Description set: HIVE-19481 / branch-3-mr2 > >> >Finished: FAILURE > >> > > >> > > >> > >> > > >
