About This Integration

Overview of the integration

Jenkins is an open source automation server. It helps automate the parts of software development related to building, testing, deploying and facilitating continuous integration and continuous delivery.

This integration enables you to start or stop a Jenkins job via Microsoft Power Automate when modifying the management method of a configuration item (CI) in the Service Catalog (Is a service option selected or unselected in the CI form).
 

Use case: Start a development platform or an Amazon platform when the Is a service option is selected in the CI form.
 

Preview of the tools used in this integration

IntegrationTool_MicrosoftAzureLogicApps

IntegrationTool_MicrosoftPowerAutomate

Integration Data Feed (direction)		Authentication Type		Integration Connector Options
Service Manager		Depending on the third-party service used (authentication managed by Logic Apps) Basic Authentication for the Service Manager API REST		Service Manager :    Workflow    Business rule MS Power Automate:    Connector: When a HTTP request is received (Trigger Service Manager => Logic Apps)

Available versions
	SaaS	On-premises
Service Manager
Third-party product		N/A

Jenkins - definitions

• Jenkins is an open-source automation tool for continuous integration.

• Each time software code is modified in the configuration management, Jenkins will perform a series of tasks to automatically recompile and test the software and send an alert to developers in the event of errors.

• A job is a set of tasks that Jenkins must perform in a sequence, e.g. extract the source code from the version control, compile the code, run individual tests, etc.

• A build represents the execution of all of the job's tasks.

Flows

Prerequisites

• You must have an abonnement Azure. If this is not the case, you can create a free account, or buy a pay-as-you-go subscription .
• You must have the relevant accounts and access rights to the services interfacing with Logic Apps.
• You must have an account authorizing access to your Service Manager platform with a profil and access rights to menu Asset & Configuration.

• You must add the fields specific to the Jenkins integration in the Create a new Configuration Item wizard  -  See Procédure
• You must add the Start Jenkins Flow field to the CI form in Service Manager  -  SeeProcédure

Caution

Caution_TitleActionInPowerAutomateFlow

Step-by-Step Integration Process

You configure the running of a Jenkins job in Service Manager, via Microsoft Power Automate in two phases:

• In Microsoft Azure Logic Apps, create an MS Power Automate flow
• In Service Manager, start or stop the Jenkins flow when modifying the management method of a configuration item (CI) in the Service Catalog

Microsoft Azure Logic Apps: Create the MS Power Automate flow

Description of the workflow

Step 1 : Create the step that will trigger the flow Step 2 : Start the Jenkins flow Step 3 : Save the configuration of the workflow

Step 1: Create the step that will trigger the flow

1. Log in to the Azure portal using your Azure account.

2. Create a new logic app. Open the Logic App Designer.
       See Microsoft Azure Logic Apps integration for details on the procedure

3. Create a When a HTTP request is received step that will trigger the workflow.

Specify the information on the trigger. Body: Copy and paste the JSON schema below. Display the JSON schema {    "type": "object",    "properties": {        "URL": {            "type": "string"         },        "Account": {            "type": "string"         },        "ID": {            "type": "string"         },        "Service": {            "type": "string"         },        "Flow": {            "type": "string"         }     } } Method: Select the POST value. Save the trigger. The following information will be retrieved from Service Manager: URL, Account, CI ID, Service boolean value indicating the management method of the CI in the Service Catalog (0 = CI not managed in the catalog, 1 = CI managed in the catalog), Flow boolean value indicating the state of the Start Jenkins Flow checkbox in the CI form (0 = box is not checked, 1 = box is checked)

Step 2: Start the Jenkins flow

1. Create a Condition action to check for changes to the state of the Start Jenkins Flow checkbox in the CI form.

Rename it Condition using in the title bar. Click Add to add the following line to the condition. Value tested Condition line State of the Start Jenkins Flow checkbox in the CI form Select Value: Select the Flow field to return the state of the checkbox. Comparator: Select is equal to. Value: Enter True.

2. Specify the actions to be performed when the Start Jenkins Flow checkbox is selected (value True - condition satisfied).

• Go to the If Yes branch.
• Select Add an action to add the following actions.

3. Create a HTTP action to start the Jenkins flow.

Rename it HTTP Send To Jenkins Jobs using in the title bar. Specify the information on the action. Method: Enter the POST value. URI: Enter the full URL of the Jenkins job in the following format. https://{Jenkins_server}/view/{Job_folder}/job/{Job_name}/ Replace: {Jenkins_server} with the URL of your Jenkins server {Job_folder} with the folder where your Jenkins jobs are saved {Job_name} with the name of the Jenkins job to be created example    https://Jenkins.net/view/Dev/job/Start_environment/

Step 3: Save the configuration of the workflow

1. Click Save at the bottom of the flow.

Service Manager: Start and stop the Jenkins flow

Step 1: Add the information specific to the Jenkins integration

1. Add the fields specific to the Jenkins integration in the Create a new Configuration Item wizard based on your requirements.

      See the detailed procedure

2. Add the Start Jenkins Flow field to the CI form.

      See the detailed procedure

Step 2: Start and stop the Jenkins flow from the CI form

1. Select the Start Jenkins Flow checkbox in the CI form to enable the Jenkins flow. (1)

2. Select the Is a service option in the CI form to monitor the CI in the Service Catalog. (2)

or

Unselect the Is a service option in the CI form if you do not want to monitor the CI in the Service Catalog.

3. Click Save.

The Jenkins flow will automatically start or stop.

Links to other integrations

• Microsoft Azure Logic Apps
• Microsoft Power Automate