×
Find plugins

Office 365 Connector2.5Minimum Jenkins requirement: 1.651.2ID: Office-365-Connector

Installs: 782
Last released: a day ago
Maintainers
Out conn
Srivardhan Hebbar

Plugin Information

Plugin ID

Office-365-Connector

Changes

In Latest Release
Since Latest Release

Latest Release
Latest Release Date
Required Core
Dependencies

2.5 (archives)
Aug 17, 2017
1.651.2
junit (version:1.5)
workflow-step-api (version:1.11)

Source Code
Issue Tracking
Pull Requests
Maintainer(s)

GitHub
Open Issues
Pull Requests
Out conn (id: outconn)
Srivardhan Hebbar (id: srhebbar)

Usage

Installations

2016-Aug 45
2016-Sep 61
2016-Oct 77
2016-Nov 216
2016-Dec 249
2017-Jan 312
2017-Feb 348
2017-Mar 481
2017-Apr 572
2017-May 642
2017-Jun 741
2017-Jul 782

This plugin from Microsoft Corp. allows sending running Jobs status notifications.

Description

Once the Office 365 Connector plugin is installed, webhooks for notifications are defined in Job Notification section of the configuration of job. Here is the screenshot for that section
Here are the steps to configure a webhook

  • Click on the "Add Webhook" button.
  • Enter the webhook URL which is displayed when you create JenkinsCI connector in Office365.
  • Check the boxes for which you want to receive notifications.
  • Configure the timeout after which jenkins plugin would give on unavailable server.

Once you configure this plugin, build related messages will appear in the workplace messaging system.

To send messages from inside pipeline script:

  • Configure the webhook you want to send message following the steps mentioned above.
  • In the Pipeline script use the following command:
    office365ConnectorSend message: "<Your message>", status:"<Build status>"

To send message from inside Jenkinsfile:

  • In the script use the following command:
    office365ConnectorSend message: "<Your message>", status:"<Build status>", webhookUrl:'<The connector webhook url>'

Requirements

This plugin is created to work with Office 365 Groups.

Release 2.5

  1. When selected notification type as "Failure", then notification is sent only when previous build is success and current build failed. No notification would be sent for repeated failure. If user wants to receive notification for repeated failure, then he/she should select "Repeated Failure" notification type.
  2. Details about test cases and developers would be displayed in the card only if those details are availble, else they would not be displayed.

Release 2.4.1

  1. Removed unwanted logging on the console.

Release 2.4

  1. Removed Build Start Time from the office365ConnectorSend message card.

Release 2.3

  1. Added support to set "Status" of the card from office365ConnectorSend command.
  2. Added facts culprits and developers when the build is triggered due to SCM commit.

Release 2.2

  1. Added support to send notification from inside Jenkinsfile. 
  2. Added option webhookUrl for the office365ConnectorSend command.

Release 2.1

  1. Fixed Back To Normal Time showing some invalid time issue.

Release 2.0

  1. Added support to send notification from inside the pipeline script. The user can use office365ConnectorSend command to send any notification.

Release 1.4

  1. Included author name and number of files changed if the build is due to SCM change.

Release 1.3.3

  1. Tracks UNSTABLE to SUCCESS build status changes with Notify Back To Normal event.

Release 1.3

  1. Supports notification for pipeline jobs.

Release 1.2.1

  1. Initial version.
ArchivesGet past versions
Labels