OpenConext / OpenConext/OpenConext-BaseContainers
dependencies between actions not enforced
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
There are a number of dependencies between the base containers (for example, "PHP 7.2 Apache2 Node14 Composer2" depends on the "PHP 7.2 Apache2" container), but those are not expressed in the github action flows. This can cause race issues because the dependent container starts building before the dependency is available. See for example https://github.com/OpenConext/OpenConext-BaseContainers/actions/runs/11322704037/attempts/1.
I'm not sure how to solve this, except for creating a single workflow with multiple stages.
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 inspecting the GitHub Action flows that build the base containers and compare them with the example run linked in the issue. Trace which container builds depend on another and choose a workflow dependency structure that prevents dependent builds from starting too early. Done means the dependent containers consistently wait for their required base containers to become available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- build-system, ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100