Jobs

Job in Allure TestOps is an entity that stores the link to a CI pipeline. The process of the test results upload is a job-run. All the parameters of a job-run are managed by Allure TestOps and CI plug-in (allurectl).

Jobs section of a project in Allure TestOps stores the information about all pipelines associated with current project and also the parameters/attributes you use in this pipelines to run your tests.

A job can be used to upload the test results and (optionally) to trigger the associated pipeline on CI server.

Managing jobs

Job actions

You can perform the following actions on a Job.

1. Start for the execution on CI side
   • Job must be allowed to run tests
   • Integration must be configured for CI server
2. Update job's parameters from CI server
3. Configure Job.
4. Delete Job.

Job configuration

To start using a Job for creating Launches and triggering CI pipelines form Allure TestOps UI, you need to configure such a Job:

1. Select correct CI server configured on Project level with correct access rights provided in CI.
2. Mark the Job as available for running tests on it.
3. Link the ENV variables received from the job to the global environment variables.
4. Submit the changes.

The configuration of the environment variables

The configuration of the environment variables can be omitted, but in this case, the defaults from the pipeline will be always used, so if you need to trigger a pipeline on an alternative branch or with alternative values of any variable, these must be explicitly added to the configuration parameters of a Job in Allure TestOps.

Update job from build server

When you click on the button Update job from build server, Allure TestOps will refresh the information about the pipeline. For some of the CI system it'll be possible to retrieve the default environment parameters and update the Job accordingly to the retrieved information. Some CI system do not allow retrieving this information and you need to enter the data manually and create the links to global Environment variables in Allure TestOps.

Running jobs

Clicking on the Ruin job button will trigger the execution of the associated pipeline, launch will be created and the data on created launch will be passed to the pipeline and this data will be used by a plug-in or allurectl.

This command will run full job by default, i.e. all the tests associated with this job will be added to new launch and Allure TestOps will create testplan.json with all the test IDs and full names and will provide this file to CI server for execution.

Once you've created a launch for your job, you need to proceed to Launches section to analyse the test results.