[
https://issues.apache.org/jira/browse/HBASE-22955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928965#comment-16928965
]
Sean Busbey commented on HBASE-22955:
-------------------------------------
I was hoping I could do this with just changes to Jenkinsfile, by making the
use of jdk7 explicit in the appropriate places. However, that won't work with
our current precommit job for testing patches on jira. because in that case
there's only the 1 bootstrapping run and we don't know what branch we're on
until yetus is already running.
So for *all* of our testing to work, we need to get the Dockerfile to properly
set JAVA_HOME to point at jdk7 on branches-1.
> Branches-1 precommit and nightly yetus jobs are using jdk8 for jdk7 jobs
> ------------------------------------------------------------------------
>
> Key: HBASE-22955
> URL: https://issues.apache.org/jira/browse/HBASE-22955
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.5.0, 1.3.6, 1.4.11
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Major
>
> branch-1 nightly job is failing while trying to do our yetus shaded jar test
> because the enforcer plugin complains about a jdk8 jdk-tools jar being
> present.
>
> looking at the yetus footer, it's because jdk8 is being used instead of jdk7:
> {code:java}
> [2019-08-30T13:30:34.353Z] | maven | version: Apache Maven 3.0.5 |
> [2019-08-30T13:30:34.353Z] | Default Java | 1.8.0_222 |
> {code}
> Same thing in the footer of the jdk7 build (which passes, even though it
> shouldn't)
> {code}
> [2019-08-30T15:43:29.103Z] | maven | version: Apache Maven 3.0.5 |
> [2019-08-30T15:43:29.103Z] | Default Java | 1.8.0_222 |
> {code}
> Both builds appear to be properly running in Docker mode.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
