The connector is compliant with both Jenkins 1.510, Jenkins 2 and Hudson 3.0.1 and with Polarion 2012, 2013, 2014, 2015 and 2016.
PJ main features:
- A Polarion workflow function to trigger a Jenkins job.
- A Jenkins/Hudson Post Build Task to notify Polarion about the job result.
- Automated Jenkins test results imported as Polarion Test Runs.
Use Cases
The connector is compliant both with Jenkins 1.510 and Hudson 3.0.1 and with Polarion 2012/2013/2014/2015.
PJ integrates Jenkins/Hudson and Polarion in two scenarios:
Jenkins is often used for continous integration, but you can integrate your build automation tool with Polarion without also doing CI.
In this scenario the Jenkins job is triggered by a workflow function provided by PJ.
The PJ plugin has the function to notify the calling workitem after the Jenkins job execution: the status of the workitem will be changed and its hyperlinks will be set in order to link the generated artifacts and reports.
PJ can additionally import the automated test results as a Polarion Test Run.
In this scenario the job is triggered by Jenkins itself in continuous integration or directly by a Jenkins user in the browser.
In both cases PJ can be used to create a new Polarion workitem and set its hyperlinks to link the generated artifacts and reports.
PJ can additionally import the automated tests results as a Polarion Test Run.