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:
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:
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:
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:
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:
NB: “Post build task” is an optional “Post-build Action” available as a Jenkins plugin: “Hudson Post build task”.