Jenkins is an open source tool written in Java which provides continuous integration services for software development.

What You Get

We install the latest stable version of Jenkins on your VPS instance. After configuration of basic script, we deliver it to you at which time it is ready to use. Additional configuration and customization would be required for a fully functional CI system

Price includes

  • Installation of Jenkins on a virtual private server at the cloud hosting provider of your choice (purchased separately)
  • DNS configuration to point your domain name to the new server
  • Training session

Domain name recommended. (more info)

Hosting fees separate. (more info)

Installation Price: $65.00 (One Time)

Add to Cart

This DevOps application is typically used in conjunction with Git. You can use GitHub or your own Git server (which we also provide (here)). Westlinks Online will install the base instance of Jenkins and, if wanted, a simple project. We are happy to consult with you how to best leverage this tool for your specific needs.

Installation Process

  • Create Server
  • Configure server
  • Install Jenkins
  • Configure Jenkins project (if desired)
  • Provide training with you to confirm system is properly working for you.

About Jenkins

From Wikipedia

Jenkins is an open source continuous integration tool written in Java. The project was forked from Hudson after a dispute with Oracle.

Jenkins provides continuous integration services for software development. It is a server-based system running in a servlet container such as Apache Tomcat. It supports SCM tools including AccuRev, CVS, Subversion, Git, Mercurial, Perforce, Clearcase and RTC, and can execute Apache Ant and Apache Maven based projects as well as arbitrary shell scripts and Windows batch commands. The primary developer of Jenkins is Kohsuke Kawaguchi. Released under the MIT License, Jenkins is free software.

Builds can be started by various means, including being triggered by commit in a version control system, by scheduling via a cron-like mechanism, by building when other builds have completed, and by requesting a specific build URL.


Jenkins was originally developed as the Hudson project. Hudson's creation started in summer of 2004 at Sun Microsystems. It was first released in in Feb. 2005.

Around 2007 Hudson became known as a better alternative to CruiseControl and other open-source build-servers. At the JavaOne conference in May 2008 the software won the Duke's Choice Award in the Developer Solutions category.

During November 2010, an issue arose in the Hudson community with respect to the infrastructure used, which grew to encompass questions over the stewardship and control by Oracle. Negotiations between the principal project contributors and Oracle took place, and although there were many areas of agreement a key sticking point was the trademarked name "Hudson", after Oracle claimed the right to the name and applied for a trademark in December 2010. As a result, on January 11, 2011, a call for votes was made to change the project name from "Hudson" to "Jenkins". The proposal was overwhelmingly approved by community vote on January 29, 2011, creating the Jenkins project.

On February 1, 2011, Oracle said that they intended to continue development of Hudson, and considered Jenkins a fork rather than a rename. Jenkins and Hudson therefore continue as two independent projects, each claiming the other is the fork. As of December 2013, the Jenkins organisation on GitHub had 567 project members and around 1,100 public repositories, compared with Hudson's 32 project members and 17 public repositories.

In 2011, creator Kohsuke Kawaguchi received a Google-O'Reilly Open Source Award for his work on the Hudson/Jenkins project. In 2014, Kawaguchi became the Chief Technology Officer for CloudBees.

On April 20, 2016 version 2 was released with the Pipeline plugin enabled by default. The plugin allows for writing build instructions in Apache Groovy.


Plugins have been released for Jenkins that extend its use to projects written in languages other than Java. Plugins are available for integrating Jenkins with most version control systems and big databases.

Many build tools are supported via their respective plugins. Plugins can also change the way Jenkins looks or add new functionality. Builds can generate test reports in various formats supported by plugins (JUnit support is currently bundled) and Jenkins can display the reports and generate trends and render them in the GUI.