Differences

This shows you the differences between two versions of the page.

--- development:ohdsi_jenkins_ci_server [2014/12/23 20:26] – lee
+++ development:ohdsi_jenkins_ci_server [2015/03/16 06:31] (current) – [How to get access] lee
@@ Line 1: / Line 1: @@
-The OHDSI Jenkins CI Server User Interface is here: [[http://54.165.59.104:8080/]]
+==== How to get access ====
-Anyone can view the status of build jobs using the above URL without needing a Jenkins user account to log into the server.
+The OHDSI Jenkins CI Server User Interface is here: [[http://jenkins.ohdsi.org:8080/]]
-If you want to setup your own build jobs then please request an OHDSI Jenkins account by sending an email to <evans@ohdsi.org>
+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 request an OHDSI Jenkins account by sending an email to <[email protected]>
+==== 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 ====
 [[https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project|General Jenkins info on how to build a software project]]
-Maven is installed on the CI server and can be used by Jenkins build jobs (more info will be posted here in the new year on how to create a maven build job).  We will use the new OHDSI WebAPI project as an example of a maven build.
+==== Maven build jobs ====
+Maven is installed on the CI server and can be used by Jenkins build jobs.  More info will be posted here in the new year on how to create a maven build job, using the new OHDSI WebAPI project as an example.
+Jenkins build jobs can optionally be automatically triggered by a Github project using a Github webhook. e.g. when source is checked into a Github project.
+==== Automated builds using Github webhooks ====
+The Cyclops job on the OHDSI Jenkins server is an example of a job that is triggered from a webhook (in this case for the ODSI Cyclops Github project.  More information will be posted here in the new year on how to setup a Github OHDSI project webhook for the OHDSI Jenkins server.
-The github plugin is installed on Jenkins so a github project githook can automatically trigger a jenkins build when source is checked into github.   The Cyclops github project job currently configured on Jenkins is an example of a job that is triggered from a githook.  More information will be posted here with the necessary details to setup a github githook.
+You will need to work with the Github OHDSI project maintainer to configure a Github project webhook if you are not the project owner.