jstone 7474 I chatted with Jorge the
@.jstone I chatted with Jorge the other night about working on improving build scheduling, triggering downstream builds, etc
well, i haven't got too far, but i did learn something possibly helpful for that and/or other github action workflow...
I know your build workflows have several cases of using step output in subsequent steps, but I was trying to use job output to gate and/or provide context to the next job. Really the idea is to have a single job that can decide if things should proceed before spawning the matrix jobs.
Here's what I came up with: https://github.com/bsherman/ucore-kmods/blob/main/.github/workflows/build.yml#L19-L51
You may know that trick, but it took me a while to sort it out so I wanted to share.
well, i haven't got too far, but i did learn something possibly helpful for that and/or other github action workflow...
I know your build workflows have several cases of using step output in subsequent steps, but I was trying to use job output to gate and/or provide context to the next job. Really the idea is to have a single job that can decide if things should proceed before spawning the matrix jobs.
Here's what I came up with: https://github.com/bsherman/ucore-kmods/blob/main/.github/workflows/build.yml#L19-L51
You may know that trick, but it took me a while to sort it out so I wanted to share.
