This repository has been archived by the owner on Aug 22, 2024. It is now read-only.
Create automated build and release firmware #75
Merged
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
Create automated build and release firmware for NEMO
|
Sample Release: |
vs4vijay
commented
Jan 26, 2024
| // -=-=- Uncommenting more than one at a time will result in errors -=-=- | ||
|
|
||
| String buildver="2.3.4"; |
There was a problem hiding this comment.
we no longer need to manage and maintain buildver and bump it everytime. It will be handled automatically by automated build system. We have introduced a pre-processor called NEMO_VERSION with default value dev. This is the value we will get when someone manually builds and flashes from source code.
- When the build happens for a branch (i.e. main branch, feature branches), it will use first 7 chars of commit hash.
- When the build is happening for tag, then the tag_name will be replaced automatically. i.e. v0.0.2, etc.
vs4vijay
commented
Jan 26, 2024
There was a problem hiding this comment.
This file is used by automated build system to generate the index for m5stack boards, libraries etc.
n0xa
approved these changes
Jan 26, 2024
| // -=-=- Uncommenting more than one at a time will result in errors -=-=- | ||
|
|
||
| String buildver="2.3.4"; |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Create automated build and release firmware for NEMO. This PR involves developing an automated system that generates firmware binaries for NEMO, catering to four different supported boards and two languages.
Whenever a push occurs in the "develop" branch or a tag is created, a Github Action will be triggered. This action will initiate the firmware build process for all combinations of supported boards and languages (4 boards x 2 languages). After completion, it will pause and await manual approval before proceeding to create a release.
Runs:
Builds:
Workflow:
Manual Approval flow for Release Creation:
Pre-requisites:
Create an environment called "github_release" from the settings tab.
Add required reviewers for approving the release and save the protection rules.
CC: @n0xa