On Fri, 13 Jan 2023 15:42:36 GMT, Magnus Ihse Bursie <i...@openjdk.org> 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 chose such > build environment. Furthermore, configure should look for the industry > standard "CI" environment variable to determine if it is running in a CI > environment, and if so, select the ci build env as default. (This is > supported e.g. by GHA). > > Most prominently is the jtreg failure handler, which will halt with a sudo > prompt unless running on a properly configured CI machine on macOS. There is > no reason to run the failure handler at all unless you are running on a CI > machine, so disabling the failure handler by default for developer build > environments will fix this problem. This pull request has now been integrated. Changeset: 75b122fe Author: Magnus Ihse Bursie <i...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/75b122feeae60c38076883b27b173c1cafcacdf5 Stats: 42 lines in 7 files changed: 30 ins; 3 del; 9 mod 8300120: Configure should support different defaults for CI/dev build environments Reviewed-by: erikj ------------- PR: https://git.openjdk.org/jdk/pull/11991
