Split workflows for reusability #13
Draft
Conversation
This file contains hidden or 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
- Separates workflow into distinct stages: - meta: determines the base (sha) and permatags (branch, git-tag) to apply to the image - build: builds the multi-platform dockerfile with a build-specific tag - test: a repo-specific workflow that runs the tests - tag: applies permatags to the tested image - This is a proof-of-concept on the path towards centralizing and versioning the reusable parts of our workflows. The common elements (meta, build, and tag) would be centralized, with individual repos only having to write a test workflow to run their tests and a ci workflow to weave the different reusable workflows together.
danschmidt5189
force-pushed
the
workflow-external-test
branch
from
a23a76a to
b5d89f8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is a proof-of-concept on the path towards centralizing and versioning the reusable parts of our workflows. The common elements (determining image metadata, building the image, and tagging it with permatags) would be centralized. Individual repos would include a custom test workflow plus a simple "ci" workflow to weave things together.
The extracted/reusable workflows are:
These reusable components are triggered on "workflow_call", meaning they can only be launched by another workflow, in this case ci.yml.