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
Because we have services in multiple languages, we had to separate the pipelines per-language (each pipeline uses a language specific box (e.g. `node`, `golang`)). Another reason we had to do this is because Wercker isn't really set up for a multi-repo - it would work better if we had a separate repo for each component.
29
+
30
+
We have the following pipelines to run tests - these could be run in parallel after build pipeline completes.
31
+
32
+
-`test-node-services` - runs unit tests for all NodeJS services
33
+
-`test-go-services` - runs unit tests for all Go services
34
+
-`test-java-services` - runs unit tests for all Java services
35
+
36
+
The test pipelines don't require any additional environment variables.
37
+
38
+
### Deployments
39
+
40
+
There are two deployment (upgrade) pipelines defined in Wercker
41
+
42
+
- Test Deployment (`upgrade-test-deployment`)
43
+
- Production Deployment (`upgrade-production-deployment`)
44
+
45
+
Both deployment pipelines are equivalent, the difference is in the environment variables that are set on the pipelines. The variables define which cluster is used for deployment as well as the Helm release name.
46
+
47
+
| Environment variable name | Description | Example |
48
+
| --- | --- | --- |
49
+
| HELM_RELEASE_NAME | Helm release name to be upgraded |`mymushop`|
50
+
| HELM_TIMEOUT | Helm timeout value |`600`|
51
+
| KUBERNETES_SERVER | URL of the Kubernetes server |`https://mykubernetescluster.com:6443`|
52
+
| KUBERNETES_TOKEN | User token for the Kubernetes cluster (from `.kube/config`) |`eyJoZWFkZXIiOnsiQXV0a...`|
0 commit comments