Good catch! Actually beam_PreCommit_Java_MavenInstall <https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_MavenInstall/> and beam_PostCommit_Java_MavenInstall <https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_MavenInstall/> is running on JDK 1.8. I think it's reasonable to skip them and focus on other variants in JDK version test.
On Fri, Jun 9, 2017 at 3:55 PM, Ted Yu <yuzhih...@gmail.com> wrote: > This is nice. > > Nit: I don't see JDK 1.8 (Oracle) variant. Is this intentional ? > > Thanks > > On Fri, Jun 9, 2017 at 3:49 PM, Mark Liu <mark...@google.com.invalid> > wrote: > > > Hi all, > > > > I worked on BEAM-1544 <https://issues.apache.org/jira/browse/BEAM-1544> > > for > > a while, which is to bring Java cross-JDK test to Jenkins, and finished > > this task recently. Now, there is a post commit Jenkins build running on > > three different Java JDK versions (Jenkins link > > <https://builds.apache.org/job/beam_PostCommit_Java_JDK_Versions_Test/ > >)! > > This > > test has already caught several issues, and I hope it continues to > provide > > quick insights into the functionality of Beam across JDK versions. > > > > Here are some details: > > > > - Current JDK versions used in the test: > > - JDK 1.7 > > - OpenJDK 7 > > - OpenJDK 8 > > - Same coverage as beam_PostCommit_Java_MavenInstall. > > - Scheduled to run every 6 hours, concurrently. > > > > Known issues: > > > > - PR-3320 <https://github.com/apache/beam/pull/3320> (just merged): > > Compiling error in Flink runners > > - BEAM-2425 <https://issues.apache.org/jira/browse/BEAM-2425>: > Package > > does not exit when building beam-sdks-java-javadoc in JDK1.7 > > - BEAM-2322 <https://issues.apache.org/jira/browse/BEAM-2322>, > > BEAM-2323 > > <https://issues.apache.org/jira/browse/BEAM-2323>, BEAM-2324 > > <https://issues.apache.org/jira/browse/BEAM-2324>: some Apex tests > > failed if project directory contains space > > > > Mark > > >
