Jenkins
  • Introduction
  • 1. Jenkins Basics
    • 1.1 Run Jenkins as-is
    • 1.2 Installation of Jenkins
    • 1.3 Installation of jenkins on Tomcat
  • 2. Jenkins Configurations
    • 2.1 Configure Jenkins Slave
    • 2.2 Configure SonarQube with Jenkins
    • 2.3 Configure SilkCentral with Jenkins
    • 2.4 Configure TestNG with Jenkins
  • 3. How to use Jenkins
    • 3.1 Create jobs
    • 3.2 Run jobs
    • 3.3 Run Single Job Parallely in Multiple slaves
  • 4. Jenkins Integrations
    • 4.1 Analysis with SonarQube using Jenkins
    • 4.2 SCTM Result Analysis with Jenkins
    • 4.3 TestNG Result Analysis with Jenkins
  • 5. Jenkins Advanced
    • 5.1Jenkins Challenges
Powered by GitBook
On this page

Was this helpful?

1. Jenkins Basics

PreviousIntroductionNext1.1 Run Jenkins as-is

Last updated 5 years ago

Was this helpful?

Jenkins is a self-contained, open source automation server which can be used to automate all sorts of tasks such as building, testing, and deploying software. Jenkins can be installed through native system packages, Docker, or even run standalone by any machine with the Java Runtime Environment installed.

Currently there are two flavours of Jenkins.

Jenkins Pipeline(One of the important feature) is a suite of plugins which supports implementing and integrating continuous delivery pipelines into Jenkins. Pipeline provides an extensible set of tools for modeling simple-to-complex delivery pipelines "as code".

Ais a text file that contains the definition of a Jenkins Pipeline and is checked into source control.This is the foundation of "Pipeline-as-Code"; treating the continuous delivery pipeline a part of the application to be version and reviewed like any other code. Creating aJenkinsfileprovides a number of immediate benefits:

  • Automatically create Pipelines for all Branches and Pull Requests

  • Code review/iteration on the Pipeline

  • Audit trail for the Pipeline

  • Single source of truth for the Pipeline, which can be viewed and edited by multiple members of the project.

While the syntax for defining a Pipeline, either in the web UI or with aJenkinsfile, is the same, it’s generally considered best practice to define the Pipeline in aJenkinsfileand check that in to source control.

Jenkins - Open Source Version
CloudBees Jenkins Enterprise Edition
Jenkinsfile