What would you like to happen?
I would like to create a multi-stage Docker build and deployment.
Current
Currently, we have multiple Docker files that all do their own specific bit; they are no longer following modern Docker naming conventions and they require you to first build the Apache Hop project and do some manual steps before they can be executed.
To-be
The goal is to upgrade our Docker build to a multi-stage process that is supported by a CLI.
Current features:
Build from source
The new scripts should be able to build from source using a git repository and a tag, which will allow us to build releases and release candidates.
Build from local hop build
Because building from source takes a while, and developers usually have local changes they want to test, it should also be possible to build using local hop artefacts
Multi arch build
Ability to build both AMD and ARM images
Single build process for all Apache Hop artefacts
I want to be able to build hop, hop-web, dataflow and all future image flavours with a single run, but also have the option to specify a single artefact
have Flavours
Currently, we have 1 extra "flavour" which is hop-web:-beam, but I foresee other suffixes in the future, so there should be a simple system to generate these
Deploy to alternative repositories
Users should be able to re-use these scripts and dockerfiles and adjust them to their personal needs and deploy to their own registry.
This includes updating all documentation, release guides, and our integration test flow to use this image.
Issue Priority
Priority: 2
Issue Component
Component: Containers
What would you like to happen?
I would like to create a multi-stage Docker build and deployment.
Current
Currently, we have multiple Docker files that all do their own specific bit; they are no longer following modern Docker naming conventions and they require you to first build the Apache Hop project and do some manual steps before they can be executed.
To-be
The goal is to upgrade our Docker build to a multi-stage process that is supported by a CLI.
Current features:
Build from source
The new scripts should be able to build from source using a git repository and a tag, which will allow us to build releases and release candidates.
Build from local hop build
Because building from source takes a while, and developers usually have local changes they want to test, it should also be possible to build using local hop artefacts
Multi arch build
Ability to build both AMD and ARM images
Single build process for all Apache Hop artefacts
I want to be able to build hop, hop-web, dataflow and all future image flavours with a single run, but also have the option to specify a single artefact
have Flavours
Currently, we have 1 extra "flavour" which is hop-web:-beam, but I foresee other suffixes in the future, so there should be a simple system to generate these
Deploy to alternative repositories
Users should be able to re-use these scripts and dockerfiles and adjust them to their personal needs and deploy to their own registry.
This includes updating all documentation, release guides, and our integration test flow to use this image.
Issue Priority
Priority: 2
Issue Component
Component: Containers