: Unfortunately this is not so easy. It is always the same Jenkins Job, : the randomization is part of the dynamic JAVA_HOME. So the mail is
Ah ... ok. What about adding a second (no mail configured) job for "untrusted" JDK9 (and if we start getting them: new IBM J9) builds? ie: your existing "main" job continues to randomize among the current JVMs and sends mail, but if/when new JVMs are available, you initially add them only to the randomization for the "untrusted" job -- watch it for ~week to see if it has any obvious problems, and then promote it to the "main" job (replacing the early minor version with the same major version) once you know it's not totally broken. -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
