RFR: 8274980: Improve adhoc build version strings [v4]
Aleksey Shipilev
shade at openjdk.java.net
Fri Feb 4 10:08:06 UTC 2022
On Fri, 4 Feb 2022 10:00:50 GMT, TheShermanTanker <duke at openjdk.java.net> wrote:
> If that's the case, I'm wondering if instead of changing `18-internal+0-adhoc.shade.jdk (18-internal)` to something like `18-internal-jdk-18+17-80-gcdf89304eaf.shade (18-internal)`, `build 18<+build number, not required>-internal-<branch name + commit id>` would be more understandable and slightly easier on one's eyes, while conveying the same information the usual (verbose) version string otherwise tries to display
We have been discussing this (see the bug comments in JIRA). The showstopper is that versions are captured during `configure`, which means you can configure on one branch, switch to another, and your build would still be recorded as produced by old branch.
-------------
PR: https://git.openjdk.java.net/jdk/pull/6152
More information about the build-dev
mailing list