actions/runner
1
0
Fork 0
mirror of https://github.com/actions/runner.git synced 2025-12-11 12:57:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

.

Browse Source
This commit is contained in:
eric sciple
2021-04-07 11:18:05 -05:00
parent 8932ad8d94
commit ec910bab3d
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/adrs/0000-composite-actions.md → docs/adrs/1040-composite-supports-action-steps.md
View File

@@ -27,12 +27,15 @@ TODO: Move these details into a tracking issue instead
- Update schema to support `uses` within a composite step
- src/Runner.Worker/action_yaml.json
- src/Sdk/DTPipelines/Pipelines/ObjectTemplating/PipelineTemplateConverter.cs
- Manage inputs/outputs between nested layers
- Mimic server validation, generate IDs, etc
- Handle inputs/outputs between nested layers
- Update server to generate context names when empty
- Fix issue with `hashFiles` within a composite action
- https://github.com/actions/runner/issues/991
- Support actions with pre-step and post-step
- Investigate whether CompositeActionHandler.cs especially wrt clearing the output scopes
- Support container-actions and actions with pre-step and post-step
- Investigate how to deal with pre-steps. Today, nested steps are created just-in-time. However, pre-steps are generally executed before regular steps. Container actions implicitly have a pre-step to pull or build the image
- Investigate whether we copy the continue-on-error setting to the pre/post steps
- Investigate CompositeActionHandler.cs especially wrt clearing the output scopes
- Investigate whether we need additional validation to restrict contexts available to pre-step condition and post-step condition
- Testing
- Support all types of action manifests: Node.js, Dockerfile, `docker://`, composite, no manifest only Dockerfile