Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8024553

Add a system property to keep internal build data to serve properly as build identity.


    • Type: Enhancement
    • Status: Closed
    • Priority: P2
    • Resolution: Won't Fix
    • Affects Version/s: 8
    • Fix Version/s: 10
    • Component/s: infrastructure
    • Labels:


      The aim of this RFE is to simplify house-keeping of build artifacts and prevent engineers errors during JDK testing and development.
      For example, we would like to know:
      - (previous) promoted release/build number (standard version string has this, i.e. 1.8.0-ea-b105)
      - product name (same as above, but we'd like to be able to distinguish noncommercial builds too, product name is the most logical place for that)
      - date of the build (timestamp)
      - 'group' (may be 'project' is a better name) - repository of the build - master/lambda/jsr308/jigsaw/core-libs/master-noncommercial
      - intent' (or 'type' or 'variant') of the build: promotion (default), nightly, adhoc, PIT, etc.

      more things may come up, so we like to have this adjustable for RE/SQE.

      Things like 'release' file won't fit - we need something like a system property requestable at runtime. (consider for instance install tests use-cases)
      This data is shared by all artifacts of the build of all platforms - bundles, zipped/tarred, unpacked binaries.

      For instance, deployment testing may install java on the machine (even to the default location) and then just run /usr/bin/java our.jar to find out the identity above.

      We don't need a special key to get it right from java executable like java -fullversion, and we may keep it strongly encrypted so that no information would slip into outer world.
      We may even afford changing encryption keys monthly.

      All in all the above data doesn't seem dangerous to share.


          Issue Links



              • Assignee:
                nzinovie Nikita Zinoviev (Inactive)
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: