"jenkins test all" includes jdk11 but should not

[pshipton]

"jenkins test all" is not supposed to include jdk11 right now, since it doesn't compile and pass the tests. However it does seem to include jdk11, see #2524 or #2044

[pshipton]

@jdekonin

[DanHeidinga]

Any update on this @jdekonin ?

[jdekonin]

The JDK11 jobs were updated to stop doing this the morning after the ticket was opened. But there were some modifications to triggers suggested and requested that @vsebe, @AdamBrousseau and I have been investigating with this as the reference issue.

I posted in the #committers-public channel last week with some details.

[pshipton]

As per the openj9-dev mailing list, @jdekonin wrote:

"
Please note that triggers for pull request compilation and test are changing, or at least this is the proposal for change.

The primary reason driving this proposal is for more targeted compilation/testing in pull requests which in turn will free more machine resources for other pull request testing and/or daily builds. As new releases and platforms are added, the existing machine resources are often laboring to keep up to the workload.

The current permitted use, is that all is accepted for platforms, test levels and release arguments. The proposal is that all will only be valid for platforms. Only a specific release, e.g. one of JDK8,JDK10,JDK11,JDKN; or one or more comma separated releases, e.g. JDK8,JDK11; would be accepted. Only specific test levels would be valid, e.g. sanity or extended.

A commonly used example, jenkins compile all all for example will need to be entered as jenkins compile all jdk8,jdk10,jdk11. Another commonly used example, jenkins test all all all would become jenkins test sanity,extended all jdk8,jdk10,jdk11

Documentation will be updated via #2539, comment/concerns can be posted to this issue or reply to the email thread.
"

[pshipton]

I assume (and expect) jenkins test sanity all won't do anything, as the jdk levels will need to be specified?

[jdekonin]

Correct.