Installing Jenkins

<< Click to Display Table of Contents >>

Navigation:  4. How to use Anatella? > 4.7. Batch Execution / Anatella command-line > 4.7.9. Running many Anatella graphs at regular interval > Using Jenkins with Anatella > Installing Jenkins




One pre-requisite to be able to run an Anatella graph inside Jenkins is to register your Anatella/TIMi licences as a “System-Wide” License: More precisely: You must follow the procedure given in section “7.4.2: Server-Wide Licence”.




Go the the URL: https://jenkins-ci.org/ and download the “Windows Native Package”:number1






There are several ways to install Jenkins under Windows. You should download a zip file that contains the “jenkins.msi” file. Try to avoid the installation system based on a WAR file.


Unzip the file “Jenkins-xxxx.zip” and run “jenkins.msi” to run the simple installation wizard: You should see:





After the installation wizard is completed, open inside a web browser the URL http://localhost:8080  (the installation wizard should already open automatically this webpage for you). After a few seconds, you should finally see:




By default, Jenkins installs itself as a standard windows service.

As usual with all Windows Services, you can start & stop the (“Jenkins”) service here:







The above window is used to manage the Windows Services that are always running in the background”. To get this window:

1.Open a run prompt: Press [WIN]+[R]

2.Run “services.msc”


Since Jenkins is a service, it means that (by default) your scheduled Anatella Graphs won’t run under your own MS-Windows account. More precisely, your graphs will execute (by default) under the “Local System Account”: It’s strongly advised to change that default behavior here: Open the window used to manage the MS-Windows Services (i.e. Open a run prompt: Press [WIN]+[R] and run “services.msc”) and then:




Running Jenkins under your own account usually solves many different problems. For example, if you forgot to change to your own account the account that executes Jenkins, you’ll most certainly experience the following difficulties/errors:

1.The “shared drives” (i.e. the network drives: Typically “Z:”) are not accessible to the “Local System Account”: You must execute Jenkins under you own account to have access to the “shared drives”.

2.If your Anatella Graph is using a Type-1 ODBC connection, make sure that this ODBC connection (i.e. the “ODBC DSN” or ODBC link) is inside the category “System DSN” (and not “User DSN”), otherwise the Graphs executed by Jenkins won’t have access to your (ODBC) connection: You’ll find more information about the difference between “System DSN” and “User DSN” inside the section about Type-1 ODBC connections (you won’t have any problem if you are using Type‑2 ODBC connections).

3.Many functionnalities inside the R or Python Engine are not working when executed under the “Local System Account” (although they are working ok when executed under your own personal account).

4.You must enter your Anatella Serial Number as a “System-Wide License” (otherwise the Jenkins user won’t have the required Serial Number to run Anatella). More precisely: You must follow the procedure given in section 7.4.2 to enter your Licence.



If the installation failed (i.e. you can’t see the Jenkins welcome webpage), you can get a description of the installation error inside the file named “jenkins.err.log” inside the Jenkins installation directory:





Here is an example of an installation failure (this is the content of the file “jenkins.err.log”):



 Nov 15, 2015 12:23:43 PM winstone.Logger logInternal
 INFO: Beginning extraction from war file
 Nov 15, 2015 12:23:44 PM org.eclipse.jetty.util.log.JavaUtilLog info
 INFO: jetty-winstone-2.8
 Nov 15, 2015 12:23:46 PM org.eclipse.jetty.util.log.JavaUtilLog info
 INFO: NO JSP Support for , did not find org.apache.jasper.servlet.JspServlet
 Nov 15, 2015 12:23:46 PM org.eclipse.jetty.util.log.JavaUtilLog warn
 WARNING: FAILED SelectChannelConnector@ java.net.BindExceptionnumber1: Address already in use: bind
 java.net.BindException: Address already in use: bind
    at sun.nio.ch.Net.bind0(Native Method)
    at sun.nio.ch.Net.bind(Unknown Source)



If you got a “java.net.BindException” (such as in the example here above)number1, it means that the default TCP/IP port that Jenkins is using (i.e. the port 8080) is already used by another application on your server. When this error occurs, you have 2 choices:

1.You can stop the other application (that is currently using port 8080): This is the preferred solution.

To help you find the application using the port 8080: open a “Windows Task Manager”, go to the “Performance” tab, and click on the “Resource Monitor” button (on the bottom of the window). Inside the “Resource Monitor”, go to the “Network panel”, open the “Listening port” section and search for the application using the port 8080:





2.You can start Jenkins on a different port (this is NOT the preferred solution):

For example, to run Jenkins on port 9090, open a command-shell and run:


 cd "C:\Program Files (x86)\Jenkins"
 java -jar jenkins.war --httpPort=9090



Then, you can open the URL http://localhost:9090/ inside your web browser.