| 1 | = Travis CI = |
| 2 | |
| 3 | CLARIN uses [https://travis-ci.org Travis CI] for [https://en.wikipedia.org/wiki/Continuous_integration continuous integration] tasks for some of the [[GitHub]] hosted code projects. |
| 4 | |
| 5 | See [https://travis-ci.org/clarin-eric travis-ci.org/clarin-eric] for an up-to-date status overview. |
| 6 | |
| 7 | == Nexus deployment == |
| 8 | |
| 9 | A 'travis' user has been added to the user store of our [[Nexus]] instance for the deployment of Maven artifacts (snapshot or production). The password can be requested from [mailto:sysops@clarin.eu]. |
| 10 | |
| 11 | === Example === |
| 12 | An example of the usage of Travis for Maven artifact deployments can be found in the [https://github.com/clarin-eric/base_style base_style] project: |
| 13 | |
| 14 | Two environment variables `NEXUS_DEPLOY_USERNAME` and `NEXUS_DEPLOY_PASSWORD` are set in the [https://travis-ci.org/clarin-eric/base_style/settings settings] (requires authorisation). These are referenced in a [https://github.com/clarin-eric/base_style/blob/master/.maven-settings.xml custom Maven settings file], which gets used when executing a [https://github.com/clarin-eric/base_style/blob/master/src/main/script/maven-deploy.sh deployment script] triggered from the project's [https://github.com/clarin-eric/base_style/blob/master/.travis.yml Travis configuration] (notice the `--settings` option). |
| 15 | |
| 16 | '''Note''': a deployment script will generally not be required except for special cases such as this project in which multiple artifacts with separate classifiers are built. In more standard cases a call to `maven deploy [--settings ...]` should be sufficient. |