-
-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐕 Batch: Add versioning in Docker builds #1069
Comments
We decided:
|
Hi @DhanshreeA Have the decisions set above been converted to actual tasks? Is this a Batch or an Epic, and are there other issues open related to this? |
@GemmaTuron the discussion above has not been converted to tasks, and I would qualify this as a batch since it would take a non trivial amount of effort to complete this, however not as intense as an epic/sprint. |
Once we start tackling this, please define specific tasks as individual issues to be tackled. Meanwhile it will remain on hold. |
Hi @DhanshreeA |
@GemmaTuron I think we now have sufficient bandwidth to fully tackle this in the coming weeks. I will prioritise this starting next week. |
Updates:
|
Summary
Right now all our Docker images are tagged "latest" by default. This is quite problematic, since we cannot roll back to a version we knew worked (especially since we don't have tests for the builds themselves). Another reason why this would have been nice to have is for sake of comparison around size differences between older builds and the new slimmer builds. I reckon this would not be entirely easy to implement since the ersilia cli isn't tag aware and always pulls the latest tag.
Objectives
###Documentation
The text was updated successfully, but these errors were encountered: