ocurrent / ocurrent/ocurrent-deployer
Deployer should submit a summary of the deployability checks.
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 24
- Forks
- 18
- Avg merge
- 16m
- Merged PRs (30d)
- 2
Description
Currently the deployability check just shows as pass or fail, and links to the general project that is being checked.
Often if there are multiple git refs being checked and/or multiple Dockerfiles to check for deployability, it isn't obvious what has failed.
As an improvement ocurrent-deployer should post the summary output of each deployability check with links directly to the failing /passing build step. As per the ocaml-ci compilation UI.
Contributor guide
No contributing guide indexed for this repository
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 tracing how ocurrent-deployer currently reports deployability checks, then compare the desired output with the ocaml-ci compilation UI referenced in the issue. Done means each check posts a summary that identifies the relevant git ref and Dockerfile and links directly to the failing or passing build step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100