README.md in knapsack_pro-0.49.0 vs README.md in knapsack_pro-0.50.0
- old
+ new
@@ -95,10 +95,11 @@
- [Info for CircleCI users](#info-for-circleci-users)
- [Info for Travis users](#info-for-travis-users)
- [Info for semaphoreapp.com users](#info-for-semaphoreappcom-users)
- [Info for buildkite.com users](#info-for-buildkitecom-users)
- [Info for Gitlab CI users](#info-for-gitlab-ci-users)
+ - [Info for codeship.com users](#info-for-codeshipcom-users)
- [Info for snap-ci.com users](#info-for-snap-cicom-users)
- [Info for Jenkins users](#info-for-jenkins-users)
- [FAQ](#faq)
- [Common problems](#common-problems)
- [Why I see API error commit_hash parameter is required?](#why-i-see-api-error-commit_hash-parameter-is-required)
@@ -780,9 +781,41 @@
- bundle exec rake knapsack_pro:cucumber
- bundle exec rake knapsack_pro:queue:rspec
```
Remember to add API tokens like `KNAPSACK_PRO_TEST_SUITE_TOKEN_CUCUMBER` and `KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC` to [Secret Variables](https://gitlab.com/help/ci/variables/README.md#secret-variables) in `Gitlab CI Settings -> CI/CD Pipelines -> Secret Variables`.
+
+#### Info for codeship.com users
+
+Codeship does not provide parallel jobs environment variables so you will have to define `KNAPSACK_PRO_CI_NODE_TOTAL` and `KNAPSACK_PRO_CI_NODE_INDEX` for each [parallel test pipeline](https://documentation.codeship.com/basic/builds-and-configuration/parallel-tests/#using-parallel-test-pipelines). Below is an example for 2 parallel test pipelines.
+
+Configure test pipelines (1/2 used)
+
+```
+# first CI node running in parallel
+
+# Cucumber tests in Knapsack Pro Regular Mode (deterministic test suite split)
+KNAPSACK_PRO_CI_NODE_TOTAL=2 KNAPSACK_PRO_CI_NODE_INDEX=0 bundle exec rake knapsack_pro:cucumber
+
+# RSpec tests in Knapsack Pro Queue Mode (dynamic test suite split)
+# It will autobalance bulid because it is executed after Cucumber tests.
+KNAPSACK_PRO_CI_NODE_TOTAL=2 KNAPSACK_PRO_CI_NODE_INDEX=0 bundle exec rake knapsack_pro:queue:rspec
+```
+
+Configure test pipelines (2/2 used)
+
+```
+# second CI node running in parallel
+
+# Cucumber tests in Knapsack Pro Regular Mode (deterministic test suite split)
+KNAPSACK_PRO_CI_NODE_TOTAL=2 KNAPSACK_PRO_CI_NODE_INDEX=1 bundle exec rake knapsack_pro:cucumber
+
+# RSpec tests in Knapsack Pro Queue Mode (dynamic test suite split)
+# It will autobalance bulid because it is executed after Cucumber tests.
+KNAPSACK_PRO_CI_NODE_TOTAL=2 KNAPSACK_PRO_CI_NODE_INDEX=1 bundle exec rake knapsack_pro:queue:rspec
+```
+
+Remember to add API tokens like `KNAPSACK_PRO_TEST_SUITE_TOKEN_CUCUMBER` and `KNAPSACK_PRO_TEST_SUITE_TOKEN_RSPEC` to `Environment` page of your project settings in Codeship.
#### Info for snap-ci.com users
Knapsack Pro supports snap-ci.com ENVs `SNAP_WORKER_TOTAL` and `SNAP_WORKER_INDEX`. The only thing you need to do is to configure number of workers for your project in configuration settings in order to enable parallelism. Next thing is to set below commands to be executed in your stage: