Advanced CI/CD pipeline
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
Allowing users to have more complex CI/CD workflows would benefit users with complex apps along keeping the process centric within Dokploy avoiding the need to make external integrations (e.g. github actions). So one use case could be a backend service that requires build/test/run migrations/deploy steps to work properly and more safely, we could even allow parallel steps or have dependencies so for example failing tests block deployment.
Describe the solution you'd like
I've worked on sketching out a solution that tries to keep it backwards compatible with existing approach.
Describe alternatives you've considered
Not as of now, but I'm looking for input for this topic.
Additional context
No response
Will you send a PR to implement it?
Yes
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 reviewing Dokploy's existing CI/CD approach and the two solution sketches linked in the issue. The issue has no named files, tests, or acceptance criteria; work would need an agreed design for dependent and parallel steps, migration or deployment handling, and backward compatibility before implementation can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100