infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andor Molnar (JIRA)" <>
Subject [jira] [Commented] (INFRA-16349) Jenkins build fails on multiple PR
Date Mon, 16 Apr 2018 10:40:00 GMT


Andor Molnar commented on INFRA-16349:

Looks like HIVE had exactly the issue a while ago:

They fixed it by setting TLS protocol versions explicitly in their precommit script until
the job is upgrade to Java 8.

> Jenkins build fails on multiple PR
> ----------------------------------
>                 Key: INFRA-16349
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Norbert Kalmar
>            Assignee: Chris Lambertus
>            Priority: Critical
> I had a failed build on my PR:
> Re-running the build it failed again with the same reason:
> The exception was:
> Unable to log in to server:
with user: hadoopqa.
>      [exec]  Cause: ; nested exception is: 
>      [exec] Received fatal alert: protocol_version
>      [exec] mv: '/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
and '/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
are the same file
> ZooKeeper calls jira via JIRACLI which is passed to the script in parameter.
> $JIRACLI -s -a addcomment -u hadoopqa -p $JIRA_PASSWD
--comment "$comment" --issue $defect
> I also found another build that failed due to the same reason:
> Can you please check on the Jenkins?
> Thanks!

This message was sent by Atlassian JIRA

View raw message