Images built in `pre-build` script aren't available in the `Build and Tag Container Image` step
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions
- Domain
- ci-cd
Research direction
Start with the referenced Experimenter workflow run and trace the pre-build stage into Build and Tag Container Image. Read the mentioned build-and-push.yml and build workflow to determine how images are handled between stages. Done means the behavior is documented clearly or the workflow/actions are adjusted and the result is verified.
Written by the indexing model from the issue text.
Description
@dlactin encountered this when trying to onboard Experimenter to this workflow:
Do either of you have opinions about this CI workflow:
If I build this image called megazord using the pre-build command & make it is not available in the next image build step.
I haven't tried this yet, but I believe I could use the build workflow to build the megazord image first and then also the build-and-push.yml workflow to build and push the experimenter image.
Current workflow: https://github.com/dlactin/experimenter/actions/runs/16944528793/workflow
We should find out why images built in the pre-build stage aren't available in later stages, and either document how to make them available or tweak the workflow / actions so they are available
- Dominant language
- No language data
- Stars
- 3
- Forks
- 7
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 mozilla/deploy-actions
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
mozilla/deploy-actions#146 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mozilla/deploy-actions#100 ·
All issues in mozilla/deploy-actions
Similar issues
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 80/100
alunduil/projects-v2-sync#21 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
good first issue No-AI
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
theforeman/obal#459 ·
Maintainers usually reply within 1 day