Ok, thanks for the clarification. I wasn’t sure if external parties had managed to set up a jib server but it sounds like that’s not so easy in practice.
-Doug > On 29 Apr 2020, at 11:02, Magnus Ihse Bursie <magnus.ihse.bur...@oracle.com> > wrote: > > On 2020-04-29 10:45, Doug Simon wrote: >> If I understand correctly, this disables building jvmci/graal/aot in *any* >> linux-aarch64 jib based build, not just those done at Oracle. Wouldn’t this >> be better done on the jib command line? > While this is technically correct, the jib tool is only used at Oracle, so in > practice, this is the same thing. > > If/when some other party of the community starts using the jib configuration > (instead of creating their own), that will be a relevant feedback. > > /Magnus >> >> -Doug >> >>> On 29 Apr 2020, at 06:12, Mikael Vidstedt <mikael.vidst...@oracle.com> >>> wrote: >>> >>> >>> Please review this small change which disables JVMCI, Graal, and AOT when >>> building linux-aarch64 at Oracle, for now. >>> >>> JBS: https://bugs.openjdk.java.net/browse/JDK-8244061 >>> webrev: >>> http://cr.openjdk.java.net/~mikael/webrevs/8244061/webrev.00/open/webrev/ >>> >>> Cheers, >>> Mikael >>> >
