runner/act
Earl Warren c85eb0e647
fix: use a unique random name to derive network and volumes for a job
When a reusable workflow is called twice in the same workflow in
parallel, it may require a dedicated network to run (for instance if
it spawns services) and will always require unique volumes to mount
the workdir and the env.

There really is no way to guarantee a unique name derived from the
job name etc. Instead, a random name is set and used as a base for
both the internal volumes and the dedicated network (if any).
2025-08-14 17:48:34 +02:00
..
artifactcache chore: to allow the runner to be imported, v9 needs to be in the go module (#777) 2025-07-31 10:35:11 +00:00
cacheproxy chore: panic if a random name cannot be created (#853) 2025-08-14 15:46:01 +00:00
common chore: panic if a random name cannot be created (#853) 2025-08-14 15:46:01 +00:00
container chore: refactor NewDockerVolumeRemoveExecutor (#854) 2025-08-14 15:46:52 +00:00
exprparser feat: added support for dereferenced map properties (#821) 2025-08-10 16:24:02 +00:00
filecollector chore: use t.Context for tests, activate usetesting for lint + add t.TempDir and t.Chdir (#844) 2025-08-11 13:21:42 +00:00
jobparser feat: support evaluation of concurrency clauses in runner (#827) 2025-08-07 21:47:01 +00:00
lookpath chore: use the same .golangci.yml as the runner & gofumpt over gofmt (#206) 2025-07-28 12:26:41 +00:00
model fix: update reusable workflow input handling (#834) 2025-08-11 21:10:44 +00:00
runner fix: use a unique random name to derive network and volumes for a job 2025-08-14 17:48:34 +02:00
schema feat: support evaluation of concurrency clauses in runner (#827) 2025-08-07 21:47:01 +00:00
workflowpattern feat: workflowpattern package (#1618) 2023-02-23 18:21:08 +00:00