Use workflow job matrix for builds #444
Merged
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
Previously, a single GitHub Actions workflow job was used to make tester, nighly, and release builds of the application. These builds were done serially. A more efficient approach is to run the builds in parallel. This is accomplished by using a job matrix, where each target has its own generated job in the workflow. Previously, checksum generation code was present both in the taskfile and in the workflows (due to the need to update the macOS checksum after the notarization process done in the workflow). The checksum generation is now done exclusively in the build workflows.
per1234
added
type: enhancement
MatteoPologruto
approved these changes
Oct 14, 2022
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.
Previously, a single GitHub Actions workflow job was used to make tester, nightly, and release builds of the application.
These builds were done serially. A more efficient approach is to run the builds in parallel. This is accomplished by using a job matrix, where each target has its own generated job in the workflow.
Previously, checksum generation code was present both in the taskfile and in the workflows (due to the need to update the macOS checksum after the notarization process done in the workflow). The checksum generation is now done exclusively in the build workflows.
This is a sync of the enhancement made by @MatteoPologruto in the reusable project assets hosted in the upstream repository:
arduino/tooling-project-assets#277
Test runs of the updated workflows:
A "Publish Tester Build" workflow run will be triggered for this pull request.