diff --git a/_api/v1/build_distributions/schema/subset/post.json b/_api/v1/build_distributions/schema/subset/post.json index 09eba72b..32278fe4 100644 --- a/_api/v1/build_distributions/schema/subset/post.json +++ b/_api/v1/build_distributions/schema/subset/post.json @@ -5,7 +5,7 @@ "fixed_test_suite_split": true, "cache_read_attempt": true, "commit_hash": "6e3396177d9f8ca87e2b93b4b0a25babd09d574d", - "branch": "master", + "branch": "main", "node_total": "4", "node_index": "0", "ci_build_id": 1234, @@ -25,7 +25,7 @@ "fixed_test_suite_split": true, "cache_read_attempt": false, "commit_hash": "6e3396177d9f8ca87e2b93b4b0a25babd09d574d", - "branch": "master", + "branch": "main", "node_total": "4", "node_index": "0", "ci_build_id": 1234, diff --git a/_api/v1/build_subsets/schema/post.json b/_api/v1/build_subsets/schema/post.json index 1323f6a8..b13cf111 100644 --- a/_api/v1/build_subsets/schema/post.json +++ b/_api/v1/build_subsets/schema/post.json @@ -1,6 +1,6 @@ { "commit_hash": "6e3396177d9f8ca87e2b93b4b0a25babd09d574d", - "branch": "master", + "branch": "main", "node_total": "4", "node_index": "0", "test_files": [ diff --git a/_api/v1/build_subsets/schema/post_response_201.json b/_api/v1/build_subsets/schema/post_response_201.json index e9272026..6fd1d99e 100644 --- a/_api/v1/build_subsets/schema/post_response_201.json +++ b/_api/v1/build_subsets/schema/post_response_201.json @@ -5,5 +5,5 @@ Response does not contain any data. // when successfully created BuildSubset record on API side // and Knapsack Pro client is outdated { - "message": "Please update client knapsack_pro-ruby/rspec 2.3.0 version to 2.4.0. See CHANGELOG: https://github.com/KnapsackPro/knapsack_pro-ruby/blob/master/CHANGELOG.md#change-log" + "message": "Please update client knapsack_pro-ruby/rspec 2.3.0 version to 2.4.0. See CHANGELOG: https://github.com/KnapsackPro/knapsack_pro-ruby/blob/main/CHANGELOG.md#change-log" } diff --git a/_api/v1/builds/main.raml b/_api/v1/builds/main.raml index 98ef3b90..0810a819 100644 --- a/_api/v1/builds/main.raml +++ b/_api/v1/builds/main.raml @@ -9,7 +9,7 @@ get: You can provide optional query params to filter list of CI builds by **commit_hash**, **branch**, **node_total**. - Example 1: /v1/builds?page=1&branch=master&node_total=2 + Example 1: /v1/builds?page=1&branch=main&node_total=2 Example 2: /v1/builds?page=1&commit_hash=d1acb81ac1bead703eb6de64d1af24104d5d4b2c diff --git a/_api/v1/builds/schema/index/response_200.json b/_api/v1/builds/schema/index/response_200.json index 8edd96bd..60db2ae8 100644 --- a/_api/v1/builds/schema/index/response_200.json +++ b/_api/v1/builds/schema/index/response_200.json @@ -10,17 +10,17 @@ "is_page_out_of_range": false }, "links": { - "first": "https://api.knapsackpro.com/v1/builds?branch=master&commit_hash=d1acb81ac1bead703eb6de64d1af24104d5d4b2c&node_total=2&page=1", + "first": "https://api.knapsackpro.com/v1/builds?branch=main&commit_hash=d1acb81ac1bead703eb6de64d1af24104d5d4b2c&node_total=2&page=1", "prev": null, - "self": "https://api.knapsackpro.com/v1/builds?branch=master&commit_hash=d1acb81ac1bead703eb6de64d1af24104d5d4b2c&node_total=2&page=1", + "self": "https://api.knapsackpro.com/v1/builds?branch=main&commit_hash=d1acb81ac1bead703eb6de64d1af24104d5d4b2c&node_total=2&page=1", "next": null, - "last": "https://api.knapsackpro.com/v1/builds?branch=master&commit_hash=d1acb81ac1bead703eb6de64d1af24104d5d4b2c&node_total=2&page=1" + "last": "https://api.knapsackpro.com/v1/builds?branch=main&commit_hash=d1acb81ac1bead703eb6de64d1af24104d5d4b2c&node_total=2&page=1" }, "data": [ { "id": "07c0fca5-9a6c-4313-b176-25dad6139057", "commit_hash": "d1acb81ac1bead703eb6de64d1af24104d5d4b2c", - "branch": "master", + "branch": "main", "node_total": 2, "created_at": "2019-09-18T17:54:54.430Z", "updated_at": "2019-09-18T18:02:16.149Z" diff --git a/_api/v1/builds/schema/show/response_200.json b/_api/v1/builds/schema/show/response_200.json index f0dbb804..bf5dfd7a 100644 --- a/_api/v1/builds/schema/show/response_200.json +++ b/_api/v1/builds/schema/show/response_200.json @@ -1,7 +1,7 @@ { "id": "ba2190af-1bb1-4e3a-8ce1-37303549a4c3", "commit_hash": "347f33f598e5c66727e36b6f0c13b034f6a057f0", - "branch": "master", + "branch": "main", "node_total": 2, "created_at": "2018-04-02T10:00:44.741Z", "updated_at": "2018-04-02T10:00:44.763Z", diff --git a/_api/v1/params/branch.raml b/_api/v1/params/branch.raml index db915280..aea5a9be 100644 --- a/_api/v1/params/branch.raml +++ b/_api/v1/params/branch.raml @@ -1,5 +1,5 @@ type: string required: true -example: master +example: main description: | You are running tests on this branch. diff --git a/_api/v1/params/filters/branch.raml b/_api/v1/params/filters/branch.raml index 196672ea..e5b475ac 100644 --- a/_api/v1/params/filters/branch.raml +++ b/_api/v1/params/filters/branch.raml @@ -1,5 +1,5 @@ type: string required: false -example: master +example: main description: | You can filter by branch name. diff --git a/_api/v1/queues/schema/queue/post.json b/_api/v1/queues/schema/queue/post.json index 8e5ff7da..b609eaa8 100644 --- a/_api/v1/queues/schema/queue/post.json +++ b/_api/v1/queues/schema/queue/post.json @@ -6,7 +6,7 @@ "attempt_connect_to_queue": true, "fixed_queue_split": false, "commit_hash": "6e3396177d9f8ca87e2b93b4b0a25babd09d574d", - "branch": "master", + "branch": "main", "node_total": "4", "node_index": "0", "node_build_id": "1234", @@ -27,7 +27,7 @@ "attempt_connect_to_queue": false, "fixed_queue_split": false, "commit_hash": "6e3396177d9f8ca87e2b93b4b0a25babd09d574d", - "branch": "master", + "branch": "main", "node_total": "4", "node_index": "0", "node_build_id": "1234", @@ -58,7 +58,7 @@ "attempt_connect_to_queue": false, "fixed_queue_split": false, "commit_hash": "6e3396177d9f8ca87e2b93b4b0a25babd09d574d", - "branch": "master", + "branch": "main", "node_total": "4", "node_index": "0", "node_build_id": "1234", diff --git a/_posts/2017-07-17-when-distributed-locks-might-be-helpful-in-ruby-on-rails-application.md b/_posts/2017-07-17-when-distributed-locks-might-be-helpful-in-ruby-on-rails-application.md index 2b3cd1a9..e26189f9 100644 --- a/_posts/2017-07-17-when-distributed-locks-might-be-helpful-in-ruby-on-rails-application.md +++ b/_posts/2017-07-17-when-distributed-locks-might-be-helpful-in-ruby-on-rails-application.md @@ -49,7 +49,7 @@ preload_app true before_fork do |server, worker| Signal.trap 'TERM' do - puts 'Unicorn master intercepting TERM and sending myself QUIT instead' + puts 'Unicorn main worker intercepting TERM and sending myself QUIT instead' Process.kill 'QUIT', Process.pid end @@ -59,7 +59,7 @@ end after_fork do |server, worker| Signal.trap 'TERM' do - puts 'Unicorn worker intercepting TERM and doing nothing. Wait for master to send QUIT' + puts 'Unicorn worker intercepting TERM and doing nothing. Wait for main worker to send QUIT' end defined?(ActiveRecord::Base) and diff --git a/_posts/2018-04-28-how-to-export-test-suite-timing-data-from-knapsack-pro-api.md b/_posts/2018-04-28-how-to-export-test-suite-timing-data-from-knapsack-pro-api.md index 9c803c9e..4143285f 100644 --- a/_posts/2018-04-28-how-to-export-test-suite-timing-data-from-knapsack-pro-api.md +++ b/_posts/2018-04-28-how-to-export-test-suite-timing-data-from-knapsack-pro-api.md @@ -46,7 +46,7 @@ You will get a response from API with the list of CI builds. { "id": "651efcce-cc5f-4cfc-b8fa-f49b4e5fb4af", "commit_hash": "347f33f598e5c66727e36b6f0c13b034f6a057f0", - "branch": "master", + "branch": "main", "node_total": 3, "created_at": "2018-04-21T10:57:42.439Z", "updated_at": "2018-04-21T10:57:54.989Z" @@ -54,7 +54,7 @@ You will get a response from API with the list of CI builds. { "id": "ba2190af-1bb1-4e3a-8ce1-37303549a4c3", "commit_hash": "347f33f598e5c66727e36b6f0c13b034f6a057f0", - "branch": "master", + "branch": "main", "node_total": 2, "created_at": "2018-04-02T10:00:44.741Z", "updated_at": "2018-04-02T10:00:44.763Z" @@ -75,7 +75,7 @@ You can use optional query params like `commit_hash`, `branch`, `node_total` to {% highlight plain %} curl -X GET \ - https://api.knapsackpro.com/v1/builds?page=1&branch=master&node_total=2&commit_hash=d1acb81ac1bead703eb6de64d1af24104d5d4b2c \ + https://api.knapsackpro.com/v1/builds?page=1&branch=main&node_total=2&commit_hash=d1acb81ac1bead703eb6de64d1af24104d5d4b2c \ -H 'cache-control: no-cache' \ -H 'KNAPSACK-PRO-TEST-SUITE-TOKEN: e5311882cbba506223ee8036fa68dc13' {% endhighlight %} @@ -100,7 +100,7 @@ For instance, you can get a response from Knapsack Pro API: { "id": "651efcce-cc5f-4cfc-b8fa-f49b4e5fb4af", "commit_hash": "347f33f598e5c66727e36b6f0c13b034f6a057f0", - "branch": "master", + "branch": "main", "node_total": 2, "created_at": "2018-04-02T10:00:44.741Z", "updated_at": "2018-04-02T10:00:44.763Z", diff --git a/_posts/2019-03-16-run-parallel-jobs-on-semaphore-ci-2-0-to-get-faster-ci-build-time.md b/_posts/2019-03-16-run-parallel-jobs-on-semaphore-ci-2-0-to-get-faster-ci-build-time.md index 2594d33f..3e5bc4fc 100644 --- a/_posts/2019-03-16-run-parallel-jobs-on-semaphore-ci-2-0-to-get-faster-ci-build-time.md +++ b/_posts/2019-03-16-run-parallel-jobs-on-semaphore-ci-2-0-to-get-faster-ci-build-time.md @@ -77,7 +77,7 @@ blocks: - checkout # Restore dependencies from cache. # Read about caching: https://docs.semaphoreci.com/article/54-toolbox-reference#cache - - cache restore gems-$SEMAPHORE_GIT_BRANCH-$(checksum Gemfile.lock),gems-$SEMAPHORE_GIT_BRANCH-,gems-master- + - cache restore gems-$SEMAPHORE_GIT_BRANCH-$(checksum Gemfile.lock),gems-$SEMAPHORE_GIT_BRANCH-,gems-main- # Set Ruby version: - sem-version ruby 2.6.1 - bundle install --jobs=4 --retry=3 --path vendor/bundle @@ -102,7 +102,7 @@ blocks: prologue: commands: - checkout - - cache restore gems-$SEMAPHORE_GIT_BRANCH-$(checksum Gemfile.lock),gems-$SEMAPHORE_GIT_BRANCH-,gems-master- + - cache restore gems-$SEMAPHORE_GIT_BRANCH-$(checksum Gemfile.lock),gems-$SEMAPHORE_GIT_BRANCH-,gems-main- # Start Postgres database service. # See https://docs.semaphoreci.com/article/54-toolbox-reference#sem-service - sem-service start postgres diff --git a/_posts/2019-09-16-how-to-run-rspec-on-github-actions-for-ruby-on-rails-app-using-parallel-jobs.md b/_posts/2019-09-16-how-to-run-rspec-on-github-actions-for-ruby-on-rails-app-using-parallel-jobs.md index a6a2eb8f..acaf5c93 100644 --- a/_posts/2019-09-16-how-to-run-rspec-on-github-actions-for-ruby-on-rails-app-using-parallel-jobs.md +++ b/_posts/2019-09-16-how-to-run-rspec-on-github-actions-for-ruby-on-rails-app-using-parallel-jobs.md @@ -26,7 +26,7 @@ In our case Rails application has Postgres database so you need to set up servic {% highlight yaml %} # If you need DB like PostgreSQL then define service below. # Example for Redis can be found here: -# https://github.com/actions/example-services/tree/master/.github/workflows +# https://github.com/actions/example-services/tree/main/.github/workflows services: postgres: image: postgres:10.8 diff --git a/_posts/2020-03-05-how-to-merge-cypress-test-reports-generated-by-mochawesome-on-github-actions.md b/_posts/2020-03-05-how-to-merge-cypress-test-reports-generated-by-mochawesome-on-github-actions.md index 4489842e..0bd9c082 100644 --- a/_posts/2020-03-05-how-to-merge-cypress-test-reports-generated-by-mochawesome-on-github-actions.md +++ b/_posts/2020-03-05-how-to-merge-cypress-test-reports-generated-by-mochawesome-on-github-actions.md @@ -73,7 +73,7 @@ Now we can run `knapsack-pro-cypress` as usual: run: knapsack-pro-cypress - name: Upload E2E test reports if: always() - uses: actions/upload-artifact@master + uses: actions/upload-artifact@v4 with: name: test-reports-${{ env.KNAPSACK_PRO_CI_NODE_INDEX }} path: mochawesome-report @@ -105,22 +105,22 @@ Now we need to download all our test artifacts, which were uploaded as `test-rep - name: Create reports directory run: mkdir reports - name: Download test-reports-0 - uses: actions/download-artifact@master + uses: actions/download-artifact@v4 with: name: test-reports-0 path: reports/0 - name: Download test-reports-1 - uses: actions/download-artifact@master + uses: actions/download-artifact@v4 with: name: test-reports-1 path: reports/1 - name: Download test-reports-2 - uses: actions/download-artifact@master + uses: actions/download-artifact@v4 with: name: test-reports-2 path: reports/2 - name: Download test-reports-3 - uses: actions/download-artifact@master + uses: actions/download-artifact@v4 with: name: test-reports-3 path: reports/3 @@ -221,7 +221,7 @@ Now we upload this report: {% highlight yml %} - name: Upload report - uses: actions/upload-artifact@master + uses: actions/upload-artifact@v4 with: name: E2E Test Reports path: report/ diff --git a/_posts/2020-06-13-how-to-run-slow-rspec-files-on-github-actions-with-parallel-jobs-by-doing-an-auto-split-of-the-spec-file-by-test-examples.md b/_posts/2020-06-13-how-to-run-slow-rspec-files-on-github-actions-with-parallel-jobs-by-doing-an-auto-split-of-the-spec-file-by-test-examples.md index 2df4255c..4b78b5b0 100644 --- a/_posts/2020-06-13-how-to-run-slow-rspec-files-on-github-actions-with-parallel-jobs-by-doing-an-auto-split-of-the-spec-file-by-test-examples.md +++ b/_posts/2020-06-13-how-to-run-slow-rspec-files-on-github-actions-with-parallel-jobs-by-doing-an-auto-split-of-the-spec-file-by-test-examples.md @@ -46,7 +46,7 @@ jobs: runs-on: ubuntu-latest # If you need DB like PostgreSQL, Redis then define service below. - # https://github.com/actions/example-services/tree/master/.github/workflows + # https://github.com/actions/example-services/tree/main/.github/workflows services: postgres: image: postgres:10.8 diff --git a/_posts/2021-02-18-how-to-build-knapsack-pro-api-client-from-scratch-in-any-programming-language.md b/_posts/2021-02-18-how-to-build-knapsack-pro-api-client-from-scratch-in-any-programming-language.md index 817eb417..c02f43dd 100644 --- a/_posts/2021-02-18-how-to-build-knapsack-pro-api-client-from-scratch-in-any-programming-language.md +++ b/_posts/2021-02-18-how-to-build-knapsack-pro-api-client-from-scratch-in-any-programming-language.md @@ -190,7 +190,7 @@ The first CI node sends the below request. Its purpose is to attempt to connect "attempt_connect_to_queue": true, "fixed_queue_split": false, "commit_hash": "6e3396177d9f8ca87e2b93b4b0a25babd09d574d", - "branch": "master", + "branch": "main", "node_total": "2", "node_index": "0", "node_build_id": "1234", @@ -233,7 +233,7 @@ You need to make a second request. This time, it should contain a list of test f "attempt_connect_to_queue": false, "fixed_queue_split": false, "commit_hash": "6e3396177d9f8ca87e2b93b4b0a25babd09d574d", - "branch": "master", + "branch": "main", "node_total": "2", "node_index": "0", "node_build_id": "1234", @@ -295,7 +295,7 @@ After you execute the test files, you should ask the API for another set of test "attempt_connect_to_queue": false, "fixed_queue_split": false, "commit_hash": "6e3396177d9f8ca87e2b93b4b0a25babd09d574d", - "branch": "master", + "branch": "main", "node_total": "2", "node_index": "0", "node_build_id": "1234", diff --git a/_posts/2021-03-03-cucumber-bdd-testing-using-github-actions-parallel-jobs-to-run-tests-quicker.md b/_posts/2021-03-03-cucumber-bdd-testing-using-github-actions-parallel-jobs-to-run-tests-quicker.md index c85b2884..651ffd8d 100644 --- a/_posts/2021-03-03-cucumber-bdd-testing-using-github-actions-parallel-jobs-to-run-tests-quicker.md +++ b/_posts/2021-03-03-cucumber-bdd-testing-using-github-actions-parallel-jobs-to-run-tests-quicker.md @@ -54,7 +54,7 @@ jobs: runs-on: ubuntu-latest # If you need DB like PostgreSQL, Redis then define service below. - # https://github.com/actions/example-services/tree/master/.github/workflows + # https://github.com/actions/example-services/tree/main/.github/workflows services: postgres: image: postgres:10.8 diff --git a/_posts/2021-04-04-run-minitest-on-github-actions-with-parallel-jobs-using-build-matrix.md b/_posts/2021-04-04-run-minitest-on-github-actions-with-parallel-jobs-using-build-matrix.md index 59878a50..ed3d8caa 100644 --- a/_posts/2021-04-04-run-minitest-on-github-actions-with-parallel-jobs-using-build-matrix.md +++ b/_posts/2021-04-04-run-minitest-on-github-actions-with-parallel-jobs-using-build-matrix.md @@ -47,7 +47,7 @@ jobs: runs-on: ubuntu-latest # If you need DB like PostgreSQL, Redis then define service below. - # https://github.com/actions/example-services/tree/master/.github/workflows + # https://github.com/actions/example-services/tree/main/.github/workflows services: postgres: image: postgres:10.8 diff --git a/_posts/2021-04-08-how-to-run-ruby-on-rails-tests-on-github-actions-using-rspec.md b/_posts/2021-04-08-how-to-run-ruby-on-rails-tests-on-github-actions-using-rspec.md index 9f7b9851..5c3912d0 100644 --- a/_posts/2021-04-08-how-to-run-ruby-on-rails-tests-on-github-actions-using-rspec.md +++ b/_posts/2021-04-08-how-to-run-ruby-on-rails-tests-on-github-actions-using-rspec.md @@ -45,7 +45,7 @@ In the config below, we also pass the settings for doing a health check to ensur {% highlight yml %} # If you need DB like PostgreSQL, Redis then define service below. -# https://github.com/actions/example-services/tree/master/.github/workflows +# https://github.com/actions/example-services/tree/main/.github/workflows services: postgres: @@ -119,7 +119,7 @@ jobs: runs-on: ubuntu-latest # If you need DB like PostgreSQL, Redis then define service below. - # https://github.com/actions/example-services/tree/master/.github/workflows + # https://github.com/actions/example-services/tree/main/.github/workflows services: postgres: image: postgres:10.8 diff --git a/docusaurus/docs/knapsack_pro-ruby/guide/index.mdx b/docusaurus/docs/knapsack_pro-ruby/guide/index.mdx index 7abb3358..b3bbb341 100644 --- a/docusaurus/docs/knapsack_pro-ruby/guide/index.mdx +++ b/docusaurus/docs/knapsack_pro-ruby/guide/index.mdx @@ -635,7 +635,7 @@ jobs: runs-on: ubuntu-latest # If you need a DB, then define it in the service below. - # https://github.com/actions/example-services/tree/master/.github/workflows + # https://github.com/actions/example-services/tree/main/.github/workflows services: postgres: image: postgres:10.8 @@ -926,7 +926,7 @@ blocks: - name: bundle commands: - checkout - - cache restore gems-$SEMAPHORE_GIT_BRANCH-$(checksum Gemfile.lock),gems-$SEMAPHORE_GIT_BRANCH-,gems-master- + - cache restore gems-$SEMAPHORE_GIT_BRANCH-$(checksum Gemfile.lock),gems-$SEMAPHORE_GIT_BRANCH-,gems-main- - sem-version ruby 2.6.1 - bundle install --jobs=4 --retry=3 --path vendor/bundle - cache store gems-$SEMAPHORE_GIT_BRANCH-$(checksum Gemfile.lock) vendor/bundle @@ -950,7 +950,7 @@ blocks: prologue: commands: - checkout - - cache restore gems-$SEMAPHORE_GIT_BRANCH-$(checksum Gemfile.lock),gems-$SEMAPHORE_GIT_BRANCH-,gems-master- + - cache restore gems-$SEMAPHORE_GIT_BRANCH-$(checksum Gemfile.lock),gems-$SEMAPHORE_GIT_BRANCH-,gems-main- - sem-service start postgres - sem-version ruby 2.6.1 - bundle install --jobs=4 --retry=3 --path vendor/bundle diff --git a/docusaurus/docs/ruby/cookbook.md b/docusaurus/docs/ruby/cookbook.md index d1eb3aec..b0afb536 100644 --- a/docusaurus/docs/ruby/cookbook.md +++ b/docusaurus/docs/ruby/cookbook.md @@ -46,7 +46,7 @@ For example, you could decide to run Knapsack Pro on all the CI nodes but the la KNAPSACK_PRO_CI_NODE_TOTAL=$((MY_CI_NODE_TOTAL-1)) bundle exec rake knapsack_pro:queue:rspec ``` -To find out which environment variable to use in place of `MY_CI_NODE_TOTAL`, take a look at what Knapsack Pro uses as `node_total` for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci) (e.g., for CircleCI it would be [`CIRCLE_NODE_TOTAL`](https://github.com/KnapsackPro/knapsack_pro-ruby/blob/master/lib/knapsack_pro/config/ci/circle.rb#L6)) +To find out which environment variable to use in place of `MY_CI_NODE_TOTAL`, take a look at what Knapsack Pro uses as `node_total` for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci) (e.g., for CircleCI it would be [`CIRCLE_NODE_TOTAL`](https://github.com/KnapsackPro/knapsack_pro-ruby/blob/main/lib/knapsack_pro/config/ci/circle.rb#L6)) ## Fail the CI build if one of the test files exceeds a certain time limit diff --git a/docusaurus/docs/ruby/encryption.mdx b/docusaurus/docs/ruby/encryption.mdx index 8ddd8592..463448fd 100644 --- a/docusaurus/docs/ruby/encryption.mdx +++ b/docusaurus/docs/ruby/encryption.mdx @@ -48,7 +48,7 @@ Also, note that the following branch names won't be encrypted to allow the Knaps - `dev` - `staging` - `production` -- [full list](https://github.com/KnapsackPro/knapsack_pro-ruby/blob/master/lib/knapsack_pro/crypto/branch_encryptor.rb) of non-encryptable branches +- [full list](https://github.com/KnapsackPro/knapsack_pro-ruby/blob/main/lib/knapsack_pro/crypto/branch_encryptor.rb) of non-encryptable branches ## Debug test file names diff --git a/docusaurus/docs/ruby/reference.md b/docusaurus/docs/ruby/reference.md index d54da247..239c9041 100644 --- a/docusaurus/docs/ruby/reference.md +++ b/docusaurus/docs/ruby/reference.md @@ -37,7 +37,7 @@ Git branch under test. You don't need to set it if either: -- Your CI is one of the [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci) +- Your CI is one of the [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci) - You are using `KNAPSACK_PRO_REPOSITORY_ADAPTER=git` and `KNAPSACK_PRO_PROJECT_DIR` In some cases, particularly for pull request merge commits or if the CI provider checks out a specific git commit during the build process, Git might only expose `HEAD` instead of the actual branch name. @@ -54,7 +54,7 @@ Available: `false` | `true` Unique ID that identifies a CI build. It must be the same for all the parallel CI nodes. -Default: Knapsack Pro will take it from the CI environment (see [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci)) +Default: Knapsack Pro will take it from the CI environment (see [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci)) If your CI is not supported, you may generate a build ID with `KNAPSACK_PRO_CI_NODE_BUILD_ID=$(openssl rand -base64 32)` and make it available to all parallel nodes. @@ -62,7 +62,7 @@ If your CI is not supported, you may generate a build ID with `KNAPSACK_PRO_CI_N Index of current CI node (first should be 0, second should be 1, etc.). -Default: Knapsack Pro will take it from the CI environment (see [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci)) +Default: Knapsack Pro will take it from the CI environment (see [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci)) If your CI is not supported, you need to set it manually. @@ -90,7 +90,7 @@ Available: Total number of parallel CI nodes. -Default: Knapsack Pro will take it from the CI environment (see [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci)) +Default: Knapsack Pro will take it from the CI environment (see [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci)) If your CI is not supported, you need to set it manually. @@ -100,7 +100,7 @@ Hash of the commit under test. You don't need to set it if either: -- Your CI is one of the [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci) +- Your CI is one of the [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci) - You are using `KNAPSACK_PRO_REPOSITORY_ADAPTER=git` and `KNAPSACK_PRO_PROJECT_DIR` ## `KNAPSACK_PRO_CUCUMBER_QUEUE_PREFIX` (Cucumber, Queue Mode) @@ -139,11 +139,11 @@ Default: `1` Dynamic or fixed tests split when retrying a CI build. -Default: automagically set to the correct value for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci) +Default: automagically set to the correct value for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci) Available: -- `false`: generate a new split when `KNAPSACK_PRO_CI_NODE_BUILD_ID` changes (see what Knapsack Pro uses as `node_build_id` for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci)) +- `false`: generate a new split when `KNAPSACK_PRO_CI_NODE_BUILD_ID` changes (see what Knapsack Pro uses as `node_build_id` for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci)) - `true`: if the triplet `(branch name, commit hash, number of nodes)` was already split in a previous build use the same split, otherwise generate a new split Recommended: @@ -160,7 +160,7 @@ Default: `true` Available: -- `false`: generate a new split when `KNAPSACK_PRO_CI_NODE_BUILD_ID` changes (see what Knapsack Pro uses as `node_build_id` for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci)) +- `false`: generate a new split when `KNAPSACK_PRO_CI_NODE_BUILD_ID` changes (see what Knapsack Pro uses as `node_build_id` for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci)) - `true`: if the triplet `(branch name, commit hash, number of nodes)` was already split in a previous build use the same split, otherwise generate a new split Recommended: @@ -255,7 +255,7 @@ Default: unset Available: -- unset: Knapsack Pro will take `KNAPSACK_PRO_BRANCH` and `KNAPSACK_PRO_COMMIT_HASH` from the CI environment (see [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci)) +- unset: Knapsack Pro will take `KNAPSACK_PRO_BRANCH` and `KNAPSACK_PRO_COMMIT_HASH` from the CI environment (see [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci)) - `git` (requires `KNAPSACK_PRO_PROJECT_DIR`): Knapsack Pro will set `KNAPSACK_PRO_BRANCH` and `KNAPSACK_PRO_COMMIT_HASH` using git on your CI ## `KNAPSACK_PRO_SLOW_TEST_FILE_PATTERN` (Internal, RSpec) @@ -495,7 +495,7 @@ A user name that started the CI build. It is usually the same person that made t You don't need to set it if: -- Your CI is one of the [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci), and we can read the user seat for the given CI provider. +- Your CI is one of the [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci), and we can read the user seat for the given CI provider. Examples: diff --git a/docusaurus/docs/ruby/rspec.mdx b/docusaurus/docs/ruby/rspec.mdx index 6708254b..4d4c4c16 100644 --- a/docusaurus/docs/ruby/rspec.mdx +++ b/docusaurus/docs/ruby/rspec.mdx @@ -301,7 +301,7 @@ The `.rspec` file is ignored in Queue Mode because `knapsack_pro` needs to pass ### Something is wrong with my custom formatter -Please ensure the `knapsack_pro` gem is updated to [version 7.0](https://github.com/KnapsackPro/knapsack_pro-ruby/blob/master/CHANGELOG.md#700) or higher. +Please ensure the `knapsack_pro` gem is updated to [version 7.0](https://github.com/KnapsackPro/knapsack_pro-ruby/blob/main/CHANGELOG.md#700) or higher.
For legacy versions of `knapsack_pro` older than 7.0, please click here. @@ -311,7 +311,7 @@ Please ensure the `knapsack_pro` gem is updated to [version 7.0](https://github. ### I see the summary of failed/pending tests multiple times in Queue Mode -Please ensure the `knapsack_pro` gem is updated to [version 7.0](https://github.com/KnapsackPro/knapsack_pro-ruby/blob/master/CHANGELOG.md#700) or higher. +Please ensure the `knapsack_pro` gem is updated to [version 7.0](https://github.com/KnapsackPro/knapsack_pro-ruby/blob/main/CHANGELOG.md#700) or higher.
For legacy versions of `knapsack_pro` older than 7.0, please click here. diff --git a/docusaurus/docs/ruby/troubleshooting.mdx b/docusaurus/docs/ruby/troubleshooting.mdx index 81d5473e..0c05d953 100644 --- a/docusaurus/docs/ruby/troubleshooting.mdx +++ b/docusaurus/docs/ruby/troubleshooting.mdx @@ -21,7 +21,7 @@ KNAPSACK_PRO_CI_NODE_BUILD_ID=MY_BUILD_ID \ bundle exec rake "knapsack_pro:rspec[--seed MY_SEED]" ``` -`KNAPSACK_PRO_CI_NODE_BUILD_ID` must be the same as the CI build you are trying to reproduce (if it helps, take a look at what Knapsack Pro uses as `node_build_id` for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci)). +`KNAPSACK_PRO_CI_NODE_BUILD_ID` must be the same as the CI build you are trying to reproduce (if it helps, take a look at what Knapsack Pro uses as `node_build_id` for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci)). You can also run the same subset of tests without Knapsack Pro: in the logs, find the command that Knapsack Pro used to invoke the test runner: @@ -44,7 +44,7 @@ KNAPSACK_PRO_FIXED_QUEUE_SPLIT=true \ bundle exec rake "knapsack_pro:queue:rspec[--seed MY_SEED]" ``` -`KNAPSACK_PRO_CI_NODE_BUILD_ID` must be the same as the CI build you are trying to reproduce (if it helps, take a look at what Knapsack Pro uses as `node_build_id` for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci)). +`KNAPSACK_PRO_CI_NODE_BUILD_ID` must be the same as the CI build you are trying to reproduce (if it helps, take a look at what Knapsack Pro uses as `node_build_id` for your [CI provider](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci)). You can also run the same subset of tests without Knapsack Pro: in the logs, find the command that Knapsack Pro used to invoke the test runner. @@ -278,7 +278,7 @@ fi ## Error `commit_hash` parameter is required -Knapsack Pro takes `KNAPSACK_PRO_COMMIT_HASH` and `KNAPSACK_PRO_BRANCH` from the CI environment (see [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/master/lib/knapsack_pro/config/ci)). If your CI is not supported you may see the following error: +Knapsack Pro takes `KNAPSACK_PRO_COMMIT_HASH` and `KNAPSACK_PRO_BRANCH` from the CI environment (see [supported CIs](https://github.com/KnapsackPro/knapsack_pro-ruby/tree/main/lib/knapsack_pro/config/ci)). If your CI is not supported you may see the following error: ```bash ERROR -- : [knapsack_pro] {"errors"=>[{"commit_hash"=>["parameter is required"]}]} diff --git a/docusaurus/sidebars.ts b/docusaurus/sidebars.ts index 647bd59d..7c0c8c68 100644 --- a/docusaurus/sidebars.ts +++ b/docusaurus/sidebars.ts @@ -149,7 +149,7 @@ const sidebars: SidebarsConfig = { { type: "link", label: "Changelog", - href: "https://github.com/KnapsackPro/knapsack_pro-ruby/blob/master/CHANGELOG.md#change-log", + href: "https://github.com/KnapsackPro/knapsack_pro-ruby/blob/main/CHANGELOG.md#change-log", }, ], },