Re: Issues after upgrade
It seems that some of the build jobs are hanging at the end. My job normally finishes up like this: Waiting for Jenkins to finish collecting data [JENKINS] Archiving ... [JENKINS] Archiving ... [CHECKSTYLE] Plug-in Result: Success - no threshold has been exceeded [CHECKSTYLE] Plug-in Result: Success - no threshold has been exceeded [FINDBUGS] Plug-in Result: Success - no threshold has been exceeded [FINDBUGS] Plug-in Result: Success - no threshold has been exceeded [PMD] Plug-in Result: Success - no threshold has been exceeded [PMD] Plug-in Result: Success - no threshold has been exceeded [PMD] Plug-in Result: Success - no threshold has been exceeded channel stopped [workspace] $ /bin/sh -xe /tmp/jenkins6227222757670508122.sh Archiving artifacts Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: SUCCESS But after the upgrade, the build just hangs after the 3 PMD lines. On Fri, Apr 19, 2019 at 3:30 PM Ryan Shoemaker wrote: > Hi, > > I just upgraded from 2.79 to 2.164.2 and am seeing a few issues: > > 1. I can't load job configuration pages. When I click on the job > "configure" link, the browser just sits there spinning and the page never > loads. There are no errors/warnings in the log to indicate any problems. > I've scanned through https://issues.jenkins-ci.org/browse/JENKINS-49630, > but there's no obvious solution in there. I'm not sure how to proceed > debugging this issue. > > 2. When I load the plugins page, the log spews an error for every plugin: > "Could not find dependency jdk-tool of " I do have the JDK Tool plugin > installed, but seemingly everything depends on it and I am unable to > uninstall it. > > 3. Relating to #1, I read some discussion about it possibly being related > to the "Violations" plugin, which should be replaced by the Warnings Next > Gen plugin (along with the old "Warnings" plugin), yet I don't see the > plugin in the "Available" list on the manage plugins page. I feel like I'm > missing something obvios here. > > I do have 3 plugin updates that I haven't installed (otherwise, all of my > plugins are up-to-date): > > Matrix Auth Strategy > > Simple Theme > > SSH Slaves > > Each have a giant warning about incompatible setting formats and I haven't > figured out which of my jobs depend on these plugins (if any). > > Thanks, > > --Ryan > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMhG3rJuWmdEK0zhjTe9QZm1PZ54%2BddgyizhEdsEaXiKmT5gmw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Issues after upgrade
Hi, I just upgraded from 2.79 to 2.164.2 and am seeing a few issues: 1. I can't load job configuration pages. When I click on the job "configure" link, the browser just sits there spinning and the page never loads. There are no errors/warnings in the log to indicate any problems. I've scanned through https://issues.jenkins-ci.org/browse/JENKINS-49630, but there's no obvious solution in there. I'm not sure how to proceed debugging this issue. 2. When I load the plugins page, the log spews an error for every plugin: "Could not find dependency jdk-tool of " I do have the JDK Tool plugin installed, but seemingly everything depends on it and I am unable to uninstall it. 3. Relating to #1, I read some discussion about it possibly being related to the "Violations" plugin, which should be replaced by the Warnings Next Gen plugin (along with the old "Warnings" plugin), yet I don't see the plugin in the "Available" list on the manage plugins page. I feel like I'm missing something obvios here. I do have 3 plugin updates that I haven't installed (otherwise, all of my plugins are up-to-date): Matrix Auth Strategy Simple Theme SSH Slaves Each have a giant warning about incompatible setting formats and I haven't figured out which of my jobs depend on these plugins (if any). Thanks, --Ryan -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMhG3rL2sVOvvsrE7doHv9aNVKLRKYLmUH-OGvOn0uR5NPEe8A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: (email-ext plugin) e-mail notification for new static analysis issues
Ah, thanks - that's what I was missing. --Ryan On Monday, 19 May 2014 12:14:34 UTC-4, slide wrote: If you click on the list of triggers to add, there should be a Script Trigger, add that and then define the groovy in the configuration for that trigger. Thanks, slide On Mon, May 19, 2014 at 9:12 AM, Ryan Shoemaker ryan.sh...@gmail.comjavascript: wrote: Hi, I'm trying to figure out how to configure the email-ext plugin to generate an e-mail whenever someone introduces a new static analysis issue (identified by findbugs, pmd, and checkstyle plugins). I found a mention of this on the static analysis plugin pagehttps://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-insand asked my question there, but Ulli suggested I try the group instead. The plugin page indicates that it is possible to add an email-ext trigger for new static analysis issues, but I can't figure out how to accomplish that. Here's a copy of my question on the wiki page: Can anyone provide more detail about how to accomplish this: In case you want to send notification emails to users introducing new warnings or violations but without failing a build you can use this groovy trigger script for the [Email-Ext Plug-in|]. I've got the Email-Ext plug-in installed and I can see where to add a post-build e-mail to my job and how to add a trigger, but I don't see where I'm supposed to specify the groovy trigger script. It seems like I've only got a specific set of pre-configured e-mail triggers to work with. Also, right now I'm using the static analysis core plugin with checkstyle, pmd, and findbugs, but not the analysis collector plugin. Thanks, --Ryan -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- Website: http://earl-of-code.com -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
(email-ext plugin) e-mail notification for new static analysis issues
Hi, I'm trying to figure out how to configure the email-ext plugin to generate an e-mail whenever someone introduces a new static analysis issue (identified by findbugs, pmd, and checkstyle plugins). I found a mention of this on the static analysis plugin pagehttps://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-insand asked my question there, but Ulli suggested I try the group instead. The plugin page indicates that it is possible to add an email-ext trigger for new static analysis issues, but I can't figure out how to accomplish that. Here's a copy of my question on the wiki page: Can anyone provide more detail about how to accomplish this: In case you want to send notification emails to users introducing new warnings or violations but without failing a build you can use this groovy trigger script for the [Email-Ext Plug-in|]. I've got the Email-Ext plug-in installed and I can see where to add a post-build e-mail to my job and how to add a trigger, but I don't see where I'm supposed to specify the groovy trigger script. It seems like I've only got a specific set of pre-configured e-mail triggers to work with. Also, right now I'm using the static analysis core plugin with checkstyle, pmd, and findbugs, but not the analysis collector plugin. Thanks, --Ryan -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Missing console link
Issue filed: https://issues.jenkins-ci.org/browse/JENKINS-16303 --Ryan
Re: Disappearing build reports
Restarting Jenkins seemed to fix the missing build reports for me... --Ryan On Thu, Jan 10, 2013 at 8:45 AM, rhythmicde...@gmail.com wrote: I believe that I am having the same issue. https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-users/7GZJaajfYvM Did you find any resolution? Steve On Wednesday, January 2, 2013 3:24:56 PM UTC-5, Ryan Shoemaker wrote: Was there an issue filed for this? I'm running 1.492 and noticed the disappearing build issue in a new job I created today (all of our existing jobs seem to behaving normally). Builds of the new job do exist on disk on the Jenkins server, but they aren't showing in the UI. At least not for very long. They appear for a little bit and then disappear. When they do exist, the hover-over context menu only shows a few of the usual options. --Ryan On Tuesday, 23 October 2012 09:49:32 UTC-4, Andrew Melo wrote: Hey everyone, We're on 1.486, but we're still having our build records disappear, did the planned fixes not make it into the release? Thanks, Andrew -- -- Andrew Melo
Missing console link
I posted recently about build reports that would seem to disappear from the UI (even though they were available on the Jenkins filesystem). Restarting seemed to fix that issue, but I'm still having trouble with missing console links. For example, if I hover over the build number on the console, the context menu is missing a link for the console output: https://lh6.googleusercontent.com/-f-4tjqnVosU/UOyUqnbzegI/E4A/AyjSQ7iPjCE/s1600/Screen+Shot+2013-01-08+at+4.50.06+PM.png The only way to get to the console output is by clicking on the job link (ie #13 above) and then following the console output link in the top-left of that page. The console output is available, it just isn't showing up in the context menus for some reason. And it is only behaving this way for a specific job - the context menus for all my other jobs are behaving totally normal. This is a free form job that simply ssh'es into a host periodically, runs a wget command, and then pipes the output back to Jenkins for archival. Is anyone else seeing this? Should I file an issue? Jenkins v1.492 Thanks, --Ryan
Re: Disappearing build reports
Was there an issue filed for this? I'm running 1.492 and noticed the disappearing build issue in a new job I created today (all of our existing jobs seem to behaving normally). Builds of the new job do exist on disk on the Jenkins server, but they aren't showing in the UI. At least not for very long. They appear for a little bit and then disappear. When they do exist, the hover-over context menu only shows a few of the usual options. --Ryan On Tuesday, 23 October 2012 09:49:32 UTC-4, Andrew Melo wrote: Hey everyone, We're on 1.486, but we're still having our build records disappear, did the planned fixes not make it into the release? Thanks, Andrew -- -- Andrew Melo
Empty Aggregated Violations Report
I updated Jenkins and all my plugins last week then created a new job that builds a new branch of our product. I noticed that the aggregated violations chart seems to be broken on the new job, but seems totally normal on the job that builds our main development branch. In order to get a violation delta between the main branch and new branch, I had the job first build the main branch to provide a baseline of the current violations. Then I reconfigured the job to build the new branch and it showed a nice delta between the two jobs (between builds 3 4) and the violations chart looked fine. A few hours later (even though there were no new builds of the job), the chart was empty as shown in the attachment. The individual charts for findbugs, pmd, and checkstyle all seem to be functioning properly though. Sometimes, the aggregated violations chart shows a single build ID on the x axis, sometimes not - even though I have the job configured to not discard any builds. If I click on the checkstyle|pmd|findbugs warnings links in the left column of the job page, they all seem to be working normally and the New Warnings column shows the correct count. However, if I click on the violations link in the left column of the job page, then I see an empty chart and it lists all of the mvn modules in my project and says (didn't run) next to each. I'm wondering if there's an issue with Jenkins or the static analysis plugin, or if my idea of switching branches to get a delta is somehow flawed (I'm pretty sure this has worked for me before). Anyone else seeing this? Should I downgrade my static analysis plugin? Anything else I can/should look for? Thanks, --Ryan attachment: Screen Shot 2012-12-10 at 3.18.30 PM.png
Re: Empty Aggregated Violations Report
Sorry about that - I quickly scanned my installed plugins and assumed static analysis was responsible for generating the violations report. I have installed: Static Analysis Utilities Checkstyle Plug-in Jenkins Violations plugin FindBugs Plug-in PMD Plug-in Warnings Plug-in plus a bunch of others. I have not tried downgrading the violations plugin yet - I was curious if others were seeing the same behavior. Thanks, --Ryan On Monday, 10 December 2012 16:02:15 UTC-5, Ullrich Hafner wrote: The violations plug-in is not part of the static analysis suite. Or are you referring to the analysis collector plug-in? You can try to downgrade the violations plug-in only. Does that help? Ulli Am 10.12.2012 um 21:37 schrieb Ryan Shoemaker ryan.sh...@gmail.comjavascript:: I updated Jenkins and all my plugins last week then created a new job that builds a new branch of our product. I noticed that the aggregated violations chart seems to be broken on the new job, but seems totally normal on the job that builds our main development branch. In order to get a violation delta between the main branch and new branch, I had the job first build the main branch to provide a baseline of the current violations. Then I reconfigured the job to build the new branch and it showed a nice delta between the two jobs (between builds 3 4) and the violations chart looked fine. A few hours later (even though there were no new builds of the job), the chart was empty as shown in the attachment. The individual charts for findbugs, pmd, and checkstyle all seem to be functioning properly though. Sometimes, the aggregated violations chart shows a single build ID on the x axis, sometimes not - even though I have the job configured to not discard any builds. If I click on the checkstyle|pmd|findbugs warnings links in the left column of the job page, they all seem to be working normally and the New Warnings column shows the correct count. However, if I click on the violations link in the left column of the job page, then I see an empty chart and it lists all of the mvn modules in my project and says (didn't run) next to each. I'm wondering if there's an issue with Jenkins or the static analysis plugin, or if my idea of switching branches to get a delta is somehow flawed (I'm pretty sure this has worked for me before). Anyone else seeing this? Should I downgrade my static analysis plugin? Anything else I can/should look for? Thanks, --Ryan Screen Shot 2012-12-10 at 3.18.30 PM.png
Re: CI-Game points issue
I see this at the end of my job logs: [ci-game] evaluating rule: Build result [ci-game] evaluating rule: Increased number of failed tests [ci-game] evaluating rule: Increased number of passed tests [ci-game] evaluating rule: Decreased number of failed tests [ci-game] evaluating rule: Decreased number of passed tests [ci-game] evaluating rule: Open HIGH priority tasks [ci-game] evaluating rule: Open NORMAL priority tasks [ci-game] evaluating rule: Open LOW priority tasks [ci-game] evaluating rule: PMD violation [ci-game] evaluating rule: pylint violation [ci-game] evaluating rule: CPD violation [ci-game] evaluating rule: Checkstyle violation [ci-game] evaluating rule: FindBugs violation [ci-game] evaluating rule: FXCop violation [ci-game] evaluating rule: Simian violation [ci-game] evaluating rule: StyleCop violation [ci-game] evaluating rule: HIGH priority PMD warnings [ci-game] evaluating rule: NORMAL priority PMD warnings [ci-game] evaluating rule: LOW priority PMD warnings [ci-game] evaluating rule: New HIGH priority Findbugs warnings [ci-game] evaluating rule: New NORMAL priority Findbugs warnings [ci-game] evaluating rule: New LOW priority Findbugs warnings [ci-game] evaluating rule: Fixed HIGH priority Findbugs warnings [ci-game] evaluating rule: Fixed NORMAL priority Findbugs warnings [ci-game] evaluating rule: Fixed LOW priority Findbugs warnings [ci-game] evaluating rule: Changed number of compiler warnings [ci-game] evaluating rule: Changed number of checkstyle warnings Finished: SUCCESS But it never assigns a score. Well, the only time is assigns a score is when someone breaks the build - other than that I never see the line [ci-game] scored: 1.0. I also checked the server logs and the only message I see during a build is this: [#|2012-06-22T08:15:49.766-0400|INFO|glassfish3.1.2|hudson.model.Run|_ThreadID=26;_ThreadName=Thread-2;|PCS Master #102 main build action completed: SUCCESS|#] Probably unrelated, but I'm seeing a lot of these when I navigate around the jenkins web pages: [#|2012-06-22T08:19:48.988-0400|WARNING|glassfish3.1.2|hudson.ExpressionFactory2$JexlExpression|_ThreadID=22;_ThreadName=Thread-2;|Caught exception evaluating: job.buildHealth. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException --Ryan On Friday, 22 June 2012 02:41:10 UTC-4, Ulli Hafner wrote: On 06/22/2012 04:00 AM, RShoemaker wrote: I just installed Jenkins 1.466 and ci-game 1.18. All the other plugins I installed are more recent than what's listed in the requirements, but every build says it's worth 0 points and that there were no players. I configured my job to run all the plugins (mvn install checkstyle:checkstyle pmd:pmd findbugs:findbugs) and publish all the results. I include ci-game as a post-build action. The job is currently setup to poll our git repo and it only builds when it notices changes. Jenkins publishes the changes and shows who committed them, so it seems like ci-game should have that info as well. The project is a multi-module maven project. I'm assuming user error on my part - any suggestions? Is there a message from the plug-in in the console log of your job? This is a typical output in our jobs: *21:48:03* [ci-game] evaluating rule: Build result*21:48:03* [ci-game] scored: 1.0*21:48:03* [ci-game] evaluating rule: Increased number of failed tests*21:48:03* [ci-game] evaluating rule: Increased number of passed tests*21:48:03* [ci-game] evaluating rule: Decreased number of failed tests*21:48:03* [ci-game] evaluating rule: Decreased number of passed tests*21:48:03* [ci-game] evaluating rule: Open HIGH priority tasks*21:48:03* [ci-game] evaluating rule: Open NORMAL priority tasks*21:48:03* [ci-game] evaluating rule: Open LOW priority tasks*21:48:03* [ci-game] evaluating rule: HIGH priority PMD warnings*21:48:03* [ci-game] evaluating rule: NORMAL priority PMD warnings*21:48:03* [ci-game] evaluating rule: LOW priority PMD warnings*21:48:03* [ci-game] evaluating rule: New HIGH priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: New NORMAL priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: New LOW priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed HIGH priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed NORMAL priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed LOW priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Changed number of compiler warnings*21:48:03* [ci-game] evaluating rule: Changed number of checkstyle warnings* Ulli* On Friday, 22 June 2012 02:41:10 UTC-4, Ulli Hafner wrote: On 06/22/2012 04:00 AM, RShoemaker wrote: I just installed Jenkins 1.466 and ci-game 1.18. All the other plugins I installed are more recent than what's listed in the requirements, but every build says it's worth 0 points and that there were no players. I
Re: CI-Game points issue
Definitely, but most of our builds should be worth negative points :) All of our trend graphs for todos, findbugs, etc are slowly trending upwards. At a minimum, you should get 1 point for a successful build and it should identify players, but neither of those things are happening --Ryan On Friday, 22 June 2012 10:28:13 UTC-4, William Soula wrote: Just a sanity check, but are you doing anything that would cause a score? Try adding a dummyTest that verifies 2+2=5 and see if you get a score of one for adding a passing test. *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Ryan Shoemaker *Sent:* Friday, June 22, 2012 7:25 AM *To:* jenkinsci-users@googlegroups.com *Subject:* Re: CI-Game points issue I see this at the end of my job logs: [ci-game] evaluating rule: Build result [ci-game] evaluating rule: Increased number of failed tests [ci-game] evaluating rule: Increased number of passed tests [ci-game] evaluating rule: Decreased number of failed tests [ci-game] evaluating rule: Decreased number of passed tests [ci-game] evaluating rule: Open HIGH priority tasks [ci-game] evaluating rule: Open NORMAL priority tasks [ci-game] evaluating rule: Open LOW priority tasks [ci-game] evaluating rule: PMD violation [ci-game] evaluating rule: pylint violation [ci-game] evaluating rule: CPD violation [ci-game] evaluating rule: Checkstyle violation [ci-game] evaluating rule: FindBugs violation [ci-game] evaluating rule: FXCop violation [ci-game] evaluating rule: Simian violation [ci-game] evaluating rule: StyleCop violation [ci-game] evaluating rule: HIGH priority PMD warnings [ci-game] evaluating rule: NORMAL priority PMD warnings [ci-game] evaluating rule: LOW priority PMD warnings [ci-game] evaluating rule: New HIGH priority Findbugs warnings [ci-game] evaluating rule: New NORMAL priority Findbugs warnings [ci-game] evaluating rule: New LOW priority Findbugs warnings [ci-game] evaluating rule: Fixed HIGH priority Findbugs warnings [ci-game] evaluating rule: Fixed NORMAL priority Findbugs warnings [ci-game] evaluating rule: Fixed LOW priority Findbugs warnings [ci-game] evaluating rule: Changed number of compiler warnings [ci-game] evaluating rule: Changed number of checkstyle warnings Finished: SUCCESS But it never assigns a score. Well, the only time is assigns a score is when someone breaks the build - other than that I never see the line [ci-game] scored: 1.0. I also checked the server logs and the only message I see during a build is this: [#|2012-06-22T08:15:49.766-0400|INFO|glassfish3.1.2|hudson.model.Run|_ThreadID=26;_ThreadName=Thread-2;|PCS Master #102 main build action completed: SUCCESS|#] Probably unrelated, but I'm seeing a lot of these when I navigate around the jenkins web pages: [#|2012-06-22T08:19:48.988-0400|WARNING|glassfish3.1.2|hudson.ExpressionFactory2$JexlExpression|_ThreadID=22;_ThreadName=Thread-2;|Caught exception evaluating: job.buildHealth. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException --Ryan On Friday, 22 June 2012 02:41:10 UTC-4, Ulli Hafner wrote: On 06/22/2012 04:00 AM, RShoemaker wrote: I just installed Jenkins 1.466 and ci-game 1.18. All the other plugins I installed are more recent than what's listed in the requirements, but every build says it's worth 0 points and that there were no players. I configured my job to run all the plugins (mvn install checkstyle:checkstyle pmd:pmd findbugs:findbugs) and publish all the results. I include ci-game as a post-build action. The job is currently setup to poll our git repo and it only builds when it notices changes. Jenkins publishes the changes and shows who committed them, so it seems like ci-game should have that info as well. The project is a multi-module maven project. I'm assuming user error on my part - any suggestions? Is there a message from the plug-in in the console log of your job? This is a typical output in our jobs: *21:48:03* [ci-game] evaluating rule: Build result *21:48:03* [ci-game] scored: 1.0 *21:48:03* [ci-game] evaluating rule: Increased number of failed tests *21:48:03* [ci-game] evaluating rule: Increased number of passed tests *21:48:03* [ci-game] evaluating rule: Decreased number of failed tests *21:48:03* [ci-game] evaluating rule: Decreased number of passed tests *21:48:03* [ci-game] evaluating rule: Open HIGH priority tasks *21:48:03* [ci-game] evaluating rule: Open NORMAL priority tasks *21:48:03* [ci-game] evaluating rule: Open LOW priority tasks *21:48:03* [ci-game] evaluating rule: HIGH priority PMD warnings *21:48:03* [ci-game] evaluating rule: NORMAL priority PMD warnings *21:48:03* [ci-game] evaluating rule: LOW priority PMD warnings *21:48
