For the complete documentation index, see llms.txt. This page is also available as Markdown.

Jenkins Job Reporter Plugin

Integrate Harness AIDI with the Jenkins Job Reporter Plugin.

The SEI Job Reporter Plugin, monitors all job runs. As soon as a job run completes it sends the info about job run and failed logs back to SEI SaaS.

This plugin does not perform any periodic push. It gathers information about job stages and steps.

  • If a job run fails and has no stages, the plugin captures the failed job run logs.

  • If the job has stages but no steps, it captures logs for the failed stages.

  • If the job has steps, it captures logs for the failed steps.

The plugin does not capture logs for any successful job, stage, or step. The plugin supports the failure triage feature.

Dependency Name
Direct Dependency/Indirect Dependency
Version
URL

REST Implementation for Blue Ocean

Direct

1.23.2

Common API for Blue Ocean

Indirect

1.23.2

REST API for Blue Ocean

Indirect

1.23.2

Blue Ocean Core JS

Indirect

1.23.2

Web for Blue Ocean

Indirect

1.23.2

JWT for Blue Ocean

Indirect

1.23.2

Pipeline implementation for Blue Ocean

Direct

1.23.2

Pipeline SCM API for Blue Ocean

Indirect

1.23.2

Dashboard for Blue Ocean

Direct

1.23.2

Pub-Sub "light" Bus

Indirect

1.13

Config as Code Settings

Requirements

  • Jenkins version should be 2.426.3 or higher.

  • Use the plugin version 1.0.33 or higher of SEI Job Reporter Jenkins plugin.

Step-by-step instructions

To configure the SEI Job Reporter plugin in Jenkins using Configuration as Code (JCasC), follow the instructions below:

  1. Locate the jenkins.yaml configuration file and insert the following configuration under the unclassified section of the jenkins.yaml file:

    Here's an example jenkins.yaml file

  2. Specify the applicationType based on the environment:

    • Prod 1: SEI_HARNESS_PROD_1

    • Prod 2: SEI_HARNESS_PROD_2

    • Prod 3: SEI_HARNESS_PROD_3

By following these steps, you can properly configure the SEI Job Reporter plugin using Jenkins Configuration as Code. Make sure to replace placeholder values like <SEI_API_KEY>, <PLUGIN_PATH>, <INSTANCE_NAME>, and more with actual data relevant to your Jenkins environment.

Last updated

Was this helpful?