Last Updated Mar 19, 2019 — Continuous Testing Expert


Jenkins is an open source Java software system designed to aid in the continuous software integration process. It is a server-based system that runs in servlet containers such as Apache Tomcat. Jenkins supports version control tools (for example – Git) and can execute your projects based on Apache Ant, Apache Maven, and sbt as well as arbitrary shell/Windows batch scripts and commands. During the development of large systems, there is a need for a continuous process of deployment and testing new versions of your product. To solve this problem, we will use the Jenkins SeleniumPipeline.

Jenkins Selenium Pipeline is a suite of plugins that support continuous delivery integration into Jenkins. In other words, it is a script that has several jobs in it and can be executed each time a certain condition is met. Let’s have a look at an example of working with Pipeline. To see more Continuous Testing Integrations, look here.

Our task is to create a Pipeline, which will be automatically launched with each push to our Maven public test repository. The repository will store a Maven project with a UI autotest, written using Selenium Webdriver.

Our Jenkins Pipeline will receive code changes, build a project, and run a simple autotest.

In steps:

1) Download Jenkins.

2) Install with the recommended parameters following the installer. (Important note: it is recommended to install Jenkins on a separate machine with Internet access, it is necessary to connect your instance with the repository. However, for the demonstration, we can (and will in this article) use a local Jenkins project with access through the Ngrok tool).

3) When the installation is complete, click on the “create new jobs” button.

welcome - jenkins pipeline

4) Then, select the Pipeline section and enter the name of your job. Click OK.

item name - jenkins pipeline

5) After that, go to the Pipeline section, and set the following parameters:

a) Definition = “pipeline script from SCM”

build triggers - jenkins pipeline

b) SCM = “Git”

build triggers - jenkins pipeline

6) Set a repository. Here the Script Path field defaults to “Jenkinsfile” – this is the name of the file-script, which contains a description of all the tasks that our Jenkins Pipeline will perform. This file should be in the root of the repository by default. We’ll get back to creating and configuring Jenkinsfile later, so now we will prepare a repository and a project of our Selenium test. For now, just click the Save button.

pipeline - jenkins pipeline

7) The script of our autotest will visit the page and check the title of this page, and then we will see “TEST PASSED” or “TEST FAILED” messages as a result. So, we will use Chromedriver and IntelliJ IDEA IDE, please download and install them if needed.

8) Create a standard Maven project in your IDE, and place the chromedriver.exe where your Jenkins Selenium instance is installed. In my case, click here to look at the code.

  [java] package com.test; import org.openqa.selenium.WebDriver; import; public class Selenium { public static void main(String[] args) { System.setProperty(“”,”F:\Jenkins\workspace\chromedriver.exe”); // <– Change this path WebDriver driver = new ChromeDriver(); String baseUrl = “”; String expectedTitle = “Free trial”; String actualTitle = “”; driver.get(baseUrl); actualTitle = driver.getTitle(); if (actualTitle.contentEquals(expectedTitle)){ System.out.println(“TEST PASSED!”); } else { System.out.println(“TEST FAILED”); } driver.close(); } } [/java]

9) In order to make sure that our test works, we will launch it locally. Open the built-in terminal (you can find it in the lower right corner of the IDEA interface) and enter the following commands:

java - jenkins pipeline

a) mvn clean install – As a result of this command, a folder /target will be created, and in it a file com.test-1.0-SNAPSHOT.jar.

b) java -jar {path to local project}comtesttargetcom.test-1.0-SNAPSHOT.jar – this command will launch our test.

See the results in the screenshot:

java - jenkins pipeline

10) Now that our project is ready, we can put it in the root of our test repository. In the same place, we will create a Jenkinsfile. Like this:

selenium - jenkins pipeline

11) Now we can discuss the contents of our Jenkinsfile, the code of which can be viewed here.


a) node { } – some kind of wrapper for our script. Inside it, the script is divided into stages.

b) stage (‘SCM checkout’) – preparatory stage, during which we receive updates from our repository.

c) stage (‘Build’) – the main stage, during which Jenkins will perform the same steps that we performed locally from the console above.

d) dir (“comtest”) – works in a specific folder.

e) sh “mvn clean install” – executes shell commands.

12) At this step we can manually launch our Jenkins Pipeline, to make sure it works.

pipeline - jenkins pipeline

You can see the results of the work of the pipeline in the form of a solid text, or step by step.

“Console Output” option:

console - jenkins pipeline

“Pipeline steps” option:

steps - jenkins pipeline

But our goal is not just to make a Jenkins Pipeline for autotests, but also to make its launch automatic. Let’s do it.

13) Install the plugins for integration with the GitLab. To do this, go to the next section: Jenkins=>Manage Jenkins=>Manage Plugins

manage - jenkins pipeline

Then select the Available tab, and enter “gitlab” in the search field. Install the necessary plugins and restart Jenkins.

available - jenkins pipeline

14) When the update is done, we return to the configuring. Go to Jenkins=>Configure System.

a) Add Gitlab repository to the plugin:

Go to Jenkins=>Configure System

gitlab - jenkins pipeline

Note: For our purposes, it is necessary to use a public repository, so we shouldn’t specify any credentials.

b) Check if we have a valid Jenkins URL. If you installed your instance of Jenkins Pipeline on a separate machine, then this step should be skipped. If you used a local machine as I did, then you will see the inscription localhost in the “Jenkins URL” field.

location - jenkins pipeline

In this case, we need to get a URL, which can be accessed by GitLab via the Internet. As I said earlier, there is an easy way to do this – ngrok.

Following the simple instructions of this tool, get the URL on which our test Jenkins is located:

get the URL on which our test Jenkins is located

We will put this address in the field Jenkins URL, and save all the changes.

put this address in the field Jenkins URL

15) Now, go to the GitLab settings: GitLab=>project=>Settings=>Integrations. So we need to configure the Jenkins CI webhook. Click the next link:


The integration settings with Jenkins CI will look as follows or similar:

integration settings with Jenkins CI

16) Update the settings of our Jenkins Pipeline (pipeline_selenium1) to use a GitLab webhook.

Jenkins Pipeline (pipeline_selenium1) to use a GitLab webhook

17) That’s all! Now let’s push something to our repository, and see what happens in Jenkins.

pipeline selenium 1 - jenkins pipeline

Wrapping up the Jenkins pipeline launch

As you can see, we have an easy way to create the Jenkins Pipeline, which will run Selenium autotests without human intervention. The Pipeline also allows us to perform any preparatory actions automatically. To learn more about the Jenkinsfile syntax, you can follow the link of Pipeline Syntax (it can be seen on the last screenshot).

If this blog interested you, please visit Continuous Testing to see how to deliver flawless customer experiences with scalable web and mobile testing.

Are you ready to scale your enterprise?


What's New In The World of

June 18, 2024

How Continuous Testing Fosters Dev and Security Collaboration: The Fashionable Approach to Secure Development

Discover how continuous testing and app sec foster a collaborative SDLC, creating a complex labyrinth for attackers while empowering teams and reducing costs.

Learn More
May 10, 2024

BPCE Banking Group Streamlines Quality Assurance and Delivery Process with Continuous Testing

Explore how BPCE Banking Group revolutionized testing with Continuous Testing, driving efficiency and quality in banking innovation.

Learn More
April 22, 2024

The Bias in the Machine: Training Data Biases and Their Impact on AI Code Assistants’ Generated Code

Explore biases in AI training data impacting code generation and learn strategies to mitigate them for fairer AI development and software innovation.

Learn More