Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CI/CD: image variants and the cache warm now run in one GitLab job

Open Beginner friendly
  • Is something wrong?
#228 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
gitlab, shell
Domain
ci-cd, documentation

Research direction

Read the image_variants_and_warm function in bin/devops/k8s.sh and the GitLab job description in the issue to confirm the combined job name. Then update content/6.deployment/3.ci-cd.md at lines 246 and 268, replacing the separate variants and warm job names with the combined image variants and warm <track> job. Check the wording at content/6.deployment/4.variables.md line 376. Done when the three pages describe one job per track; the release link waits until the template is released.

Written by the indexing model from the issue text.

Description

From components-web-app/components-web-app#160 (commit 5f987be09ccf7ecfda261be61662020f7d72ea67, in the template's Unreleased section, so the next release after 2.0.0-alpha.30).

On GitLab, the image variants <track> and warm cache <track> jobs are now one job per track, image variants and warm <track> (the image_variants_and_warm function in bin/devops/k8s.sh). A separate warm job waited about 50 s for a runner after every deploy.

  • It runs the variants first and then the warm, in the same order as before (the warm must never come first, #153).
  • Each half keeps its switch: CWA_CI_IMAGE_VARIANTS_* and CWA_CI_WARM_CACHE_*, with production on unless "false" and the other tracks off unless "true". The job runs when either is on.
  • If one half fails, the other still runs. Either failure fails the job, which is allow_failure, so a live deploy is never marked failed.
  • The performance audit <track> jobs now needs: the combined job.
  • GitHub is unchanged: its steps already run one after another in the same job.

Pages to update:

  • content/6.deployment/3.ci-cd.md:246: lists image variants review/staging/canary/production as their own jobs.
  • content/6.deployment/3.ci-cd.md:268: says the warm runs "as its own job" and lists the warm cache <track> jobs.
  • Check content/6.deployment/4.variables.md:376 (CWA_CI_PRODUCTION_DISABLED removes "image variants, cache warm … jobs"); the wording can stay, but there's now one job for both.
  • Add the release link once the template version is released.

Upgrade note for downstream projects: copy .gitlab-ci.yml and bin/devops/k8s.sh. A project job that needs: either old job name must use the new name.

Dominant language
Vue
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from components-web-app/docs

All issues in components-web-app/docs

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.