rusackas opened a new pull request, #40723:
URL: https://github.com/apache/superset/pull/40723
### SUMMARY
`docker.yml` ran change-detection at the **step level**: the `docker-build`
matrix (2 presets on PRs, 7 on push) provisioned a runner per preset, checked
out the repo, ran the `change-detector` action, and *then* skipped its build
steps when no relevant files changed. Docs-only and other unrelated PRs still
spun up those build runners only to no-op.
This adopts the lead-`changes`-job pattern already used by
`superset-frontend.yml` (and proposed for the test workflows in #40718): one
lightweight job runs the change-detector once and exposes `python` /
`frontend`
/ `docker` outputs, and the build jobs gate at the **job level**:
```yaml
docker-build:
needs: [setup_matrix, changes]
if: >-
needs.changes.outputs.python == 'true' ||
needs.changes.outputs.frontend == 'true' ||
needs.changes.outputs.docker == 'true'
```
The push-to-master-only `docker-compose-image-tag` job now also gates on the
`docker` output at the job level. Redundant per-job change-detector steps and
per-step `if:` guards are removed.
### TESTING INSTRUCTIONS
- Code/docker PR: confirm `docker-build` runs its presets as before.
- Docs-only PR: confirm `docker-build` is **skipped** (no build runners spin
up).
### ADDITIONAL INFORMATION
- [ ] Has associated issue:
- [ ] Changes UI
- [ ] Includes DB Migration
- [ ] Introduces new feature or API
- [ ] Removes existing feature or API
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
