You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The existing Workflow/Job attributes are extremely limiting. As implemented to produce more than one job per triggered workflow in GitHubActions you would need to add multiple OS Images... One problem with this is that it assumes you want to run the same exact target each time.
A far better scenario is one in which I can create 1-N GitHub Workflows each of which could have 1-N Jobs, Jobs may define relationships such as a particular Job needs other jobs to pass before it can start, and Jobs may need to download artifacts from other jobs. This is currently implemented in the Nuke.Maui repo. You'll notice that the sample generates 2 workflows, one for CI each time the master branch is updated, and on for PRs. There are several jobs defined including one to publish the library which is excluded from the PRs while the other jobs are declared once and reused across multiple workflows.
Description
The existing Workflow/Job attributes are extremely limiting. As implemented to produce more than one job per triggered workflow in GitHubActions you would need to add multiple OS Images... One problem with this is that it assumes you want to run the same exact target each time.
A far better scenario is one in which I can create
1-N
GitHub Workflows each of which could have1-N
Jobs, Jobs may define relationships such as a particular Job needs other jobs to pass before it can start, and Jobs may need to download artifacts from other jobs. This is currently implemented in the Nuke.Maui repo. You'll notice that the sample generates 2 workflows, one for CI each time the master branch is updated, and on for PRs. There are several jobs defined including one to publish the library which is excluded from the PRs while the other jobs are declared once and reused across multiple workflows.Usage Example
Alternative
Currently multiple YAML files need to be generated. To bring these into a single file is a manual process.
The text was updated successfully, but these errors were encountered: