Page tree
Skip to end of metadata
Go to start of metadata



Jenkins is a free and open source Continuous Integration server. It is usually installed locally which makes it easier to manage and monitor. It is robust, easy to use, and offers many helpful plugins for various purposes such as integrating with GitHub, injecting environment variables, building .NET projects and many more.

To use seetest.io with Jenkins, follow the instruction below:


1. Download and Install Jenkins

Download Jenkins

Install Jenkins

It is highly recommended that you install the suggested plugins. You will be prompted to install them the first time you access Jenkins after installation.



3. Configure Git Credentials

In order for Jenkins to be able to check out the source code from your Git Repository, you need to provide your Git Credentials. You will later choose these credentials when creating a new Jenkins Job.

From Jenkins main screen, go to CredentialsSystemGlobal credentials (unrestricted). Click on Add Credentials.





4. Create a new Jenkins Job

From Jenkins main screen, click on create new jobs. Name your project, choose Freestyle project and click OK.






5. Configure the Jenkins Job

Under the General Tab, check the box next to This project is parameterized, open the Add Parameter drop-down list and choose Password Parameter.

Name the parameter SEETEST_IO_ACCESS_KEY and give it the value of your seetest.io access key.

This will be added as an environment variable in build time. You can access this environment variable from your code and pass it as access key in the desired capabilities.





Under the Source Code Management tab, choose Git, paste the desired repository in the Repository URL field and choose your credentials that you setup in the step #3.





6. Configure Build Steps

In order for Jenkins to be able to trigger the build properly regardless of the programming language you are using, you will have to specify at least one build step.

Under the Build tab, click on Add build step.

The build step is different for each sample git repository that we provided. See below what build step needs to be specified for each git repository.



  • No labels