-
Notifications
You must be signed in to change notification settings - Fork 6
Add release-go-crosscompile-task
workflow that use golang crosscompile
#198
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
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 there was only a workflow in the assets repo handling the release of a go project. That workflow was based on the build process we have in the Arduino CLI, but that's not the only way of compiling. We use that one in the Arduino CLI because we need CGO enabled and is not possible with golang crosscompile. The easiest (and fastest) way of cross-compiling is by using environment variables to set the OS and ARCH we want to build for. See https://go.dev/doc/install/source#introduction
per1234
requested changes
Jan 26, 2022
workflow-templates/assets/release-go-crosscompile-task/DistTasks.yml
Outdated
Show resolved
Hide resolved
...lates/dependabot/workflow-template-copies/.github/workflows/release-go-crosscompile-task.yml
Outdated
Show resolved
Hide resolved
per1234
approved these changes
Jan 26, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Umberto!
umbynos
added a commit
to arduino/arduino-cslt
that referenced
this pull request
Jan 26, 2022
umbynos
added a commit
to arduino/arduino-cslt
that referenced
this pull request
Jan 26, 2022
* Add CI workflow to publish releases On every push of a tag named with a version format: - Build the project for all supported platforms. - Sign and notarize the macOS build. - Create a GitHub release. - Builds and checksums are attached as release assets - A changelog generated from the commit history is added to the release description - If the tag has a pre-release version suffix, the GitHub release will be marked as a pre-release. * rename stuff according to arduino/tooling-project-assets#198 * Remove license after #3 * use Go version 1.17 to build * change fine extension to be compliant with assets repo
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 there was only a workflow in the assets repo handling the release of a go project. That workflow was based on the build process we have in the Arduino CLI, but that's not the only way of compiling. We use that one in the Arduino CLI because we need CGO enabled and is not possible with golang crosscompile. The easiest (and fastest) way of cross-compiling is by using environment variables to set the OS and ARCH we want to build for. See https://go.dev/doc/install/source#introduction