chore: run build-release.sh in client/server CI #279
Merged
+14
−0
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
|
This pull request has been linked to Shortcut Story #222503: Create CI step that tests CMake release commands. |
cwaldren-ld
force-pushed
the
cw/sc-222503/test-release-in-ci
branch
from
4720cc9 to
ad453ef
Compare
kinyoklion
approved these changes
Oct 31, 2023
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.
Right now our release process isn't tested on every commit - if the release fails due to a build issue, we need to make a new release.
This commit runs
./build-releasein our Linux CI step. It's not building docs nor running on all types executors, but I think this is a good compromise to catch 99% of issues that might occur.