Context
Currently, our Docker images are maintained separately from our main source code. They are located at https://github.com/nebari-dev/nebari-docker-images/. This setup often leads to issues when releasing or merging changes to that separate repository. This is because it can result in errors if the Docker images are not fully tested in sync with the main source code. For example, updates made to the docker images won't necessarily be tested with the current head of the main branch.
We need to move the docker images into a docker folder within this repo and update the ci/cd so that images are built and tested as part of our regular test suite.
Value and/or benefit
- better testability and issue tracking
- Validate changes to docker images are not breaking
- Simplify release process
Anything else?
No response
Context
Currently, our Docker images are maintained separately from our main source code. They are located at https://github.com/nebari-dev/nebari-docker-images/. This setup often leads to issues when releasing or merging changes to that separate repository. This is because it can result in errors if the Docker images are not fully tested in sync with the main source code. For example, updates made to the docker images won't necessarily be tested with the current head of the main branch.
We need to move the docker images into a
dockerfolder within this repo and update the ci/cd so that images are built and tested as part of our regular test suite.Value and/or benefit
Anything else?
No response