keep rolling docker tags of last 4 releases
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem
As an engineer, I would like the ability to easily roll back to a previous release without having to dig through the thousands of docker tags. It would be nice to be able to have - weekly, weekly-1 (weekly minus 1 - one week ago), weekly-2 (weekly minus 2 - 2 weeks ago) etc..
This would allow us to use latest and if we find a blocking issue, switch to weekly-1 or weekly-2 and get last weeks or 2 week old release.
Goal
Be able to easily roll back to a release 1, 2 or 3 weeks old.
Have a weekly cron that auto-tags these for us to keep the list up to date.
Target Personas
- Developer teams
- Content teams
- DevOps teams
- System administrators (dotCMS)
Demo Expectations
How the release, release-1, release-2 tags exist and map to older releases.
Acceptance Criteria
No response
User Stories
No response
Links
No response
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
Start by locating the release process that publishes Docker tags and the weekly automation or cron configuration. Trace how releases are selected and tagged, then verify that the current release and the three preceding weekly releases consistently receive the requested rollback tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100