You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2019-03-16-run-parallel-jobs-on-semaphore-ci-2-0-to-get-faster-ci-build-time.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Here you can find Semaphore CI 2.0 config for projects using:
31
31
32
32
`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.
33
33
34
-
- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC`. If you don't want to commit secrets in yml file then you can <ahref="https://docs.semaphoreci.com/article/66-environment-variables-and-secrets"target="_blank"rel="nofollow">follow this guide</a>.
34
+
- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC`. If you don't want to commit secrets in yml file then you can <ahref="https://docs.semaphoreci.com/using-semaphore/secrets"target="_blank"rel="nofollow">follow this guide</a>.
35
35
- 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.
36
36
37
37
Below you can find full Semaphore CI 2.0 config for Rails project.
@@ -135,7 +135,7 @@ blocks:
135
135
136
136
`@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.
137
137
138
-
- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_CYPRESS`. If you don't want to commit secrets in yml file then you can <ahref="https://docs.semaphoreci.com/article/66-environment-variables-and-secrets"target="_blank"rel="nofollow">follow this guide</a>.
138
+
- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_CYPRESS`. If you don't want to commit secrets in yml file then you can <ahref="https://docs.semaphoreci.com/using-semaphore/secrets"target="_blank"rel="nofollow">follow this guide</a>.
139
139
- 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.
140
140
141
141
Below you can find example part of Semaphore CI 2.0 config.
@@ -164,7 +164,7 @@ blocks:
164
164
165
165
`@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.
166
166
167
-
- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_JEST`. If you don't want to commit secrets in yml file then you can <ahref="https://docs.semaphoreci.com/article/66-environment-variables-and-secrets"target="_blank"rel="nofollow">follow this guide</a>.
167
+
- You need to set `KNAPSACK_PRO_TEST_SUITE_TOKEN_JEST`. If you don't want to commit secrets in yml file then you can <ahref="https://docs.semaphoreci.com/using-semaphore/secrets"target="_blank"rel="nofollow">follow this guide</a>.
168
168
- 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.
169
169
170
170
Below you can find example part of Semaphore CI 2.0 config.
0 commit comments