Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Demonstrate usage in multi-board coverage applications #84

Merged
merged 4 commits into from
Jan 24, 2024
Merged

Demonstrate usage in multi-board coverage applications #84

merged 4 commits into from
Jan 24, 2024

Conversation

per1234
Copy link
Collaborator

@per1234 per1234 commented Jan 24, 2024

The readme contains a set of workflows demonstrating the use of the action.

The action user will often want the system to provide coverage for multiple boards. The configuration of the workflows required for that use case is significantly more complex, especially now that it is necessary to upload each sketches report to a separate artifact. It will be beneficial to demonstrate that advanced usage in addition to the simplified demonstrations.

The demonstrations consist of a significant amount of content so putting them in the readme would harm the readability and approachability of that document. For this reason, they are published in a separate document which is linked to from the readme. This "FAQ" document will serve as a container for the addition of more supplemental documentation in the future.

Some GitHub Actions workflows are provided in the readme to demonstrate the use of the action. These workflows have
dependencies on the "actions/upload-artifact" and "actions/download-artifact" actions.

Previously, these dependencies were pinned to their 3.x major version series. A 4.x major version series of the actions
was recently started. It is best practices to use the latest version of actions, so the documentation should demonstrate
that.

A significant breaking change was introduced in the 4.0.0 release of "actions/upload-artifact": uploading multiple times
to the same artifact is no longer allowed. Previously the "Workflow triggered by `pull_request` event" example workflow
used a single artifact for the sketches report file produced by the matrix job for each of the boards the sketches were
compiled for. It was necessary to adjust the configuration of the workflow to use a separate workflow for each of the
sketches report files in order to accommodate the bump fo the "actions/upload-artifact" action dependency.
@per1234 per1234 added topic: documentation Related to documentation for the project type: enhancement Proposed improvement labels Jan 24, 2024
@per1234 per1234 self-assigned this Jan 24, 2024
The readme contains a set of workflows demonstrating the use of the action in the use case where the report workflow is
triggered by a `schedule` event.

These workflows demonstrate the most simple use case, where sketches are only being compiled for a single board.
Although this provides a good introduction into using the action, the action user will often want the system to provide
coverage for multiple boards. The configuration of the workflows become significantly more complex, especially now that
it is necessary to upload each sketches report to a separate artifact. It will be beneficial to also demonstrate that
advanced usage.

The demonstration consists of a significant amount of content so putting it in the readme would harm the readability and
approachability of that document. For this reason, it is published in a separate document which is linked to from the
readme. This "FAQ" document will serve as a container for the addition of more supplemental documentation in the future.
A demonstration workflow is provided in the readme to show how to use the action in the use case where the report
workflow is triggered by `pull_request` event.

Previously, this workflow demonstrated the more advanced configuration that is required in order to compile for multiple
boards. Although this demonstration will be useful to the action users, it might be overwhelming as an introduction to
the action usage. A demonstration that only compiles for a single board can be far more simple. Even if the user
requires coverage of multiple boards in their application, this will give them a basic understanding of the action
usage.

The advanced demonstration workflow is hereby moved to the FAQ document, replaced in the readme by a simple
demonstration workflow. A link from the readme to the advanced usage demonstration is provided.
@per1234 per1234 merged commit b4d8c01 into arduino:main Jan 24, 2024
10 checks passed
@per1234 per1234 deleted the add-faq branch January 24, 2024 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: documentation Related to documentation for the project type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant