Re: RFR: 8300120: Configure should support different defaults for CI/dev build environments

2023-01-17 Thread Erik Joelsson
On Fri, 13 Jan 2023 15:42:36 GMT, Magnus Ihse Bursie wrote: > There are several configure settings that should have different default > values depending on if configure is run as part of a CI build, or a local > developer. > > We should have a `--with-build-env=ci/dev` argument that lets you c

Re: RFR: 8300120: Configure should support different defaults for CI/dev build environments

2023-01-17 Thread Magnus Ihse Bursie
On Tue, 17 Jan 2023 04:13:22 GMT, David Holmes wrote: >> There are several configure settings that should have different default >> values depending on if configure is run as part of a CI build, or a local >> developer. >> >> We should have a `--with-build-env=ci/dev` argument that lets you ch

Re: RFR: 8300120: Configure should support different defaults for CI/dev build environments

2023-01-16 Thread David Holmes
On Fri, 13 Jan 2023 15:42:36 GMT, Magnus Ihse Bursie wrote: > There are several configure settings that should have different default > values depending on if configure is run as part of a CI build, or a local > developer. This change only seems to deal with the jtreg failure handler, are ther

RFR: 8300120: Configure should support different defaults for CI/dev build environments

2023-01-13 Thread Magnus Ihse Bursie
There are several configure settings that should have different default values depending on if configure is run as part of a CI build, or a local developer. We should have a `--with-build-env=ci/dev` argument that lets you chose such build environment. Furthermore, configure should look for the