ci(workflow): use release build of next-dev for integration test #3650
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
9 Ignored Deployments
|
🟢 CI successful 🟢Thanks |
jridgewell
approved these changes
Feb 6, 2023
kwonoj
added
the
pr: automerge
kwonoj
force-pushed
the
build-next-dev-integration
branch
from
e64aa12
to
ad07c61
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.
Context: https://vercel.slack.com/archives/C04KC8A53T7/p1675471724960239?thread_ts=1675469142.533699&cid=C04KC8A53T7
There are some expected failures with debug build (without proper setup) for the integration test. This PR choose to build release binary, as it'll also help overall test turnaround time since debug build is lot slower.