`.release_windows*` jobs are running even though `check windows * test failures` failed
With the introduction of !2076 (merged) there was an undesirable change in behavior, where .release_windows*
jobs are running even though check windows * test failures
failed. This is caused by the way the needs
array is merged. Discussion happened here for the test coverage report
job, but we need to also take into consideration the needs
array of the .release_windows*
jobs.
Proposal
- Option 1: Create a
.release_windows_${VERSION}_docker_image
job that encapsulates.release_windows${VERSION}
and.release_windows_docker_images
and ensures that theneeds
array is correctly merged. - Option 2: Use YAML anchors to create and import the
needs
arrays.