2020-11-30 11:59:53 +00:00
# Description
This document describes the continuous integration setup for `nim-waku` .
# Details
The CI setup exists on the Status.im Jenkins instance:
https://ci.status.im/job/nim-waku/
It currently consists four jobs:
* [manual ](https://ci.status.im/job/nim-waku/job/manual/ ) - For manually executing builds using parameters.
* [deploy-v1-test ](https://ci.status.im/job/nim-waku/job/deploy-v1-test/ ) - Builds every new commit in `master` and deploys to `wakuv1.test` fleet.
* [deploy-v2-test ](https://ci.status.im/job/nim-waku/job/deploy-v2-test/ ) - Builds every new commit in `master` and deploys to `wakuv2.test` fleet.
* [deploy-v2-prod ](https://ci.status.im/job/nim-waku/job/deploy-v2-prod/ ) - Currently has no automatic trigger, and deploys to `wakuv2.prod` fleet.
# Configuration
The main configuration file is [`Jenkinsfile` ](../../Jenkinsfile ) at the root of this repo.
Key part is the definition of four `parameters` :
* `MAKE_TARGET` - Which `Makefile` target is built.
* `IMAGE_TAG` - Tag of the Docker image to push.
* `IMAGE_NAME` - Name of the Docker image to push.
2022-05-17 19:11:07 +00:00
* `NIMFLAGS` - Nim compilation parameters.
2020-11-30 11:59:53 +00:00
The use of `?:` [Elvis operator ](http://groovy-lang.org/operators.html#_elvis_operator ) plays a key role in allowing parameters to be changed for each defined job in Jenkins without it being overridden by the `Jenkinsfile` defaults after every job run.
```groovy
defaultValue: params.IMAGE_TAG ?: 'deploy-v2-test',
```