[OPENJDK-3676] WIP: convert installing some things over to artifacts: #559
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP WIP WIP
Depends upon #562 .
This would resolve https://issues.redhat.com/browse/OPENJDK-2814 and https://issues.redhat.com/browse/OPENJDK-3674
The pattern used in our containers for copying files in, up to now, was to do so entirely inside a script
configure.sh
, with the files to be copied in an adjacent directoryartifacts
, normally with a local directory heirarchy mirroring the destination in the image, e.g.modules/jdk/21/artifacts/opt/jboss/container/openjdk/jdk/jvm-options
. The script usually changed the ownership and/or permissions of the files after copying them.Cekit offers a different method, artifacts, which for some reason we overlooked using for this. Using this is normally shorter, by default sets the owner and group to root, and is more declarative, so makes the images easier to reason about. For the above example artifact, the diff to the configuration to copy it in would be
I've gone a step further in this PR and removed the deep directory heirarchies encoding the destination path, since that's now present in the YAML. Personally I find the deep directory heirarchies hard to work with.
Most of the
configure.sh
scripts have been removed, as all they did was the copying.The copied files are all now owner by root:root, which I prefer, it was always weird to me that the scripts could theoretically be modified by the running web application.
Cekit
artifacts
handling does not change file permissions, so I've set the necessary permissions on the scripts in git itself.