development:ohdsi_jenkins_ci_server
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
development:ohdsi_jenkins_ci_server [2015/03/08 22:13] lee |
development:ohdsi_jenkins_ci_server [2015/03/16 06:31] (current) lee [How to get access] |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| Anyone can view the status of the build jobs in Jenkins using the above URL without needing to log into the server. | Anyone can view the status of the build jobs in Jenkins using the above URL without needing to log into the server. | ||
| - | If you want to setup your own Jenkins build jobs then request an OHDSI Jenkins account by sending an email to <evans@ohdsi.org> | + | If you want to setup your own Jenkins build jobs request an OHDSI Jenkins account by sending an email to <evans@ohdsi.org> |
| + | |||
| + | ==== Build jobs running on the OHDSI Jenkins CI Server ==== | ||
| + | * WebAPI | ||
| + | * SqlRender | ||
| + | * AchillesWeb | ||
| + | * CIRCE | ||
| + | * HERMES | ||
| + | * Cyclops | ||
| + | |||
| + | Note. The WebAPI, AchillesWeb, CIRCE and HERMES Jenkins build jobs also auto-deploy the latest versions from the associated github master repos to the public OHDSI server. Therefore it is recommended that developers develop in feature branches and only push to the master branch when they are ready to deploy the code. | ||
| ==== General info on how to setup up a Jenkins build job ==== | ==== General info on how to setup up a Jenkins build job ==== | ||
development/ohdsi_jenkins_ci_server.1425852807.txt.gz · Last modified: 2015/03/08 22:13 by lee
Page Tools
