Associating Jenkins jobs using Manage jobs

You can link jobs to a product by adding one or more CloudBees CI or Jenkins jobs to a product. Linking the Jenkins jobs to the products surfaces Jenkins job information.

Once jobs are associated with a product, they inform the analytics. This screen lists all jobs associated with a product and lets you unlink or add additional ones.

You can link Jenkins jobs to products by using Manage jobs.

You can also filter any of the jobs associated with a product by keywords, last success, last failure, last duration, and status.

Figure 1. Manage jobs

Requirements

To use this screen, you must have:

Linking jobs with products

Linking Jenkins jobs allows you to add build and job information to products. Selecting a Jenkins job links the job with the chosen product. Jenkins controllers need to be connected before you can link jobs to products.

Each job can be linked to one or more products.

To link jobs:

  1. From Products, select a product.

  2. Select Manage jobs.

    • If this is the first time you are linking a job, select Link your first job.

    • Otherwise, select Link jobs.

  3. Select one or more check boxes to associate those jobs with the product.

  4. Select Save change.

Unlinking jobs

Unlinking a job from a product disassociates that data from the product. The job data remain available in CloudBees Engineering Efficiency.

To unlink one or more jobs from a product:

  1. From Products, select the product, and then select Manage jobs.

  2. Select the check box next to each job that you want to remove.

  3. Select Unlink selected jobs.

Deployment jobs

Of the work teams do, only a subset do the work of deploying to production. Identifying jobs as deployment jobs helps differentiate these jobs so they can be tracked separately for contributing to deployment-related metrics. This helps identify the jobs that are pushing code changes to production.

Using this feature, you can learn:

  • How often is the team deploying to production using deployment job frequently.

  • Time between merge and deploy.

  • Failed build jobs can be an indication of deployments to production being blocked.

Deployment job calculations are used on the Cycle time screen.

Identifying jobs as deployment jobs

Once a jobs are linked to a product, you can use Manage jobs to mark individual jobs as a deployment job using the Deployment job toggle. A blue toggle to the right indicates that a job is a deployment job; a grey toggle with the switch to the left indicates a non-deployment job.

To identify a job as a deployment job:

  1. Open CloudBees Engineering Efficiency and sign in as an admin.

  2. Select the desired product.

  3. Select Manage jobs in the left navigation.

  4. Locate the job.

  5. Select the slider to the far right of the job to identify it as as a Deployment job. The slider turns blue.

Repeat the above steps for any additional jobs you wish to identify as deployment jobs.

Disabling the deployment job identifier

You can remove the deployment job identifier by activating the slider.

  1. Open CloudBees Engineering Efficiency and sign in as an admin.

  2. Select the desired product.

  3. Select Manage jobs in the left navigation.

  4. Locate the job.

  5. Select the slider to the far right of the job to identify it as as a Deployment job. The slider turns grey.