Start Jenkins jobs from Hiptest

You can start a Jenkins job directly from Hiptest. There is two pre-requisites to do so:

  • the Jenkins server must be accessible by Hiptest. If your server is hosted inside a private network, Hiptest on-premises is a solution.
  • you need an account on the Jenkins server that is able to start jobs

1 – Enabling Jenkins

Go to your project settings and look for the Jenkins settings panel. Enter the URL of the Jenkins server and save:


Several Jenkins servers may be added here. Feel free to assigned them identifiable names:


NB: The Delete Jenkins Server link won’t be available if the server is referenced in a test run.

Saving a Jenkins URL allows you to store the credentials used to connect to that Jenkins server. We strongly recommend you to use the API token instead of the password. To find it, login to Jenkins, open your profile and click on the “configure” link.

You will find a “API token” sub-section, click on the “Show API token” button and use the API token as the password in Hiptest:

Screen Shot 2016-05-09 at 16.52.58.png

Once the credentials have been saved, you can click on the “Test credentials” to ensure the connection between Hiptest and Jenkins is working as expected:

Screen Shot 2016-05-09 at 16.54.31

2 – Select the jobs to start

To be able to start a Jenkins job, you will need a test run from which the job is started. In the test run, you will see a “Jenkins” panel. It will list all jobs linked to this project:

Screen Shot 2016-05-09 at 17.01.49

Normally, you will not have any job linked to the test run for now, so let’s add one. Click on the “Add new job” button:


Click on the name of the job you want to link to this project and it will appear in the Jenkins panel:


Now click on the button “Run job ” to start it:


For parametrized jobs, after clicking on ‘Run Job’, a modal will appear with the Jenkins’ parameters pre-filled. You can check or modify them before to trigger the build:


Capture d_écran 2018-01-12 à 15.54.54

Note : Credentials, File and Custom parameters are not supported by Hiptest. If the job linked to your test-run contains some of them, a warning message will appear to notify that they will be ignored.

Refreshing job

If your job is modified in Jenkins (default value changes, adding/deleting parameters, …), you may refresh your linked job in Hiptest. There is nothing more simple !

Capture d_écran 2018-01-12 à 16.23.09

All you have to do is to click on the refresh button before filling your parameters and triggering your build.

That’s it, you Jenkins job is now started. You can link multiple jobs to a single test run.


3 – Going a bit further

If needed, you can get some extra data from Hiptest when starting the build. There are three available parameters:

  •  test_run_data: this is the link to the XML export of the test run from which the job was started. This can be used for example to filter the tests you want to run.
  • project_token: this is the project secret token. You can use it to push the results of the execution back to Hiptest.
  • test_run_id: is the ID of the test run used to start the build. Again, it can be used to pushed the results back to Hiptest.

Here is an example of a post-build action that pushes the results back to Hiptest, based on those parameters:

Screen Shot 2016-05-09 at 17.12.13

NB: “Post build task” is an optional “Post-build Action” available as a Jenkins plugin: “Hudson Post build task”.

Download the ebook

This field is required

This field is required

Please enter a valid email address

Thank you, the ebook has been sent to your mailbox

Hiptest is FREE for open source projects

We actually utilize a number of open source components, which is why Hiptest service is free for any open source project. We are giving back to the community!

Your open source project must meet the following criteria to be approved:

  • Your project is licensed under a license approved by the Open Source Initiative
  • Your project source code is available for download
  • Your project has a publicly accessible website

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.