-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins LTS on CentOS Linux 7 + OpenJDK 8
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.