We have https://github.com/project-hop/hop-docker project for building docker image. Move this project source into https://github.com/apache/incubator-hop project with directory structure separating container (docker), orchestration(kubernetes, gke, docker-compose, etc.,) and deployment (helm, operator etc).
- docker: user should be able to do `docker pull hop` without any challenge
- docker: provide readme with simple pipeline job running in docker
- helm: user should be able to install hop server setup using `helm install --name my-hop hop`
- When PR created with change which affect these artifacts, Jenkins should build the artifact and upload it to respective repository.
Dockerfile should have option to take the maven artifact either from assemblies/client/target or from maven repository. By default it should use maven repository with a switch during docker build command.
In CI (Jenkins), docker build will use the artifact from assemblies/client/target. This will be used for testing the docker image before pushing it to dockerhub
Once image successfully tested, CI will build the docker image which downloads the artifact from maven repository
References and related stories: