[JIRA] (JENKINS-60314) Git knowledge base
Title: Message Title Tomas Westling commented on JENKINS-60314 Re: Git knowledge base Hi Thomas, I think it sounds like a good idea. The information that is to be stored is suited well for git, since it is human-readable text. The biggest pro for it would be the history, which sounds like a good reason to do it, in both of the current solutions, we only have a latest version of a failure cause. And implementation-wise I guess it wouldn't be that hard to integrate with the existing git plugins. It isn't something I have the time to look at, but feel free to hack away and create a pull request. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.203311.1574934344000.8583.1574936460160%40Atlassian.JIRA.
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title Tomas Westling assigned an issue to Oliver Gondža Jenkins / JENKINS-59840 NullPointerException when activating the plugin Change By: Tomas Westling Assignee: Tomas Westling Oliver Gondža Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202575.157138872.10261.1571388960259%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. That is weird, but seems it has to be a problem on your end, since 1.23.1 is visible from all our Jenkins instances. When was the last "update information obtained" ? It has been in the update site for quite a while now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202251.1569939008000.10120.1571381100403%40Atlassian.JIRA.
[JIRA] (JENKINS-59593) enableStatistics and successfulLogging config values are not loaded properly
Title: Message Title Tomas Westling updated JENKINS-59593 Jenkins / JENKINS-59593 enableStatistics and successfulLogging config values are not loaded properly Change By: Tomas Westling Status: In Review Closed Resolution: Fixed Released As: 1.23.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202234.1569877154000.8678.1571222640230%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling updated JENKINS-59610 Jenkins / JENKINS-59610 Build failure causes are deleted when saving Jenkins global configuration. Change By: Tomas Westling Status: In Review Closed Resolution: Done Released As: 1.23.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202251.1569939008000.8671.1571222580558%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. I can't say for sure, but I am currently working on fixing some review comments. After the pull request is in, releasing a new version is quick work. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202251.1569939008000.3287.1570535460326%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. I have uploaded a fix here: https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/112 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202251.1569939008000.985.1570191600230%40Atlassian.JIRA.
[JIRA] (JENKINS-59593) enableStatistics and successfulLogging config values are not loaded properly
Title: Message Title Tomas Westling updated JENKINS-59593 Jenkins / JENKINS-59593 enableStatistics and successfulLogging config values are not loaded properly Change By: Tomas Westling Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202234.1569877154000.981.1570191540956%40Atlassian.JIRA.
[JIRA] (JENKINS-59593) enableStatistics and successfulLogging config values are not loaded properly
Title: Message Title Tomas Westling commented on JENKINS-59593 Re: enableStatistics and successfulLogging config values are not loaded properly I have uploaded a fix here: https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/112 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202234.1569877154000.983.1570191541131%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling updated JENKINS-59610 Jenkins / JENKINS-59610 Build failure causes are deleted when saving Jenkins global configuration. Change By: Tomas Westling Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202251.1569939008000.979.1570191540830%40Atlassian.JIRA.
[JIRA] (JENKINS-59593) enableStatistics and successfulLogging config values are not loaded properly
Title: Message Title Tomas Westling started work on JENKINS-59593 Change By: Tomas Westling Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202234.1569877154000.896.1570177920315%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling edited a comment on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. Yes, the issue is in the Build Failure Analyzer , v 1.23 and is present in every Jenkins version.I'm working on a fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202251.1569939008000.9635.1570015860305%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. Yes, the issue is in the Build Failure Analyzer, present in every Jenkins version. I'm working on a fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202251.1569939008000.9633.1570015860281%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. I have been able to reproduce the issue locally. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202251.1569939008000.9548.1570006260228%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling started work on JENKINS-59610 Change By: Tomas Westling Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202251.1569939008000.9542.1570006200341%40Atlassian.JIRA.
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Tomas Westling commented on JENKINS-59582 Re: build-failure-analyzer fails to load on startup, exception thrown. Yeah that doesn't seem related to this one, so please add a new one. Is this reproducible every time? I.e. if you add a failure cause, save, is it immediately deleted? As for the original issue, I took a quick look at your xml, but since it was so large it was hard to deduce what the problem with it was. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.20.1569837284000.8621.1569929880112%40Atlassian.JIRA.
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Tomas Westling commented on JENKINS-59582 Re: build-failure-analyzer fails to load on startup, exception thrown. Hi, I tried reproducing this in Linux (which is my work environment), but wasn't succesful. Before I start spinning up a vm to test this in Windows, could you check out https://issues.jenkins-ci.org/browse/JENKINS-55945 and see if it is related to your issue in any way? Br Tomas Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.20.1569837284000.7755.1569841560119%40Atlassian.JIRA.
[JIRA] (JENKINS-56285) Timestamp plugin compatability (Tiny css style change)
Title: Message Title Tomas Westling assigned an issue to Unassigned Jenkins / JENKINS-56285 Timestamp plugin compatability (Tiny css style change) Change By: Tomas Westling Assignee: Tomas Westling 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.197864.1551179179000.1925.1566995580209%40Atlassian.JIRA.
[JIRA] (JENKINS-56285) Timestamp plugin compatability (Tiny css style change)
Title: Message Title Tomas Westling commented on JENKINS-56285 Re: Timestamp plugin compatability (Tiny css style change) Unfortunately, I haven't had the time to look at this. If you want to implement it yourself, I will gladly accept a pull request. 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.197864.1551179179000.1923.1566995520145%40Atlassian.JIRA.
[JIRA] (JENKINS-22026) Propagate failure causes from downstream builds
Title: Message Title Tomas Westling commented on JENKINS-22026 Re: Propagate failure causes from downstream builds I haven't prioritized this issue, but will have a second look now. I'll analyze it again and get back to you. 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-41278) bfa should support a shared mongodb database
Title: Message Title Tomas Westling commented on JENKINS-41278 Re: bfa should support a shared mongodb database Good idea, some documentation regarding this should be added. I can tell you straight away though that it works like a charm, and is part of the reason why it was implemented. 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-22026) Propagate failure causes from downstream builds
Title: Message Title Tomas Westling commented on JENKINS-22026 Re: Propagate failure causes from downstream builds From what I've observed, it works in 1.6 but not in 2.x, so upgrading shouldn't help anything. I can see that the issue comes from our use of reflection to find the Parameterized Trigger classes in order to find the downstream builds. I am not sure why this works in 1.6 but not in 2.x, but some changes to classloaders must have been made. Once https://github.com/jenkinsci/parameterized-trigger-plugin/pull/109 has been merged, we won't need the failing reflection code at all, and this issue should be solved. 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-22026) Propagate failure causes from downstream builds
Title: Message Title Tomas Westling commented on JENKINS-22026 Re: Propagate failure causes from downstream builds I can also see this bug in newer (2.x) Jenkins versions, but not in 1.6. I'll dig a little deeper. 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-6819) Jobs are triggered twice occasionally
Title: Message Title Tomas Westling commented on JENKINS-6819 Re: Jobs are triggered twice occasionally I have seen this happen in Jenkins 1.651.3, however, only when the Jenkins master is under heavy CPU load. Normally, everything works as it should, but on certain times when the Jenkins master CPU is running on max, we see two downstream builds of one project started, both builds pointing to the same parent build. This is done using the conditional build step + parameterized trigger and a schedule for the parent project. 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-37986) Build history supports column customization ?
Title: Message Title Tomas Westling commented on JENKINS-37986 Re: Build history supports column customization ? How is this related to the build failure analyzer plugin? I don't see the connection from reading the description. 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-29023) Propagate results from subjobs from MultiJob plugin
Title: Message Title Tomas Westling commented on JENKINS-29023 Re: Propagate results from subjobs from MultiJob plugin Yeah, maybe you should open a separate ticket for this, this discussion has nothing to do with the MultiJob plugin. Yes, I mean 1.12.1. Just to make sure, can you test out the very basics of the functionality and add on more complexity as you go along? If you create a job with one build step, a "trigger/call builds on another project", and in the other job, create one build step that fails, what is your result in BFA? No text saying "Subproject build" and a link to the failure in the subproject build? This is very basic functionality that I can reproduce in a minute or so, so I'm very curious what is going wrong at your end. 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-29023) Propagate results from subjobs from MultiJob plugin
Title: Message Title Tomas Westling commented on JENKINS-29023 Re: Propagate results from subjobs from MultiJob plugin Propagating downstream builds to the upstream build have been in the plugin since 1.21, which was released January 2015. The only configuration needed is: Create job a which triggers job b as a build step and waits for it to finish. Have job b fail. The failure causes found on b should appear on the build page for a. Are you triggering job b from a build step or a post-build step? If you do it from a post build step or you choose to not wait for it, then the functionality doesn't work, since job a is long since done running when project b is finished. 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-29023) Propagate results from subjobs from MultiJob plugin
Title: Message Title Tomas Westling commented on JENKINS-29023 Re: Propagate results from subjobs from MultiJob plugin The parameterized trigger plugin is already supported. If you set the build to wait for the sub-build to finish, the found failure causes from the sub build will be propagated up to the calling build. The MultiJob isn't supported yet and is nothing I have planned to implement. I would gladly accept pull requests for the functionality though. 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] [build-failure-analyzer-plugin] (JENKINS-35169) Jenkins "Job status" shows success even if it has many / all test cases failed
Title: Message Title Tomas Westling commented on JENKINS-35169 Re: Jenkins "Job status" shows success even if it has many / all test cases failed The build failure analyzer plugin is used to quickly tell a user what went wrong with a build when it failed, by matching regular expressions with the build log. It doesn't have any power over which builds fail or not. Since TestNG tells you that tests failed, I would start there, with the testng-plugin. Br Tomas Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-failure-analyzer-plugin] (JENKINS-35169) Jenkins "Job status" shows success even if it has many / all test cases failed
Title: Message Title Tomas Westling commented on JENKINS-35169 Re: Jenkins "Job status" shows success even if it has many / all test cases failed In which way is this problem related to the build failure analyzer plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
