Build dotcms-dev:latest every night
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Task
Because we do not have the release process hooked up to the newer cicd pipeline, we need to use the nightly pipeline to build and deploy a dotcms-dev image that uses the latest release. This means that when a new release is pushed, the dev image will be updated with that at the nightly build, keeping it pretty much in sync.
Right now we only have the dotcms/dotcms-dev:nightly, which is ok but can contain some untested or "unreleased" code.
Proposed Objective
Technical User Experience
Proposed Priority
Priority 2 - Important
Acceptance Criteria
Make sure the dotcms/dotcms-dev:latest is built nightly
Make sure it uses the latest dotcms released codebase.
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
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 nightly pipeline configuration and the existing build and deployment steps for dotcms-dev:nightly. Trace how the latest released dotCMS codebase is selected and how Docker images are tagged; done means dotcms/dotcms-dev:latest is built and deployed nightly from the latest release rather than unreleased code.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100