While the meat of the devstack is complete (a docker container, with container tags), there are several QOL improvements that we could do to make it easier to use. I think it would be helpful to create a new release with each new build. This would enable:
- We would tag the git repository with the same datestamp tag (
YYYY-MM-DD) as the docker container, which would make it easier to link a specific container back to the source code.
- Creating a new release gives us a chance to update the text of the release body with the specific instructions, including the correct SHA digest, for that specific container and also a report of all the packages included in this release for later reference.
- Creating a new release allows us to pre-build a singularity container and attach it as a release artifact, provided that the file is less than 2GB in size. If the devstack image exceeds that, we'll need to rethink this approach, trim the size of the container, or else host the container somewhere else, like on GCS.
While the meat of the devstack is complete (a docker container, with container tags), there are several QOL improvements that we could do to make it easier to use. I think it would be helpful to create a new release with each new build. This would enable:
YYYY-MM-DD) as the docker container, which would make it easier to link a specific container back to the source code.