mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2026-05-20 01:36:37 +00:00
75cb38faa6
This change allows the `with:` field of a reusable workflow to reference a previous job, such as `with: { some-input: "${{ needs.other-job.outputs.other-output }}" }`. `strategy.matrix` can also reference `${{ needs... }}`.
When a job is parsed and encounters this situation, the outer job of the workflow is marked with a field `incomplete_with` (or `incomplete_matrix`), indicating to Forgejo that it can't be executed as-is and the other jobs in its `needs` list need to be completed first. And then in `job_emitter.go` when one job is completed, it checks if other jobs had a `needs` reference to it and unblocks those jobs -- but if they're marked with `incomplete_with` then they can be sent back through the job parser, with the now-available job outputs, to be expanded into the correct definition of the job.
The core functionality for this already exists to allow `runs-on` and `strategy.matrix` to reference the outputs of other jobs, but it is expanded upon here to include `with` for reusable workflows.
There is one known defect in this implementation, but it has a limited scope -- if this code path is used to expand a nested reusable workflow, then the `${{ input.... }}` context will be incorrect. This will require an update to the jobparser in runner version 12.4.0, and so it is out-of-scope of this PR.
## Checklist
The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org).
### Tests
- I added test coverage for Go changes...
- [x] in their respective `*_test.go` for unit tests.
- [ ] in the `tests/integration` directory if it involves interactions with a live Forgejo server.
- I added test coverage for JavaScript changes...
- [ ] in `web_src/js/*.test.js` if it can be unit tested.
- [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)).
- **end-to-end test:** will require the noted "known defect" to be resolved, but tests are authored at https://code.forgejo.org/forgejo/end-to-end/compare/main...mfenniak:expand-reusable-workflows-needs
### Documentation
- [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change.
- [x] I did not document these changes and I do not expect someone else to do it.
### Release notes
- [ ] I do not want this change to show in the release notes.
- [x] I want the title to show in the release notes with a link to this pull request.
- [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title.
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/10647
Reviewed-by: Andreas Ahlenstorf <aahlenst@noreply.codeberg.org>
Co-authored-by: Mathieu Fenniak <mathieu@fenniak.net>
Co-committed-by: Mathieu Fenniak <mathieu@fenniak.net>
60 lines
1.1 KiB
YAML
60 lines
1.1 KiB
YAML
-
|
|
id: 100
|
|
task_id: 100
|
|
output_key: colors
|
|
output_value: '["red", "blue", "green"]'
|
|
-
|
|
id: 101
|
|
task_id: 101
|
|
output_key: colors
|
|
output_value: '[]'
|
|
-
|
|
id: 102
|
|
task_id: 102
|
|
output_key: datacenters
|
|
output_value: '["site-a", "site-b"]'
|
|
-
|
|
id: 103
|
|
task_id: 102
|
|
output_key: node-versions
|
|
output_value: '["12.x", "14.x"]'
|
|
-
|
|
id: 104
|
|
task_id: 102
|
|
output_key: pg_version
|
|
output_value: '[17, 18]'
|
|
-
|
|
id: 105
|
|
task_id: 103
|
|
output_key: entire-matrix
|
|
output_value: '{"datacenter": ["site-a", "site-b"], "node": ["12.x", "14.x"], "pg": [17, 18]}'
|
|
-
|
|
id: 106
|
|
task_id: 104
|
|
output_key: scalar-value
|
|
output_value: just some value
|
|
-
|
|
id: 107
|
|
task_id: 105
|
|
output_key: run-on-this
|
|
output_value: nixos-25.11
|
|
-
|
|
id: 108
|
|
task_id: 106
|
|
output_key: entire-matrix
|
|
output_value: '{"datacenter": ["site-a", "site-b"], "node": ["12.x", "14.x"], "pg": [17, 18]}'
|
|
-
|
|
id: 109
|
|
task_id: 107
|
|
output_key: run-on-this
|
|
output_value: nixos-25.11
|
|
-
|
|
id: 110
|
|
task_id: 108
|
|
output_key: workflow_input
|
|
output_value: my-workflow-input
|
|
-
|
|
id: 111
|
|
task_id: 109
|
|
output_key: workflow_input
|
|
output_value: my-workflow-input
|