Move jobs around so they can be part of a single parallel workflow #203
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CodeGat
force-pushed
the
199-multi-target-deployments
branch
from
ba543c4 to
463afbe
Compare
… job. This matrix job must have the required I/O to do pre-deploy checks, as well as a deployment.
This is due to dynamic matrix job outputs not being collected appropriately. See https://github.com/orgs/community/discussions/17245
…oyment jobs, misc changes
CodeGat
force-pushed
the
199-multi-target-deployments
branch
from
463afbe to
05d4115
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
Although preliminary work had been done on allowing multiple HPC targets (notably by creating a config file that allows for multiple HPCs, using GitHub Environments that correspond to multiple HPCs, and having inputs to existing workflows take a variable GitHub Environment), we aren't fully there yet.
The major change is that we start the matrixing(?) of the overall pipeline much, much earlier. Each matrix job contains the
check-spack-yaml,check-configanddeployjobs, and the rest of the pre- and post- matrix jobs are relatively unchanged. Although, the deployment comment that is generated is now no longer relatively static, but must be generated on the fly depending on how many deployment targets there are.Chicken-scratches on how the workflow looked after and before are below:
References #199