[JIRA] (JENKINS-39010) Comment Added event does not work
Title: Message Title Ry Jones edited a comment on JENKINS-39010 Re: Comment Added event does not work - This is still an issue in Jenkins 2.89.4, gerrit-trigger-plugin 2.27.5. Specifically: - - Job 0 triggers on new patchset, leaves a comment "DO BUILD 1" in gerrit when it completes. - - Job 1 triggers on comment regex of "DO BUILD 1". Does not trigger, even though comment appears in Gerrit - - However: if a user manually places a comment "DO BUILD 1" on patchset, Job 1 is triggered correctly. -see below 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-39010) Comment Added event does not work
Title: Message Title Ry Jones commented on JENKINS-39010 Re: Comment Added event does not work Björn Pedersen you are correct. What we did to work around this is change the email address the plugin uses to post comments. 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-39010) Comment Added event does not work
Title: Message Title Björn Pedersen commented on JENKINS-39010 Re: Comment Added event does not work Ry Jones: I think this actually excpected behaviour: The plugin filters it's own comments to avoid trigger-loops. One solution: use the gerrit ssh cli to post the review 'DO BUILD 1' with another account to force triggering, or just trigger the other job directly (there are different ways to do that in jenkins...) 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-39010) Comment Added event does not work
Title: Message Title Ry Jones edited a comment on JENKINS-39010 Re: Comment Added event does not work This is still an issue in Jenkins 2.89.4, gerrit-trigger-plugin 2.27.5 . Specifically:Job 0 triggers on new patchset, leaves a comment "DO BUILD 1" in gerrit when it completes.Job 1 triggers on comment regex of "DO BUILD 1". Does not trigger, even though comment appears in GerritHowever: if a user manually places a comment "DO BUILD 1" on patchset, Job 1 is triggered correctly. 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-39010) Comment Added event does not work
Title: Message Title Ry Jones commented on JENKINS-39010 Re: Comment Added event does not work This is still an issue in Jenkins 2.89.4, gerrit-trigger-plugin 2.27.5 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-39010) Comment Added event does not work
Title: Message Title fahd arshad updated an issue Jenkins / JENKINS-39010 Comment Added event does not work Change By: fahd arshad Priority: Critical Blocker 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-39010) Comment Added event does not work
Title: Message Title fahd arshad updated an issue Jenkins / JENKINS-39010 Comment Added event does not work Change By: fahd arshad We recently upgraded our jenkins server from 1 version 2 . 67 28 to 2. 25 30 . Gerrit trigger (v2.22.0) on *comments added Contains Regex* does not seem to work ever since the upgrade. Other gerrit triggers seems to be working flawlessly. 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-39010) Comment Added event does not work
Title: Message Title fahd arshad commented on JENKINS-39010 Re: Comment Added event does not work Any update on this ? gerrit-trigger 2.22.0 version does not seem to work with Jenkins version 2.30 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-39010) Comment Added event does not work
Title: Message Title Fathi Boudra commented on JENKINS-39010 Re: Comment Added event does not work yes, unfortunately, reverting to 2.20.0 has incompatibilities with JGit4: http://jenkins-ci.361315.n4.nabble.com/JGit-api-changed-Handling-removal-of-methods-from-an-underlying-API-td4822183.html you'll also need to revert to git-client/1.19.6 and git/2.4.4 as well. Moving forward, the proper fix is really to get comments-added event support fixed. rsandell any chance to get your opinion please? 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-39010) Comment Added event does not work
Title: Message Title Ry Jones commented on JENKINS-39010 Re: Comment Added event does not work Fathi Boudra this is our experience, as well. Rolling back to 2.20.0 causes the plugin to crash, and 2.22.0 is inop. I've tried adding regexes but they don't seem to fire 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-39010) Comment Added event does not work
Title: Message Title Fathi Boudra commented on JENKINS-39010 Re: Comment Added event does not work Similar regression. Jobs used to work with 2.20.0 version. After upgrading to 2.22.0 version, it doesn't work anymore. 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-39010) Comment Added event does not work
Title: Message Title fahd arshad updated an issue Jenkins / JENKINS-39010 Comment Added event does not work Change By: fahd arshad Issue Type: New Feature Bug 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-39010) Comment Added event does not work
Title: Message Title fahd arshad updated an issue Jenkins / JENKINS-39010 Comment Added event does not work Change By: fahd arshad Priority: Minor Critical 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-39010) Comment Added event does not work
Title: Message Title fahd arshad created an issue Jenkins / JENKINS-39010 Comment Added event does not work Issue Type: New Feature Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/Oct/16 8:14 AM Priority: Minor Reporter: fahd arshad We recently upgraded our jenkins server from 1.67 to 2.25. Gerrit trigger on comments added Contains Regex does not seem to work ever since the upgrade. Other gerrit triggers seems to be working flawlessly. Add Comment This message was sent by
