Yicong-Huang opened a new issue, #4623:
URL: https://github.com/apache/texera/issues/4623

   ### Task Summary
   
   `.github/workflows/github-action-build.yml` and 
`.github/workflows/reusable-build.yml` currently duplicate the `frontend`, 
`scala`, `python`, and `agent-service` matrix jobs (~150 lines). The two files 
have already drifted: `reusable-build.yml` is missing the recent license-check 
steps (npm bundle check, pip-licenses manifest, binary-deps script, 
distributable-bundle build for jar checks) that exist on `main`'s build path.
   
   Now that `.asf.yaml` only requires `Required Checks` and not the individual 
matrix contexts, we can consolidate without affecting branch protection.
   
   Plan:
   1. Sync `reusable-build.yml` with the latest steps from 
`github-action-build.yml` (license-check additions, bundle build, etc.).
   2. Replace the four matrix jobs in `github-action-build.yml` with a single 
caller job (`uses: ./.github/workflows/reusable-build.yml`).
   3. Update `required-checks` `needs:` from `[precheck, frontend, scala, 
python, agent-service, backport]` to `[precheck, build, backport]`.
   
   Side effects:
   - Job display names gain a `build /` prefix (e.g., `build / frontend 
(ubuntu-latest, 18)`). `.asf.yaml` only references `Required Checks`, so this 
does not affect merge gating.
   - `direct-backport-push.yml`'s job-name prefix matching (`backport (target) 
/`) is unaffected because that prefix comes from the backport caller job, which 
is unchanged.
   
   ### Priority
   
   P3 – Low
   
   ### Task Type
   
   - [x] Refactor / Cleanup
   - [x] DevOps / Deployment


-- 
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]

Reply via email to