Build container images via jib-maven-plugin #301
Merged
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.
Summary:
This PR adds
jib-maven-plugin
as build dependency which allows to build and publish onebusaway gtfs tools as docker images.Note: currently, image names are build using their maven
artifactId
as repository names.To build and publish them, an env variable
CONTAINER_REGISTRY_NAMESPACE
needs to be defined.To build use e.g.
CONTAINER_REGISTRY_NAMESPACE=mfdz mvn jib:dockerBuild
, or, to build and publish to the registryCONTAINER_REGISTRY_NAMESPACE=mfdz mvn jib:build
It will build the following images (assuming current version is
4.0.1-SNAPSHOT
):mfdz/onebusaway-gtfs-merge-cli:4.0.1-SNAPSHOT
mfdz/onebusaway-gtfs-hibernate-cli:4.0.1-SNAPSHOT
mfdz/onebusaway-gtfs-transformer-cli:4.0.1-SNAPSHOT
According to
jib-maven-plugin multi-module example
, module-dependencies are built as reproducible builds.