Page MenuHomePhabricator

Stop running the build-coverage-report job alongside the 'build-and-test-image' job in CI for the orchestrator on pushes?
Open, LowPublic

Description

Currently on build we run both build-coverage-report and build-and-test-image. The latter builds the image and then does the full lint-and-unit-test run; the former runs npm coverage, which isn't needed in a pre-merge CI run.

Let's simplify things (and use less CI server space!) and just run the main job, renaming test to build-coverage-report and only running it when needed, unless I'm missing something?

  • Rename test to build-coverage-report
  • Rename test-build-and-run-image to build-and-test-image
  • Only run the coverage job before merge, but still be blocking

Details

TitleReferenceAuthorSource BranchDest Branch
build: Rename 'test' job to clearer 'build-coverage-report'repos/abstract-wiki/wikifunctions/function-orchestrator!19jforresterT337504main
Customize query in GitLab

Event Timeline

Jdforrester-WMF created this task.
Jdforrester-WMF renamed this task from Stop running the coverage job (named 'test') alongside the 'test-build-and-run-image' job in CI for the orchestrator to Stop running the build-coverage-report job alongside the 'build-and-test-image' job in CI for the orchestrator on pushes?.Jul 12 2023, 2:41 PM
Jdforrester-WMF updated the task description. (Show Details)