Have the build status be output of the Docker containers
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker
- Domain
- build-system, ci-cd
Research direction
Start by inspecting how the Docker build is invoked through Jenkins and how the build containers report their results. Trace the container exit status through the build process, then verify that Jenkins reports failure when the engine build or unit tests fail and success when they pass.
Written by the indexing model from the issue text.
Description
Right now if you run the docker build through Jenkins the output will always be a success, because the docker build command was successful. However, I would like the actual build status to be the output of the docker containers.
- Dominant language
- Dockerfile
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from flingengine/FlingDockerBuild
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in flingengine/FlingDockerBuild
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Qiskit/benchpress#116 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
adobe-fonts/source-serif#153 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
fwcd/tree-sitter-kotlin#289 ·
-
area:ai-suggestions bug P1
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
uttrflow/uttrflow-swift#3456 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100