Provide a method to rollback the base image
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 39
- Avg merge
- 18d 18h
- Merged PRs (30d)
- 1
Description
We've had a few instances where changes to the base image (ghcr.io/pulp/pulp-ci-centos:latest) have caused the developer environment to break (in some cases for up to a week with the user permission changes). Developers should have the option to rollback to a previous base image when this happens so that they can continue working while a fix is created.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by inspecting the repository's developer-environment setup and search for references to ghcr.io/pulp/pulp-ci-centos:latest. Done means developers can select a previous base image when the latest image breaks the environment, with the behavior covered by appropriate tests or documented usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- developer-experience, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100