[JIRA] (JENKINS-50640) Link messages together
Title: Message Title Srivardhan Hebbar assigned an issue to Out conn Jenkins / JENKINS-50640 Link messages together Change By: Srivardhan Hebbar Assignee: Srivardhan Hebbar Out conn Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42306) Error "Unable to cast run to abstract build" with AccuRev
Title: Message Title Srivardhan Hebbar resolved as Fixed Jenkins / JENKINS-42306 Error "Unable to cast run to abstract build" with AccuRev Change By: Srivardhan Hebbar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42306) Error "Unable to cast run to abstract build" with AccuRev
Title: Message Title Srivardhan Hebbar commented on JENKINS-42306 Re: Error "Unable to cast run to abstract build" with AccuRev Hi Timothy Williams Can you try with 2.4.2? Do you still see the exception trace on the console? The details I need is: 1. Are both Jenkins and AccuRev running in the same server? 2. Is there any special configuration for AccuRev that I need to know to reproduce the same setup here? 3. Are you using any specific plugin to detect the SCM changes from AccuRev? Thank-you Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42306) Error "Unable to cast run to abstract build" with AccuRev
Title: Message Title Srivardhan Hebbar commented on JENKINS-42306 Re: Error "Unable to cast run to abstract build" with AccuRev Hi Timothy Williams With the version 2.4.1 the unwanted logging on the console have been removed. So you should not be seeing the stack trace on the console. Thank-you, Sri Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42177) [office365ConnectorSend] 'Unable to cast run to abstract build' error appears in pipeline build (Jenkinsfile).
Title: Message Title Srivardhan Hebbar resolved as Fixed With release 2.4.1, all unwanted logging have been removed. Jenkins / JENKINS-42177 [office365ConnectorSend] 'Unable to cast run to abstract build' error appears in pipeline build (Jenkinsfile). Change By: Srivardhan Hebbar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-42033) Override `Start Time` (or remove it at all) in report with `office365ConnectorSend` command
Title: Message Title Srivardhan Hebbar resolved as Fixed With version 2.4, Build Start Time from the message card has been removed. Jenkins / JENKINS-42033 Override `Start Time` (or remove it at all) in report with `office365ConnectorSend` command Change By: Srivardhan Hebbar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-40570) Override `Status` in report with `office365ConnectorSend` command
Title: Message Title Srivardhan Hebbar resolved as Fixed With release 2.3, this support has been added to office365ConnectorSend command. To set the status just pass the status to the command via status parameter. Syntax: office365ConnectorSend message:'', status:'', webhookUrl:'' Jenkins / JENKINS-40570 Override `Status` in report with `office365ConnectorSend` command Change By: Srivardhan Hebbar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-40075) Add support for multi-branch pipeline builds
Title: Message Title Srivardhan Hebbar resolved as Fixed With release 2.2 version an option webhookUrl has been added to office365ConnectorSend command which can be used to send message to connector. Below is the syntax: office365ConnectorSend message:'', webhookUrl:'' Jenkins / JENKINS-40075 Add support for multi-branch pipeline builds Change By: Srivardhan Hebbar Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-40075) Add support for multi-branch pipeline builds
Title: Message Title Srivardhan Hebbar commented on JENKINS-40075 Re: Add support for multi-branch pipeline builds Vasily Korytov The notification URL would be picked from the one configured in the plugin. Kindly follow the steps mentioned in the below link: https://wiki.jenkins-ci.org/display/JENKINS/Office+365+Connector+Plugin When you go in the configuration page of the project, you will see Office 365 Connector tab, click on that and configure the webhook url and select the events for which you want to receive notifications. This same URL would be picked to send the messages when you use "office365ConnectorSend" command from inside pipeline script to send messages. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40075) Add support for multi-branch pipeline builds
Title: Message Title Srivardhan Hebbar resolved as Fixed office365ConnectorSend command can be used to send notifications from inside pipeline script. The support has been added to the plugin in the revision 2.0. The same has been updated in the wiki. Jenkins / JENKINS-40075 Add support for multi-branch pipeline builds Change By: Srivardhan Hebbar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-40052) Office 365 Connector doesn't supply commiter name(s) for events started by SCM change
Title: Message Title Srivardhan Hebbar resolved as Fixed Released version 1.4 with support to show authors if the build is due to SCM change. Jenkins / JENKINS-40052 Office 365 Connector doesn't supply commiter name(s) for events started by SCM change Change By: Srivardhan Hebbar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-40051) Office 365 Connector doesn't track UNSTABLE to SUCCESS build status changes with Notify Back To Normal event
Title: Message Title Srivardhan Hebbar resolved as Fixed This event is now tracked with the 1.3.3 build. Jenkins / JENKINS-40051 Office 365 Connector doesn't track UNSTABLE to SUCCESS build status changes with Notify Back To Normal event Change By: Srivardhan Hebbar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-39745) Office 365 Connector does not work with pipelines
Title: Message Title Srivardhan Hebbar resolved as Fixed The plugin is now updated to provide notifications for pipeline jobs too. Jenkins / JENKINS-39745 Office 365 Connector does not work with pipelines Change By: Srivardhan Hebbar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
