[JIRA] (JENKINS-41905) Periodic Reincarnation plugin does not work with Pipeline job type
Title: Message Title
Torben Thellefsen commented on JENKINS-41905
Re: Periodic Reincarnation plugin does not work with Pipeline job type
Issue still exists. Example declarative pipeline to demonstrate the problem:
pipeline {
agent any
stages {
stage('Test') {
steps {
error 'some string'
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178758.148667454.15091.1563437940631%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56587) PerfPublisher 8.08 does not mark build as unstable even if there are errors
Title: Message Title Torben Thellefsen resolved as Fixed Fixed and released as 8.09, as Eugene Schava wrote. Jenkins / JENKINS-56587 PerfPublisher 8.08 does not mark build as unstable even if there are errors Change By: Torben Thellefsen Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56587) PerfPublisher 8.08 does not mark build as unstable even if there are errors
Title: Message Title Torben Thellefsen commented on JENKINS-56587 Re: PerfPublisher 8.08 does not mark build as unstable even if there are errors Ah, discovered it. There's a difference between setting threshold: '' and threshold: '0'. For the former, the success/unstable check is not performed, but it is for the latter. It is exactly as documented, but different from the older (pre-8.08) default. Anyway, I'll fix my pipelines. Sorry about the noise. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56587) PerfPublisher 8.08 does not mark build as unstable even if there are errors
Title: Message Title Torben Thellefsen commented on JENKINS-56587 Re: PerfPublisher 8.08 does not mark build as unstable even if there are errors Hm, something is not quite right. The test case I gave above worked on my development machine, but when the released plugin (8.09) was installed in production, it looks like it does not work (still gives SUCCESS when there are failed tests). I'm trying to get some logs, hoping that will help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56587) PerfPublisher 8.08 does not mark build as unstable even if there are errors
Title: Message Title Torben Thellefsen updated JENKINS-56587 Jenkins / JENKINS-56587 PerfPublisher 8.08 does not mark build as unstable even if there are errors Change By: Torben Thellefsen Resolution: Fixed Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title Torben Thellefsen commented on JENKINS-56528 Re: Gerrit trigger 2.29.0 does not trigger jobs PR#350 is about handling dynamic configuration, and we certainly have that for most of our jobs, so there is that. I have no data whether our few statically configured jobs would trigger or not; they run much more rarely than the others. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56587) PerfPublisher 8.08 does not mark build as unstable even if there are errors
Title: Message Title Torben Thellefsen updated JENKINS-56587 Jenkins / JENKINS-56587 PerfPublisher 8.08 does not mark build as unstable even if there are errors Change By: Torben Thellefsen Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56587) PerfPublisher 8.08 does not mark build as unstable even if there are errors
Title: Message Title Torben Thellefsen commented on JENKINS-56587 Re: PerfPublisher 8.08 does not mark build as unstable even if there are errors I can confirm your workaround works - but you likely knew that Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56587) PerfPublisher 8.08 does not mark build as unstable even if there are errors
Title: Message Title
Torben Thellefsen created an issue
Jenkins / JENKINS-56587
PerfPublisher 8.08 does not mark build as unstable even if there are errors
Issue Type:
Bug
Assignee:
Eugene Schava
Components:
perfpublisher-plugin
Created:
2019-03-15 16:03
Environment:
Jenkins 2.150.3, perfpublisher 8.08, many others
Priority:
Minor
Reporter:
Torben Thellefsen
Since upgrading from 8.06 to 8.08 (which fixed some html issues for us), we have noticed that builds are no longer marked unstable when there are test errors. It does not matter whether we set the parameter "threshold" (or "unstableThreshold") to blank or zero '0'. To reproduce, make a pipeline with this configuration and run it:
pipeline {
agent any
stages {
stage('perf') {
steps {
writeFile file: 'result.xml', text: '''
FAILBAD
GOOD
'''
perfpublisher name: 'result.xml', threshold: '0', unstableThreshold: '0', healthy: '', unhealthy: '', metrics: '', parseAllMetrics: false
}
}
}
}
Expected result: Build is unstable (yellow), because there's 1 test failure. Actual result: Build is stable (blue/green). The plugin does correctly show that there's 1 success and 1 failure, but does not set status correctly. Here's an excerpt of the log output from the build:
[JIRA] (JENKINS-56528) Gerrit trigger 2.29.0 does not trigger jobs
Title: Message Title Torben Thellefsen created an issue Jenkins / JENKINS-56528 Gerrit trigger 2.29.0 does not trigger jobs Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2019-03-12 17:42 Environment: Linux, openjdk 8, Jenkins 2.150.3, gerrit-trigger 2.29.0, gerrit server runs 2.13.7, lots of other plugins. Priority: Major Reporter: Torben Thellefsen After upgrading yesterday, triggering stopped working today. There is some evidence that triggering did work for a time, but not conclusive. I tried restarting Jenkins, then Gerrit. Nothing helped. Saw logs of "too many events in the queue" (similar to JENKINS-52636), but the whole setup felt more like JENKINS-53738. What finally helped was downgrading to 2.28.0 of the plugin. Then triggering started again. I never tried re-saving a job; we have a few too many of those that I want to do that for all of them. Add Comment
