Skip to content

Commit

Permalink
Update 2019-03-16-run-parallel-jobs-on-semaphore-ci-2-0-to-get-faster…
Browse files Browse the repository at this point in the history
…-ci-build-time.md

fix broken links
  • Loading branch information
ArturT committed Dec 2, 2024
1 parent 3628976 commit 93a8161
Showing 1 changed file with 3 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Here you can find Semaphore CI 2.0 config for projects using:

`knapsack_pro` gem supports environment variables provided by Semaphore CI 2.0 to run your tests. You will have to define a few things in `.semaphore/semaphore.yml` config file.

- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC`. If you don't want to commit secrets in yml file then you can <a href="https://docs.semaphoreci.com/article/66-environment-variables-and-secrets" target="_blank" rel="nofollow">follow this guide</a>.
- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC`. If you don't want to commit secrets in yml file then you can <a href="https://docs.semaphoreci.com/using-semaphore/secrets" target="_blank" rel="nofollow">follow this guide</a>.
- You should create as many parallel jobs as you need with `parallelism` property. If your test suite is long you should use more parallel jobs.

Below you can find full Semaphore CI 2.0 config for Rails project.
Expand Down Expand Up @@ -135,7 +135,7 @@ blocks:

`@knapsack-pro/cypress` supports environment variables provided by Semaphore CI 2.0 to run your tests. You will have to define a few things in `.semaphore/semaphore.yml` config file.

- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_CYPRESS`. If you don't want to commit secrets in yml file then you can <a href="https://docs.semaphoreci.com/article/66-environment-variables-and-secrets" target="_blank" rel="nofollow">follow this guide</a>.
- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_CYPRESS`. If you don't want to commit secrets in yml file then you can <a href="https://docs.semaphoreci.com/using-semaphore/secrets" target="_blank" rel="nofollow">follow this guide</a>.
- You should create as many parallel jobs as you need with `parallelism` property. If your test suite is long you should use more parallel jobs.

Below you can find example part of Semaphore CI 2.0 config.
Expand Down Expand Up @@ -164,7 +164,7 @@ blocks:

`@knapsack-pro/jest` supports environment variables provided by Semaphore CI 2.0 to run your tests. You will have to define a few things in `.semaphore/semaphore.yml` config file.

- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_JEST`. If you don't want to commit secrets in yml file then you can <a href="https://docs.semaphoreci.com/article/66-environment-variables-and-secrets" target="_blank" rel="nofollow">follow this guide</a>.
- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_JEST`. If you don't want to commit secrets in yml file then you can <a href="https://docs.semaphoreci.com/using-semaphore/secrets" target="_blank" rel="nofollow">follow this guide</a>.
- You should create as many parallel jobs as you need with `parallelism` property. If your test suite is long you should use more parallel jobs.

Below you can find example part of Semaphore CI 2.0 config.
Expand Down

0 comments on commit 93a8161

Please sign in to comment.