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. ------------- Commit messages: - No need to set jtreg failure handler on GHA either - Let configure decide if failure handler should be enabled or not - Turn off failure handler by default in dev build env - 8300120: Configure should support different defaults for CI/dev build environments Changes: https://git.openjdk.org/jdk/pull/11991/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=11991&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8300120 Stats: 42 lines in 7 files changed: 30 ins; 3 del; 9 mod Patch: https://git.openjdk.org/jdk/pull/11991.diff Fetch: git fetch https://git.openjdk.org/jdk pull/11991/head:pull/11991 PR: https://git.openjdk.org/jdk/pull/11991
