Awesome, Thomas! Thanks for following up on this. On Thu, Jul 12, 2018 at 10:01 AM Thomas D'Silva <[email protected]> wrote:
> I found a similar issue posted here > https://issues.apache.org/jira/browse/INFRA-16349. > I was able to get the Precommit build to post to jira by changing the > jiracli cmd location to /home/jenkins/tools/jiracli/latest/jira.sh > If you submit a patch the Precommit build should post the results to the > JIRA now. > > > On Thu, Mar 8, 2018 at 4:09 PM, Thomas D'Silva <[email protected]> > wrote: > > > I think the exception is because we are using JDK7 according to this > issue > > https://issues.apache.org/jira/browse/HIVE-18461. > > I tried switching the precommit build to use JDK8 but it then fails on a > > different error: > > > > This message is automatically generated.' --issue PHOENIX-4576 > > Unable to log in to server: > https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2 with user: > hadoopqa. > > Cause: (404)404 > > + /home/jenkins/tools/jiracli/latest/jira -s > https://issues.apache.org/jira -a logout -u hadoopqa -p 4hadoopqa > > Unable to log in to server: > https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2 with user: > hadoopqa. > > Cause: (404)404 > > + cleanupAndExit 130 > > > > > > > > On Fri, Mar 2, 2018 at 12:37 PM, Thomas D'Silva <[email protected]> > > wrote: > > > >> The precommit build is running but not posting the results to the jira. > >> It looks like hadoopqa is unable to login. > >> Does anyone know how to fix this? > >> > >> export USER=hudson > >> > >> + USER=hudson > >> > >> + /home/jenkins/tools/jiracli/latest/jira -s > >> https://issues.apache.org/jira -a addcomment -u hadoopqa -p 4hadoopqa > >> --comment '{color:red}-1 overall{color}. Here are the results of > testing > >> the latest attachment > >> > >> http://issues.apache.org/jira/secure/attachment/12912665/PHO > >> ENIX-4633-v2.patch > >> > >> against master branch at commit 1a226ed3e6ac4a56658acbac4da0d5 > >> 18af343ee2. > >> > >> ATTACHMENT ID: 12912665 > >> > >> > >> > >> This message is automatically generated.' --issue PHOENIX-4633 > >> > >> Unable to log in to server: https://issues.apache.org/jira > >> /rpc/soap/jirasoapservice-v2 with user: hadoopqa. > >> > >> Cause: ; nested exception is: > >> > >> javax.net.ssl.SSLException: Received fatal alert: protocol_version > >> > >> + /home/jenkins/tools/jiracli/latest/jira -s > >> https://issues.apache.org/jira -a logout -u hadoopqa -p 4hadoopqa > >> > >> Unable to log in to server: https://issues.apache.org/jira > >> /rpc/soap/jirasoapservice-v2 with user: hadoopqa. > >> > >> Cause: ; nested exception is: > >> > >> javax.net.ssl.SSLException: Received fatal alert: protocol_version > >> > >> + cleanupAndExit 129 > >> > >> + local result=129 > >> > >> + [[ true == \t\r\u\e ]] > >> > >> + '[' -e > /home/jenkins/jenkins-slave/workspace/PreCommit-PHOENIX-Build/patchprocess > >> ']' > >> > >> + mv > /home/jenkins/jenkins-slave/workspace/PreCommit-PHOENIX-Build/patchprocess > >> /home/jenkins/jenkins-slave/workspace/PreCommit-PHOENIX-Build > >> > >> mv: > '/home/jenkins/jenkins-slave/workspace/PreCommit-PHOENIX-Build/patchprocess' > >> and > '/home/jenkins/jenkins-slave/workspace/PreCommit-PHOENIX-Build/patchprocess' > >> are the same file > >> > >> + echo '' > >> > >> > >> On Thu, Jan 18, 2018 at 4:16 PM, James Taylor <[email protected]> > >> wrote: > >> > >>> The pre-commit Jenkins job doesn't appear to be running. Do you think > >>> this > >>> might be related to moving master to HBase 1.4? Another potential > culprit > >>> might be PHOENIX-4538. > >>> > >>> WDYT, Lars? > >>> > >>> Thanks, > >>> James > >>> > >> > >> > > >
