archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/.github/workflows/build_and_test.yml

218 lines
6.7 KiB
YAML
Raw Normal View History

Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
name: build-and-test
on:
push:
branches: ['canary']
Update workflow cancel handling (#50442) The built-in cancel handling doesn't have our desired behavior so this disables it
2023-05-28 07:57:45 +02:00
pull_request:
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
types: [opened, synchronize]
env:
NAPI_CLI_VERSION: 2.14.7
TURBO_VERSION: 1.9.6
Fix pnpm `ERR_INVALID_THIS` on Node 20 (#51406) ### What? Fixes pnpm/pnpm#6424 ### Why? So users of Node 20 can contribute to Next.js ### How? Upgrades pnpm with back compatibility to patch `ERR_INVALID_THIS` error. If Node 14 support isn't necessary, I'd recommend upgrading to pnpm 8 for continued feature support and committing the lockfile. --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-16 14:37:11 +02:00
PNPM_VERSION: 7.32.2
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
NODE_MAINTENANCE_VERSION: 16
NODE_LTS_VERSION: 18
Update test concurrency (#50588)
2023-05-31 15:15:18 +02:00
TEST_CONCURRENCY: 6
better rust setup in CI (#50905) ### Description Set some environment variables that reduce size on disk and make the build a little faster. Also, read the toolchain from the `rust-toolchain` file, so it's not duplicated in every workflow. Ported over from the `turbo` repo.
2023-06-07 18:53:50 +02:00
# disable backtrace for test snapshots
RUST_BACKTRACE: 0
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
TURBO_TEAM: 'vercel'
TURBO_REMOTE_ONLY: 'true'
NEXT_TELEMETRY_DISABLED: 1
# we build a dev binary for use in CI so skip downloading
# canary next-swc binaries in the monorepo
NEXT_SKIP_NATIVE_POSTINSTALL: 1
ci(workflow): enable test trace again (#50817) ### What? Another attempt to https://github.com/vercel/next.js/pull/50619 and WEB-1150, trying to apply setup guard more throughly. I still do not know why original PR passed CI but fails to subsequent PRs after merge, but hope this could be a right guard to prevent unexpected failures.
2023-06-08 12:52:49 +02:00
DATADOG_API_KEY: ${{ secrets.DATA_DOG_API_KEY }}
ci(workflow): enable test trace upload (#51107) ### What? WEB-1150. This PR is an attempt to upload next.js's test results into datadog test trace to track its status. Originally it tried to use automatic trace injection (dd-trace/ci/init). However, due to some of custom environments / setup we use it was not compatible out of the box. Instead, this PR injects a new test reportert to generate junit report, then upload it at once at the end of the testing pipeline. The reporter is configured to run when necessary variables set, local run should not be affected. One thing to note is this report will not count retry results, as it'll create duplicated test entry with multiple results since we runts jest per individual test. This'll allow to detect flaky test easier, but also it means we'll get bit of skewed test results compare to the real world as first failure will be accounted as test fail immediately.
2023-06-12 19:14:13 +02:00
DATADOG_TRACE_NEXTJS_TEST: 'true'
ci(workflow): enable test trace again (#50817) ### What? Another attempt to https://github.com/vercel/next.js/pull/50619 and WEB-1150, trying to apply setup guard more throughly. I still do not know why original PR passed CI but fails to subsequent PRs after merge, but hope this could be a right guard to prevent unexpected failures.
2023-06-08 12:52:49 +02:00
DD_ENV: 'ci'
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
TEST_TIMINGS_TOKEN: ${{ secrets.TEST_TIMINGS_TOKEN }}
NEXT_TEST_JOB: 1
jobs:
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
build-native:
name: build-native
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
with:
skipInstallBuild: 'yes'
secrets: inherit
build-next:
name: build-next
uses: ./.github/workflows/build_reusable.yml
with:
skipNativeBuild: 'yes'
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
secrets: inherit
lint:
name: lint
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needs: ['build-native', 'build-next']
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
with:
afterBuild: pnpm lint-no-typescript && pnpm check-examples
secrets: inherit
check-types-precompiled:
name: types and precompiled
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needs: ['build-native', 'build-next']
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
with:
afterBuild: pnpm types-and-precompiled
skipForDocsOnly: 'yes'
secrets: inherit
test-cargo-unit:
name: test cargo unit
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needs: ['build-next']
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
with:
skipForDocsOnly: 'yes'
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needsRust: 'yes'
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
skipInstallBuild: 'yes'
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
skipNativeBuild: 'yes'
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
afterBuild: turbo run test-cargo-unit
secrets: inherit
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
test-cargo-integration:
name: test cargo integration
needs: ['build-next']
uses: ./.github/workflows/build_reusable.yml
with:
skipForDocsOnly: 'yes'
needsNextest: 'yes'
needsRust: 'yes'
skipNativeBuild: 'yes'
afterBuild: xvfb-run turbo run test-cargo-integration
test-cargo-bench:
name: test cargo benchmarks
needs: ['build-next']
uses: ./.github/workflows/build_reusable.yml
with:
skipForDocsOnly: 'yes'
Skip cargo bench job on release (#51311) This fails when run during a release since the new version isn't published yet x-ref: https://github.com/vercel/next.js/actions/runs/5266469610/jobs/9520466217
2023-06-14 23:44:23 +02:00
skipForRelease: 'yes'
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needsRust: 'yes'
skipNativeBuild: 'yes'
afterBuild: xvfb-run turbo run test-cargo-bench
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
rust-check:
name: rust check
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needs: ['build-next']
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
with:
skipForDocsOnly: 'yes'
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needsRust: 'yes'
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
skipInstallBuild: 'yes'
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
skipNativeBuild: 'yes'
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
afterBuild: turbo run rust-check
secrets: inherit
test-turbopack-dev:
name: test turbopack dev
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needs: ['build-native', 'build-next']
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
with:
skipForDocsOnly: 'yes'
afterBuild: RUST_BACKTRACE=0 NEXT_EXTERNAL_TESTS_FILTERS="$(pwd)/packages/next-swc/crates/next-dev-tests/tests-manifest.js" __INTERNAL_NEXT_DEV_TEST_TURBO_DEV=TRUE __INTERNAL_CUSTOM_TURBOPACK_BINDINGS="$(pwd)/packages/next-swc/native/next-swc.linux-x64-gnu.node" __INTERNAL_NEXT_DEV_TEST_TURBO_GLOB_MATCH="*" NEXT_E2E_TEST_TIMEOUT=240000 NEXT_TEST_MODE=dev node run-tests.js --type development --timings -c ${TEST_CONCURRENCY}
secrets: inherit
test-next-swc-wasm:
name: test next-swc wasm
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needs: ['build-native', 'build-next']
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
with:
skipForDocsOnly: 'yes'
afterBuild: rustup target add wasm32-unknown-unknown && curl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | sh && node ./scripts/normalize-version-bump.js && turbo run build-wasm -- --target nodejs --features tracing/release_max_level_info && git checkout . && mv packages/next-swc/crates/wasm/pkg packages/next-swc/crates/wasm/pkg-nodejs && node ./scripts/setup-wasm.mjs && NEXT_TEST_MODE=start TEST_WASM=true node run-tests.js test/integration/production/test/index.test.js test/e2e/streaming-ssr/index.test.ts
secrets: inherit
test-dev:
name: test dev
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needs: ['build-native', 'build-next']
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
strategy:
fail-fast: false
matrix:
group: [1, 2, 3]
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
with:
skipForDocsOnly: 'yes'
afterBuild: NEXT_TEST_MODE=dev node run-tests.js --timings -g ${{ matrix.group }}/3 -c ${TEST_CONCURRENCY} --test-pattern '^(development|e2e|unit)/.*\.test\.(js|jsx|ts|tsx)$'
secrets: inherit
test-prod:
name: test prod
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needs: ['build-native', 'build-next']
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
strategy:
fail-fast: false
matrix:
group: [1, 2, 3]
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
with:
skipForDocsOnly: 'yes'
afterBuild: NEXT_TEST_MODE=start node run-tests.js --timings -g ${{ matrix.group }}/3 -c ${TEST_CONCURRENCY} --test-pattern '^(production|e2e)/.*\.test\.(js|jsx|ts|tsx)$'
secrets: inherit
test-integration:
name: test integration
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needs: ['build-native', 'build-next']
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
strategy:
fail-fast: false
matrix:
group: [1, 2, 3, 4, 5, 6]
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
with:
Ensure swc builds are triggered eagerly (#50632) Ensures we continue pre-building binaries on merge to canary and ensures we are testing against the maintenance Node.js version also adds turbo summarize for all swc builds.
2023-06-01 12:43:09 +02:00
nodeVersion: 16
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
skipForDocsOnly: 'yes'
afterBuild: node run-tests.js --timings -g ${{ matrix.group }}/6 -c ${TEST_CONCURRENCY} --test-pattern '^(integration)/.*\.test\.(js|jsx|ts|tsx)$'
secrets: inherit
test-firefox-safari:
name: test firefox and safari
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
needs: ['build-native', 'build-next']
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
Update PR stats workflow (#50853) Updates to re-use our build workflow so turbo remote cache is leveraged and updates re-usable workflow reference to be the same branch instead of main.
2023-06-06 18:57:09 +02:00
uses: ./.github/workflows/build_reusable.yml
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
with:
skipForDocsOnly: 'yes'
afterBuild: pnpm playwright install && BROWSER_NAME=firefox node run-tests.js test/integration/production/test/index.test.js && BROWSER_NAME=safari NEXT_TEST_MODE=start node run-tests.js -c 1 test/integration/production/test/index.test.js test/e2e/basepath.test.ts && BROWSER_NAME=safari DEVICE_NAME='iPhone XR' node run-tests.js -c 1 test/production/prerender-prefetch/index.test.ts
secrets: inherit
ci(workflow): enable test trace upload (#51107) ### What? WEB-1150. This PR is an attempt to upload next.js's test results into datadog test trace to track its status. Originally it tried to use automatic trace injection (dd-trace/ci/init). However, due to some of custom environments / setup we use it was not compatible out of the box. Instead, this PR injects a new test reportert to generate junit report, then upload it at once at the end of the testing pipeline. The reporter is configured to run when necessary variables set, local run should not be affected. One thing to note is this report will not count retry results, as it'll create duplicated test entry with multiple results since we runts jest per individual test. This'll allow to detect flaky test easier, but also it means we'll get bit of skewed test results compare to the real world as first failure will be accounted as test fail immediately.
2023-06-12 19:14:13 +02:00
report-test-results:
needs: ['test-dev', 'test-prod', 'test-integration', 'test-turbopack-dev']
ci(workflow): skip test trace upload when test skips (#51190) <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### Why? ### How? Closes NEXT- Fixes # --> ### What? Attempt to fix workflow to skip trace upload if test skips.
2023-06-13 17:06:15 +02:00
uses: ./.github/workflows/build_reusable.yml
with:
skipForDocsOnly: 'yes'
uploadTestTrace: 'yes'
secrets: inherit
ci(workflow): enable test trace upload (#51107) ### What? WEB-1150. This PR is an attempt to upload next.js's test results into datadog test trace to track its status. Originally it tried to use automatic trace injection (dd-trace/ci/init). However, due to some of custom environments / setup we use it was not compatible out of the box. Instead, this PR injects a new test reportert to generate junit report, then upload it at once at the end of the testing pipeline. The reporter is configured to run when necessary variables set, local run should not be affected. One thing to note is this report will not count retry results, as it'll create duplicated test entry with multiple results since we runts jest per individual test. This'll allow to detect flaky test easier, but also it means we'll get bit of skewed test results compare to the real world as first failure will be accounted as test fail immediately.
2023-06-12 19:14:13 +02:00
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
tests-pass:
needs:
[
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
'build-native',
'build-next',
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
'lint',
'check-types-precompiled',
'test-dev',
'test-prod',
'test-integration',
'test-cargo-unit',
add turbopack integration tests to CI (#50904) ### What? * enable turbopack tests in new CI * split pre-build step into native and JS builds to allow to start native tests faster * update swc_core to sync with turbo * update turbopack ### Why? Running our test suite is still important as long we don't have the full integration test suite enabled. ### Turbopack updates * https://github.com/vercel/turbo/pull/5215 <!-- OJ Kwon - ci(workflow): upload benchmark results to datadog --> * https://github.com/vercel/turbo/pull/5239 <!-- OJ Kwon - fix(swc_plugin): use shared runtime --> * https://github.com/vercel/turbo/pull/3090 <!-- CHEN Yuan - Docs: prior to run testcases, add guides to install dependencies for testcases. --> * https://github.com/vercel/turbo/pull/5264 <!-- Tobias Koppers - update test runner --> --------- Co-authored-by: JJ Kasper <jj@jjsweb.site>
2023-06-12 16:47:43 +02:00
'test-cargo-integration',
'test-cargo-bench',
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
'rust-check',
'test-next-swc-wasm',
'test-turbopack-dev',
]
Ensure final workflow job always runs (#50589) Makes sure we either fail or succeed the single required job correctly
2023-05-31 15:51:13 +02:00
if: always()
Add new build and test workflow (#50436) This adds new `build and test` and `build and deploy` workflows in favor of the existing massive `build, test, and deploy` workflow. Since the new workflows will use `pull_request_target` this waits to remove the existing workflow until the new one is tested. While testing this new workflow flakey behavior in tests have also been addressed. Along with the new workflow we will also be leveraging new runners which allow us to run tests against the production binary of `next-swc` so this avoids slight differences in tests we've seen due to running against the dev binary. Furthermore we will have a new flow for allowing workflow runs on PRs from external forks which will either require a comment be checking a box approving the run after each change or a label added by the team. The new flow also no longer relies on `actions/cache` or similar which have proven to be pretty unreliable. Tests runs with the new workflow can be seen here https://github.com/vercel/next.js/actions/runs/5100673508/jobs/9169416949
2023-05-28 06:02:31 +02:00
runs-on: [self-hosted, linux, x64]
name: thank you, next
steps:
Ensure final workflow job always runs (#50589) Makes sure we either fail or succeed the single required job correctly
2023-05-31 15:51:13 +02:00
- run: exit 1
Fix required check job (#50620) x-ref: https://github.com/vercel/next.js/actions/runs/5138467619/attempts/1
2023-06-01 03:38:53 +02:00
if: ${{ always() && contains(needs.*.result, 'failure') }}
Reference in a new issue Copy permalink