ci: store artifacts after build #79
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
trym-b
force-pushed
the
ci/build-releases-with-github-actions
branch
from
f1f93e8
to
97ffe96
Compare
andrbo
approved these changes
Mar 4, 2024
maeb
reviewed
Mar 5, 2024
maeb
approved these changes
Mar 5, 2024
|
As for the |
# Motivation To be able to build and release more automatic and less dependent on the local environment, we need to store the build artifacts in a place where we can access them later. # Changes Stores some of the build artifacts from the `dist` directory after a successful build. # Future work Use these artifacts to create a release together with autogenerated docs. # Quirks Ideally the artifacts should be built in a separate job to avoid potential contamination of the build environment. But because this is a paid `gorelease` feature we will just have to continue building all targets in one go.
trym-b
force-pushed
the
ci/build-releases-with-github-actions
branch
from
97ffe96
to
af93e5f
Compare
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.
Motivation
To be able to build and release more automatic and less dependent on the local environment, we need
to store the build artifacts in a place where we
can access them later.
Changes
Stores some of the build artifacts from the
distdirectory after a successful build.Future work
Use these artifacts to create a release together
with autogenerated docs.
Quirks
Ideally the artifacts should be built in a
separate job to avoid potential contamination of
the build environment. But because this is a paid
goreleasefeature we will just have to continuebuilding all targets in one go.