Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39745

Office 365 Connector does not work with pipelines

    Details

    • Similar Issues:

      Description

      Microsoft Teams proposes to use the Office 365 connector plugin for Jenkins integration. But the bad news is it does not seem to work with Jenkins Pipelines.

      That is: in my Pipeline job I'm able to configure Office 365 Connector. But it silently does not work. That is: it produces no messages to Microsoft Teams or anything in Jenkins logs.

      And yes, on non-pipeline jobs the same configuration works perfectly.

      What information should I give to trace this better? I suspect, using Office 365 Connector with Jenkins Pipelines may require some other additional steps, but was unable to find them in documentation or code.

        Attachments

          Activity

          Hide
          bhunt Bryan Hunt added a comment -

          I've not been able to find any docs on how to call the plugin from a pipeline script.

          Show
          bhunt Bryan Hunt added a comment - I've not been able to find any docs on how to call the plugin from a pipeline script.
          Hide
          srhebbar Srivardhan Hebbar added a comment -

          The plugin is now updated to provide notifications for pipeline jobs too.

          Show
          srhebbar Srivardhan Hebbar added a comment - The plugin is now updated to provide notifications for pipeline jobs too.
          Hide
          bhunt Bryan Hunt added a comment -

          Where is the documentation for sending a notification from a pipeline script?

          Show
          bhunt Bryan Hunt added a comment - Where is the documentation for sending a notification from a pipeline script?
          Hide
          vkorytov Vasily Korytov added a comment -

          Bryan Hunt it now works as configured in job settings, i.e. in simple cases there is no need to call it from pipeline script. if that does not suffice you, I suggest making a new ticket like `manual usage of o365 connector from pipeline'.

          Show
          vkorytov Vasily Korytov added a comment - Bryan Hunt it now works as configured in job settings, i.e. in simple cases there is no need to call it from pipeline script. if that does not suffice you, I suggest making a new ticket like `manual usage of o365 connector from pipeline'.
          Hide
          bhunt Bryan Hunt added a comment -

          I'll create a new bug. Multi-branch pipeline builds do not support notifications in the UI. You must call from your script.

          Show
          bhunt Bryan Hunt added a comment - I'll create a new bug. Multi-branch pipeline builds do not support notifications in the UI. You must call from your script.

            People

            • Assignee:
              srhebbar Srivardhan Hebbar
              Reporter:
              vkorytov Vasily Korytov
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: