[JIRA] [join-plugin] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
Steve Roth commented on JENKINS-22348 Join Plugin: intermittent NullPointerException in child project when all downstream projects complete I also saw this issue occur repeatedly, as soon as we moved to dynamic slaves. In case anyone else runs into this, our solution was to add a minor source tweak to remove the requirement that the slave which ran the job using the join-plugin persist until the join plugin downstream project is triggered. I believe this requirement was added when support for CopyArchiver was added. Since we dont use CopyArchiver plugin, this was a simple mod: Our solution was to edit src/main/java/join/JoinAction.java and change final Launcher launcher = new NoopLauncher(listener, owner); to final Launcher launcher = null; This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [jacoco-plugin] (JENKINS-26168) Jacoco plugin: enh to skip the graph generation (good when many runs are kept)
Steve Roth updated JENKINS-26168 Jacoco plugin: enh to skip the graph generation (good when many runs are kept) Change By: Steve Roth (18/Dec/14 11:34 PM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [jacoco-plugin] (JENKINS-26168) Jacoco plugin: enh to skip the graph generation (good when many runs are kept)
Steve Roth created JENKINS-26168 Jacoco plugin: enh to skip the graph generation (good when many runs are kept) Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 18/Dec/14 11:34 PM Description: First off, thanks for the great plugin. This plugin is heavily used in our org, and we really like it. One issue we have seen recently is that sometimes it takes the Jacoco plugin a long time (2.5 minutes) to analyze data/generate the png graph which is presented in the browser, and (due to our proxy) our browsers would timeout when viewing the Jacoco reports. After some investigation, we determined it was due to the # of runs in our job (we have ~80 runs). By reducing the 'max # of builds to keep' down to 7, we are no longer seeing this long delay to analyze data/generate the png graph. Unfortunately, however, reducing our 'max # of builds to keep' down to 7 also means we lose a lot of other data. It would be very handy if there was a way to use the jacoco plugin and simply turn off the png graph generation. That way we could continue to keep 80 runs (to collect data on intermittent test failures), but could still view the Jacoco reports. Project: Jenkins Priority: Major Reporter: Steve Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [delivery-pipeline-plugin] (JENKINS-25899) Delivery Pipeline: request for IFrame so Deliv Pipeline can be inlined in Dashboard View
Steve Roth created JENKINS-25899 Delivery Pipeline: request for IFrame so Deliv Pipeline can be inlined in Dashboard View Issue Type: New Feature Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 03/Dec/14 9:51 PM Description: First off, thanks for a great plugin. In my experience, the delivery pipeline plugin is the best of the several Jenkins pipeline plugins. One feature I think would be really useful to add is the ability to show the delivery pipeline plugin in a dashboard view (from the dashboard view plugin). The dashboard view has a bunch of integrations already that is one option. Another option would be to add an URL so that the delivery pipeline plugin view can be added as an IFrame. (dashboard view plugin supports iframe 'portlets'). Thanks again for the great plugin. Project: Jenkins Priority: Major Reporter: Steve Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [delivery-pipeline-plugin] (JENKINS-25899) Delivery Pipeline: request for IFrame so Deliv Pipeline can be inlined in Dashboard View
Steve Roth updated JENKINS-25899 Delivery Pipeline: request for IFrame so Deliv Pipeline can be inlined in Dashboard View Change By: Steve Roth (03/Dec/14 9:52 PM) Description: Firstoff,thanksforagreatplugin.Inmyexperience,thedeliverypipelinepluginisthebestoftheseveralJenkinspipelineplugins.OnefeatureIthinkwouldbereallyusefultoaddistheabilitytoshowthedeliverypipelineplugininadashboardview(fromthedashboardviewplugin).Thedashboardviewhasabunchof plugin integrationsalready (checkstyle,jacoco,etcetc) -- thatis so oneoption istoaddanewdashboardviewintegration .AnotheroptionwouldbetoaddanURLsothatthedeliverypipelinepluginviewcanbeaddedasanIFrame.(dashboardviewpluginsupportsiframeportlets).Thanksagainforthegreatplugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [naginator] (JENKINS-25037) Naginator: ability to restart pipeline if job fails
Steve Roth created JENKINS-25037 Naginator: ability to restart pipeline if job fails Issue Type: New Feature Assignee: Nicolas De Loof Components: naginator Created: 07/Oct/14 11:10 PM Description: The naginator is a great plugin. One issue we have, however, is that if one of our jobs fails, naginator will rerun it (good!) but if it passes, the Join plugin will not re-trigger. Therefore, our pipeline (which uses the Join plugin) will not re-evaluate its closing 'join' conditions. I'm requesting an enhancement for this case to the Join plugin as well, but IMO it would be great if Naginator had an option to retrigger the full pipeline. That would also address this issue. Project: Jenkins Priority: Major Reporter: Steve Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [schedule-failed-builds] (JENKINS-7604) When used with the Join plugin, the retry break the job flow
Steve Roth commented on JENKINS-7604 When used with the Join plugin, the retry break the job flow We have the same issue. It seems when the Naginator (build retry) plugin retries a job, and the job succeeds, the Join plugin does not re-evaluate the ending Join condition. So you can end up with all of your pipeline jobs passing, yet not have your Join condition evaluated. It would be really great if this feature was added. Without this, we are considering the option of automatically detecting stalled pipelines and re-triggering them. This will work, but will consume a lot more resources and be much slower than if this could be fixed in the Join plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-24306) Jenkins 1.575 regression? Empty build list, but trend shows builds. Stackoverflow in console
Steve Roth created JENKINS-24306 Jenkins 1.575 regression? Empty build list, but trend shows builds. Stackoverflow in console Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 18/Aug/14 4:19 PM Description: Since upgrading to Jenkins 1.575 I have now seen two cases in which jobs are shown with an empty build list (complete with a more... button), yet the trend link shows builds. When the main project page is loaded, I also see stack overflows in the console. The console shows the following stack overflow (repeatable): Aug 18, 2014 8:41:28 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.renderList in /view/aaa/view/bbb/view/ccc/job/ddd.MAIN/buildHistory/all. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor742.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:94) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[JIRA] [core] (JENKINS-24306) Jenkins 1.575 regression? Empty build list, but trend shows builds. Stackoverflow in console
Steve Roth
commented on JENKINS-24306
Jenkins 1.575 regression? Empty build list, but trend shows builds. Stackoverflow in console
On reverting to Jenkins 1.574, the jobs which previously experienced this issue are once again showing build records. So this appears it may be a regression in 1.575.
Possibly relevant: We are using a separate build record root directory, on a NFS server.
Jenkins is configured to use it as follows:
Workspace Root Directory: /foo/jenkinsworkspace/${ITEM_FULLNAME}
This is a local directory
Build Record Root Directory: /foo/jenkinsarchive/${ITEM_FULLNAME}/builds
where /foo/jenkinsarchive is a symlink to a NFS server directory. So the Build Record Root directory is actually on our NFS server.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [core] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Steve Roth commented on JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream I have not seen this in more than a month closing. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22205) Jenkins failed to rotate log error -- unable to delete .nfsxxxxx file with NAS Build Record Root directory
Steve Roth closed JENKINS-22205 as Cannot Reproduce Jenkins failed to rotate log error -- unable to delete .nfsx file with NAS Build Record Root directory Change By: Steve Roth (09/Jul/14 3:02 AM) Status: Open Closed Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22205) Jenkins failed to rotate log error -- unable to delete .nfsxxxxx file with NAS Build Record Root directory
Steve Roth commented on JENKINS-22205 Jenkins failed to rotate log error -- unable to delete .nfsx file with NAS Build Record Root directory I have not seen this issue in more than a month closing as CNR. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Steve Roth closed JENKINS-21905 as Cannot Reproduce intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream Change By: Steve Roth (09/Jul/14 3:01 AM) Status: Open Closed Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-23721) fix out-of-order builds does not use custom build record root dir
Steve Roth
created JENKINS-23721
fix out-of-order builds does not use custom build record root dir
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
09/Jul/14 3:10 AM
Description:
Using version 1.570 along with a custom build record root dir (under configure system, at the top, under advanced...) I noticed that the 'fix out-of-order builds' action is not using the custom build record root dir.
Settings:
home dir: /foo/jenkins
workspace root dir: /foo/jenkinsworkspace/${ITEM_FULLNAME}
build record root dir: /foo/jenkinsarchive/${ITEM_FULLNAME}/builds
Output example:
Renaming /foo/jenkinsarchive/somejob/builds/2014-03-03_20-00-42
- /foo/jenkins/jobs/somejob/outOfOrderBuilds/2014-03-03_20-00-42
Project:
Jenkins
Priority:
Minor
Reporter:
Steve Roth
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [join] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
Steve Roth created JENKINS-22348 Join Plugin: intermittent NullPointerException in child project when all downstream projects complete Issue Type: Bug Affects Versions: current Assignee: mdonohue Components: join Created: 25/Mar/14 9:53 PM Description: Using Jenkins 1.552 and Join Plugin 1.15, today we saw an intermittent NPE in Join plugin when the last child job completed, and the parent job was being notified of job completion. ... No emails were triggered. Notifying upstream build somejob #308 of job completion All downstream projects complete! FATAL: null java.lang.NullPointerException at join.JoinAction$NoopLauncher.init(JoinAction.java:120) at join.JoinAction.checkPendingDownstream(JoinAction.java:92) at join.JoinAction.downstreamFinished(JoinAction.java:70) at join.JoinDependency.shouldTriggerBuild(JoinDependency.java:45) at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:213) at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.cleanUp(Build.java:194) at hudson.model.Run.execute(Run.java:1715) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Project: Jenkins Priority: Major Reporter: Steve Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [join] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
Steve Roth updated JENKINS-22348 Join Plugin: intermittent NullPointerException in child project when all downstream projects complete shows how upstream job was configured to use join plugin Change By: Steve Roth (25/Mar/14 9:55 PM) Attachment: joinPlugin1.png Attachment: joinPlugin2.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-21579) Very slow resource loading from UberClassLoader
Steve Roth commented on JENKINS-21579 Very slow resource loading from UberClassLoader I cannot say with certainty, but I think this started appearing in 1.553. I dont think I have seen this since reverting to 1.552. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22205) Jenkins failed to rotate log error -- unable to delete .nfsxxxxx file with NAS Build Record Root directory
Steve Roth commented on JENKINS-22205 Jenkins failed to rotate log error -- unable to delete .nfsx file with NAS Build Record Root directory Given the .nfs file location at jenkinsarchive/SomeJob/builds/.2014-03-15_19-19-58/.nfs0009e0cc03c4 it appears the original file location (of the file which was removed) was in the dot-date directory at jenkinsarchive/SomeJob/builds/.2014-03-15_19-19-58 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Steve Roth commented on JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream Thanks Jesse. I've been able to capture artifacts for two cases in which archiving subsequently failed with this exception. Unfortunately, I cannot repro the issue in a test job by unpacking and archiving. Is there any logging I can enable which might be helpful in identifying the underlying issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Steve Roth edited a comment on JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream Thanks Jesse. I've been able to capture artifacts for two cases in which archiving subsequently failed with this exception. Unfortunately, I cannot repro the issue in a test job by unpacking and archiving. So it seems like there might be more to this issue than just the file-to-archive structure. Is there any logging I can enable which might be helpful in identifying the underlying issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22205) Jenkins failed to rotate log error -- unable to delete .nfsxxxxx file with NAS Build Record Root directory
Steve Roth
created JENKINS-22205
Jenkins failed to rotate log error -- unable to delete .nfsx file with NAS Build Record Root directory
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
16/Mar/14 5:42 AM
Description:
Summary:
When Jenkins results are stored on a NAS location, we are seeing very frequent errors (100x/day) when log rotation runs after a job completes. These appear to be a very small (4-second or less) race condition when using NAS storage.
The net effect is that log rotation does not appear to work properly, at least from the Jenkins perspective, resulting in increasing build records over time.
The typical symptom, as seen in the Jenkins console, is:
Mar 15, 2014 10:38:32 PM hudson.model.Run execute
SEVERE: Failed to rotate log
java.io.IOException: Unable to delete /zzz/jenkinsarchive/SomeJob/builds/.2014-03-15_20-32-56/.nfs011886413187
at hudson.Util.deleteFile(Util.java:254)
at hudson.Util.deleteRecursive(Util.java:301)
at hudson.Util.deleteContentsRecursive(Util.java:203)
at hudson.Util.deleteRecursive(Util.java:300)
at hudson.model.Run.delete(Run.java:1452)
at hudson.tasks.LogRotator.perform(LogRotator.java:124)
at hudson.model.Job.logRotate(Job.java:440)
at hudson.model.Run.execute(Run.java:1739)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
More Details:
==
We have a good-sized Jenkins install, with several hundred jobs, and due to the archiving size requirements and large # of jobs, we are archiving results to a NAS location.
The Jenkins Build Record Root Directory option is configured to /zzz/jenkinsarchive/${ITEM_FULLNAME}/builds
Where /zzz/jenkinsarchive is a symlink to a mount-point location, such as /mnt/foo.com/export/foo/bar/jenkinsarchive
So records are written to /zzz/jenkinsarchive/SomeJob/builds/... which really evaluates to /mnt/foo.com/export/foo/bar/jenkinsarchive/SomeJob/builds/...
My understanding of .nfs lock files is that they appear on the NAS when a NAS file is unlinked but is still open by a NFS client. (presumably in this case, Jenkins).
Using lsof -n -P -N -u someUser -a I can see that normally we have 2 files in-use on the NAS one at
jenkinsarchive/SomeJob/builds/2014-03-15_19-19-58/log
and one at
jenkinsarchive/SomeJob/builds/2014-03-15_19-19-58/timestamper/timestamps
but for very short periods of time, when log rotation runs, I see a files at a path like
jenkinsarchive/SomeJob/builds/.2014-03-15_19-19-58/.nfs0009e0cc03c4
exist. It appears to only exist for a couple seconds.
So it seems that something in Jenkins is keeping access open to these files, which then (per NFS semantics) is preventing deletion at the time of the stack trace above.
Project:
Jenkins
Priority:
Major
Reporter:
Steve Roth
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [core] (JENKINS-22205) Jenkins failed to rotate log error -- unable to delete .nfsxxxxx file with NAS Build Record Root directory
Steve Roth commented on JENKINS-22205 Jenkins failed to rotate log error -- unable to delete .nfsx file with NAS Build Record Root directory We have seen this issue for awhile, including using the most recent 1.554 version of Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22205) Jenkins failed to rotate log error -- unable to delete .nfsxxxxx file with NAS Build Record Root directory
Steve Roth commented on JENKINS-22205 Jenkins failed to rotate log error -- unable to delete .nfsx file with NAS Build Record Root directory Using lsof, I've noticed that most of the time, there are files open to NAS paths of the form .../jenkinsarchive/SomeJob/builds/2014-03-15_21-00-56/... but for very short periods of time, there are files open to NAS paths of the form .../jenkinsarchive/SomeJob/builds/.2014.../ I interpret this as a potential rename from the earlier format to the secondary format. I wonder if this rename might account for the NFS lock behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-22205) Jenkins failed to rotate log error -- unable to delete .nfsxxxxx file with NAS Build Record Root directory
Steve Roth commented on JENKINS-22205 Jenkins failed to rotate log error -- unable to delete .nfsx file with NAS Build Record Root directory In case it is relevant, I am seeing large numbers of these builds/.2014-xxx directories exist, across our jobs, for days/weeks-- approximately 16000. I suspect this is not expected, so I wanted to mention it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-21579) Very slow resource loading from UberClassLoader
Steve Roth commented on JENKINS-21579 Very slow resource loading from UberClassLoader I am seeing this as well, on 1.553, but without the cloudbees-template plugin installed. Handling GET /job/something/configure : http-bio-5269-exec-1805" daemon prio=5 RUNNABLE java.lang.Throwable.fillInStackTrace(Native Method) java.lang.Throwable.init(Throwable.java:196) java.lang.Exception.init(Exception.java:41) javax.naming.NamingException.init(NamingException.java:109) javax.naming.NameNotFoundException.init(NameNotFoundException.java:33) org.apache.naming.resources.BaseDirContext.lookup(BaseDirContext.java:500) org.apache.naming.resources.ProxyDirContext.lookup(ProxyDirContext.java:308) org.apache.catalina.loader.WebappClassLoader.findResources(WebappClassLoader.java:1315) java.lang.ClassLoader.getResources(ClassLoader.java:1040) java.lang.ClassLoader.getResources(ClassLoader.java:1036) java.lang.ClassLoader.getResources(ClassLoader.java:1036) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103) hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:598) java.lang.ClassLoader.getResources(ClassLoader.java:1040) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103) hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:598) java.lang.ClassLoader.getResources(ClassLoader.java:1040) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103) hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:598) java.lang.ClassLoader.getResources(ClassLoader.java:1040) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103) hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:598) java.lang.ClassLoader.getResources(ClassLoader.java:1040) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) jenkins.ClassLoaderReflectionToolkit._findResources(ClassLoaderReflectionToolkit.java:103) hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:598) java.lang.ClassLoader.getResources(ClassLoader.java:1040) org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957)
[JIRA] [core] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Steve Roth created JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 21/Feb/14 12:39 AM Description: Since approximately 1/30 we have seen 15 very intermittent archiving failures in Jenkins, of the form: Archiving artifacts ERROR: Failed to archive artifacts: versions/**, archive/** java.io.IOException: Failed to extract /foo/bar/slave/workspace/someJob/transfer of 7 files at hudson.FilePath.readFromTar(FilePath.java:2088) at hudson.FilePath.copyRecursiveTo(FilePath.java:2000) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1695) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.EOFException: Unexpected end of ZLIB input stream at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:186) at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257) at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223) at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228) at hudson.FilePath.readFromTar(FilePath.java:2066) ... 12 more Build step 'Archive the artifacts' changed build result to FAILURE We definitely have seen this running 1.549 and later. I cannot confirm if we saw it with 1.548 or earlier, but I think it was less frequent. It seems to be a relatively new issue we are seeing. Project: Jenkins Priority: Major Reporter: Steve Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-19473) failed to archive slave artifacts. Unexpected end of ZLIB input stream
Steve Roth commented on JENKINS-19473 failed to archive slave artifacts. Unexpected end of ZLIB input stream @fommil I am seeing the same thing, and have created bug JENKINS-21905 for that issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Steve Roth commented on JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream I saw JENKINS-19473, but this seems to be a different issue. The caused by clause is different. in that case, it was a java.lang.ArrayIndexOutOfBoundsException This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Steve Roth
updated JENKINS-21905
intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Change By:
Steve Roth
(21/Feb/14 12:42 AM)
Description:
Sinceapproximately1/30wehaveseen15veryintermittentarchivingfailuresinJenkins,oftheform:{noformat}ArchivingartifactsERROR:Failedtoarchiveartifacts:versions/**,archive/**java.io.IOException:Failedtoextract/foo/bar/slave/workspace/someJob/transferof7files athudson.FilePath.readFromTar(FilePath.java:2088) athudson.FilePath.copyRecursiveTo(FilePath.java:2000) atjenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) athudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756) athudson.model.Build$BuildExecution.post2(Build.java:183) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) athudson.model.Run.execute(Run.java:1695) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)Causedby:java.io.EOFException:UnexpectedendofZLIBinputstream atcom.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:186) atcom.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) atorg.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257) atorg.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223) athudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228) athudson.FilePath.readFromTar(FilePath.java:2066) ...12moreBuildstepArchivetheartifactschangedbuildresulttoFAILURE{noformat}Wedefinitelyhaveseenthisrunning1.
549
548
andlater
,especiallywith1
.
549.
Icannotconfirmifwesawitwith1.
548
547
orearlier,but
ifso,
Ithinkitwaslessfrequent.Itseemstobearelativelynewissueweareseeing.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [core] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Steve Roth commented on JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream Forgot to mention, we are seeing this even in the latest Jenkins version (1.551) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-6096) lastSuccessfulBuild symlink isn't being created anymore
Steve Roth commented on JENKINS-6096 lastSuccessfulBuild symlink isnt being created anymore We are seeing this as well Jenkins 1.38, Build Publisher 1.17. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-18238) Symbolic link is not updated after publishing build
Steve Roth commented on JENKINS-18238 Symbolic link is not updated after publishing build We are seeing this as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [external-monitor-job] (JENKINS-18891) Monitor External Jobs: username containing @ (at sign) not supported
Steve Roth commented on JENKINS-18891 Monitor External Jobs: username containing @ (at sign) not supported I see a comment in https://wiki.jenkins-ci.org/display/JENKINS/Monitoring+external+jobs from zhewei shou on 4/24/2012 indicating the same issue: Apr 24, 2012 zhewei shou says: when i export JENKINS_HOME(which is not localhost path), i need pass username password. but what can i do if the password exists character like '@'? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [external-monitor-job] (JENKINS-18891) Monitor External Jobs: username containing @ (at sign) not supported
Steve Roth created JENKINS-18891 Monitor External Jobs: username containing @ (at sign) not supported Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: external-monitor-job Created: 23/Jul/13 2:41 PM Description: From what I can tell (using Jenkins 1.518), the 'monitor external jobs' feature does not support usernames containing the @ (at sign) character. This is a big problem for us, since we use LDAP auth, and all our usernames contain the @ sign. When I use this sequence: export JENKINS_HOME=https://f...@bar.com:sec...@somebox.bar.com java jar /somepath/jenkins-core*.jar "somejob" pwd I get this exception: java.net.MalformedURLException: For input string: "sec...@somebox.bar.com" at java.net.URL.init(URL.java:601) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at hudson.Main.remotePost(Main.java:93) at hudson.Main.run(Main.java:74) at hudson.Main.main(Main.java:56) If there was a way to support multiple auth providers, then this would not be a big deal, since we could store our 'automation users' (the users we would use for monitoring external jobs) in Jenkins and use LDAP for the rest of the users. However, this does not appear to be an option. Project: Jenkins Priority: Major Reporter: Steve Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0
style=background-color:#ff;border:1px solid
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;
table align=left border=0 cellpadding=0 cellspacing=0
width=100% style=width:100%;
tr valign=top
td
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar
src=https://issues.jenkins-ci.org/secure/useravatar?avatarId=10292; alt=
height=48 width=48 border=0 align=left style=padding:0;margin: 0 16px
16px 0; /
div id=email-action style=padding: 0 0 8px
0;font-size:12px;line-height:18px;
a class=user-hover rel=sroth
id=email_sroth
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=sroth;
style=color:#355564;Steve Roth/a
commented on img src=https://issues.jenkins-ci.org/images/icons/bug.gif;
height=16 width=16 border=0 align=absmiddle alt=Bug a
style='color:#355564;text-decoration:none;'
href='https://issues.jenkins-ci.org/browse/JENKINS-10876'JENKINS-10876/a
/div
div
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0
style=background-color:#ff;border:1px solid
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;
table align=left border=0 cellpadding=0 cellspacing=0
width=100% style=width:100%;
tr valign=top
td
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar
src=https://issues.jenkins-ci.org/secure/useravatar?avatarId=10292; alt=
height=48 width=48 border=0 align=left style=padding:0;margin: 0 16px
16px 0; /
div id=email-action style=padding: 0 0 8px
0;font-size:12px;line-height:18px;
a class=user-hover rel=sroth
id=email_sroth
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=sroth;
style=color:#355564;Steve Roth/a
commented on img src=https://issues.jenkins-ci.org/images/icons/bug.gif;
height=16 width=16 border=0 align=absmiddle alt=Bug a
style='color:#355564;text-decoration:none;'
href='https://issues.jenkins-ci.org/browse/JENKINS-10875'JENKINS-10875/a
/div
div
[JIRA] (JENKINS-12123) Emma - Coverage results = 0 causes error in the reports
Steve Roth commented on JENKINS-12123 Emma - Coverage results = 0 causes error in the reports Thanks Dan reviewing the cases, I was actually seeing it when there was no coverage reported in some of the view jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15552) envinject plugin v1.72 might be incompatible with Jenkins v.1486
Steve Roth commented on JENKINS-15552 envinject plugin v1.72 might be incompatible with Jenkins v.1486 I should clarify, in case it is relevant I normally dont restart all of the slaves every time I restart the master. In this case all the slaves were already running their listener processes. In this repro process, I restarted only the master. I can consistently repro this issue every time I restart the master. Still happening with Jenkins 1.492 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12123) Emma - Coverage results = 0 causes error in the reports
Steve Roth edited a comment on JENKINS-12123 Emma - Coverage results = 0 causes error in the reports I would bump up the priority on this, since rendering a view is extremely slow when these NPE are occurring. If I remove the emma column from the view config, then it renders almost instantaneously. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12123) Emma - Coverage results = 0 causes error in the reports
Steve Roth commented on JENKINS-12123 Emma - Coverage results = 0 causes error in the reports I would bump up the priority on this, since rendering a view is extremely slow when these NPE are occurring. I remove the emma column from the view config, then it renders almost instantaneously. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12123) Emma - Coverage results = 0 causes error in the reports
Steve Roth commented on JENKINS-12123 Emma - Coverage results = 0 causes error in the reports I am seeing this as well logfile shows: Dec 2, 2012 2:13:58 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.getPercent(job). Reason: java.lang.NullPointerException java.lang.NullPointerException at jenkins.plugins.emmacoveragecolumn.EmmaColumn.getPercentageFloat(EmmaColumn.java:82) at jenkins.plugins.emmacoveragecolumn.EmmaColumn.getLinePercent(EmmaColumn.java:66) at jenkins.plugins.emmacoveragecolumn.EmmaColumn.getPercent(EmmaColumn.java:37) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15552) envinject plugin v1.72 might be incompatible with Jenkins v.1486
Steve Roth commented on JENKINS-15552 envinject plugin v1.72 might be incompatible with Jenkins v.1486 I am seeing this during the start process, when the slaves are coming online (we have approx 20 slaves). So I also suspect it may be related to the slaves. My server is on Centos6, but the startup messages are similar: Summary: 1) a bunch of 'xxx monitoring activity is still in progress. Interrupting' messages 2) a bunch of 'Node monitoring someslave for xxx aborted' messages w/InterruptedExceptions 3) a few warnings of the form WARNING: Failed to monitor someslave for XXX due to IOException: remote file operation failed due to failed to deserialize the Callable object followed by 4) WARNING: Failed to monitor someslave for XXX due to InvalidClassException: ... local class incompatible: stream classdesc serialVersionUID Details: Nov 21, 2012 8:02:01 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record init WARNING: Previous Architecture monitoring activity still in progress. Interrupting Nov 21, 2012 8:02:01 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record init WARNING: Previous Clock Difference monitoring activity still in progress. Interrupting Nov 21, 2012 8:02:01 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record init ...etc ... WARNING: Previous Clock Difference monitoring activity still in progress. Interrupting Nov 21, 2012 8:02:00 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run WARNING: Node monitoring slave1 for Architecture aborted. java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:146) at hudson.remoting.Channel.call(Channel.java:665) at hudson.node_monitors.ArchitectureMonitor$DescriptorImpl.monitor(ArchitectureMonitor.java:43) at hudson.node_monitors.ArchitectureMonitor$DescriptorImpl.monitor(ArchitectureMonitor.java:40) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:219) Nov 21, 2012 8:02:01 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run WARNING: Node monitoring master for Response Time aborted. java.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1024) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1303) at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:227) at java.util.concurrent.FutureTask.get(FutureTask.java:91) at hudson.remoting.LocalChannel$2.get(LocalChannel.java:81) at hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:60) at hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:52) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:219) Nov 21, 2012 8:02:01 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run WARNING: Node monitoring slave2 for Free Swap Space aborted. ...etc... Nov 21, 2012 8:02:01 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run WARNING: Node monitoring slave2 for Free Disk Space aborted. java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:146) at hudson.remoting.Channel.call(Channel.java:665) at hudson.FilePath.act(FilePath.java:841) at hudson.FilePath.act(FilePath.java:825) at hudson.node_monitors.DiskSpaceMonitor$1.getFreeSpace(DiskSpaceMonitor.java:71) at hudson.node_monitors.DiskSpaceMonitorDescriptor.monitor(DiskSpaceMonitorDescriptor.java:169) at hudson.node_monitors.DiskSpaceMonitorDescriptor.monitor(DiskSpaceMonitorDescriptor.java:49) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:219) Nov 21, 2012 8:02:01 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run WARNING: Failed to monitor slave3 for Free Temp Space hudson.util.IOException2: remote file operation failed: /scratch/jslave at hudson.remoting.Channel@557d2390:slave3 at hudson.FilePath.act(FilePath.java:848) at hudson.FilePath.act(FilePath.java:825) at hudson.node_monitors.TemporarySpaceMonitor$1.getFreeSpace(TemporarySpaceMonitor.java:73) at
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Steve Roth commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space me too, on 1.491 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15552) envinject plugin v1.72 might be incompatible with Jenkins v.1486
Steve Roth commented on JENKINS-15552 envinject plugin v1.72 might be incompatible with Jenkins v.1486 me too. version 1.488 with the following plugins installed: External Monitor Job Type Plugin 1.1 LDAP Plugin 1.1 pam-auth 1.0 javadoc 1.0 ant 1.1 Macro Plugin 1.5.1 Config File Provider Plugin 2.2.1 Dashboard View 2.3 Jenkins Emma plugin 1.29 Emma Line Coverage Column 0.0.4 Safe Restart Plugin 0.2 Show Build Parameters plugin 1.0 Sectioned View Plugin 1.16 Purge Build Queue Plugin 1.0 Hudson Xvnc plugin 1.10 Compact Columns 1.9 Shelve Project Plugin 1.3 Progress Bar Column Plugin 1.0 Audit Trail 1.7 Jenkins DocLinks plugin 0.5 Log Parser Plugin 1.0.8 Console Column Plugin 1.5 Jenkins Parameterized Trigger plugin 2.16 Jenkins Email Extension Plugin 2.24.1 Jenkins GIT plugin 1.1.25 Change Log History 1.3 Jenkins Environment File Plugin 1.2 Slave Monitor for system load average 1.2 Jenkins Version Column plugin 0.2 Dump Info BuildWrapper Plugin 1.1 Claim Plugin 1.7 Sidebar Link 1.6 Hudson Setenv Plugin 1.1 Priority Sorter 1.3 Job Import Plugin 1.0 Project Health Report 1.2 Periodic Reincarnation of failed jobs 1.0 Run Condition Plugin 0.10 Jenkins SSH Slaves plugin 0.21 Build Keeper Plugin 1.3 Multiline Views TabBar Plugin 1.1 Performance plugin 1.8 Rebuild Plugin 1.15 Favorite 1.13 xUnit plugin 1.50 Hudson Build-Publisher plugin 1.13 Jenkins build log file size checker plugin 1.0 Jenkins disk-usage plugin 0.18 Monitoring 1.41.0 Hudson global-build-stats plugin 1.3 build-metrics 1.0 Jenkins Job Configuration History Plugin 1.13 Drop Down ViewsTabBar Plugin 1.6 Jenkins build timeout plugin 1.11 Project statistics Plugin 0.4 Fortify 360 Plugin 2.4 Keyboard Shortcuts Plugin 1.2 Bulk Builder 1.5 Downstream build view 1.8 View Job Filters 1.22 Description Column Plugin 1.3 Nested View Plugin 1.9 Jenkins Throttle Concurrent Builds Plug-in 1.7.2 Jenkins Workspace Cleanup Plugin 0.10 scripttrigger 0.21 excludeMatrixParent 1.1 Extra Columns Plugin 1.6 Timestamper 1.3.2 Jenkins Translation Assistance plugin 1.10 Labeled Test Groups Publisher 1.2.7-SNAPSHOT (private build) Retry Failed Builds 1.1 Thread Dump Action Plugin 1.0 Jenkins SLOCCount Plug-in 1.8 Configuration Slicing plugin 1.36 AnchorChain 1.0 Jenkins promoted builds plugin 2.8 HTML Publisher plugin 1.0 built-on-column 1.1 Copy Artifact Plugin 1.25 Job Poll Action Plugin 1.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
Steve Roth commented on JENKINS-13114 dropdown views taskbar: error when saving jenkins config page Jesse, thanks for the fix! I apologize for the delay in responding I missed the update. I am no longer seeing this issue in Jenkins 1.477. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14613) Maven job config page loses 'invoke top-level maven targets' setting for 'use private repository'
Steve Roth created JENKINS-14613 Maven job config page loses invoke top-level maven targets setting for use private repository Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 27/Jul/12 11:14 PM Description: Using Jenkins 1.473, I am seeing an issue in a Maven project, when I use the 'Invoke top-level Maven targets' pre-build step. When I add this pre-biuld step, it comes with the 'Use private Maven repository' option checked. If I uncheck this option, and save the job, when I re-open the job, I see it is checked again. So it appears that the config page is losing my persisted setting, and always setting it back to the checked mode. The net result is that if you are using the 'Invoke top-level Maven targets' pre-build step, and dont the 'use private mavne repository' option checked, then each time you change your maven job, you need to go and uncheck that option before you click save. Project: Jenkins Priority: Minor Reporter: Steve Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14585) Test Failure Claim Link not present for Maven test results
Steve Roth created JENKINS-14585 Test Failure Claim Link not present for Maven test results Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: claim, maven Created: 26/Jul/12 4:03 PM Description: First, thanks for this great plugin. This seems to work great for Freestyle projects. We're seeing an issue, however, when using it with Maven projects. In particular, although it is possible to claim build failures, it does not seem to be possible to claim test failures in the maven results the 'claim' link is not present, nor is the text saying this test has not yet been claimed, even though we have enabled the 'allow claiming of failed tests' in our job configuration. Project: Jenkins Priority: Minor Reporter: Steve Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10787) Dashboard view does not display Dropdownviews taskbar
[ https://issues.jenkins-ci.org/browse/JENKINS-10787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163365#comment-163365 ] Steve Roth commented on JENKINS-10787: -- This is no longer an issue in Jenkins 1.454 -- thanks for the fix! Dashboard view does not display Dropdownviews taskbar - Key: JENKINS-10787 URL: https://issues.jenkins-ci.org/browse/JENKINS-10787 Project: Jenkins Issue Type: Bug Components: dashboard-view Affects Versions: current Reporter: Steve Roth Assignee: Peter Hayes Priority: Minor When the DropDownViews taskbar is enabled and selected, the dashboard view does not display using it -- it uses the standard tab approach. This causes issues in some cases such as when lots of sub-views are configured, since the width of the page is huge, and therefore the dashboard portlets are also huge, and require scrolling to see all of the columns. Occurs in Jenkins 1.424 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10787) Dashboard view does not display Dropdownviews taskbar
[ https://issues.jenkins-ci.org/browse/JENKINS-10787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Roth resolved JENKINS-10787. -- Resolution: Cannot Reproduce This is no longer an issue with Jenkins 1.454 Dashboard view does not display Dropdownviews taskbar - Key: JENKINS-10787 URL: https://issues.jenkins-ci.org/browse/JENKINS-10787 Project: Jenkins Issue Type: Bug Components: dashboard-view Affects Versions: current Reporter: Steve Roth Assignee: Peter Hayes Priority: Minor When the DropDownViews taskbar is enabled and selected, the dashboard view does not display using it -- it uses the standard tab approach. This causes issues in some cases such as when lots of sub-views are configured, since the width of the page is huge, and therefore the dashboard portlets are also huge, and require scrolling to see all of the columns. Occurs in Jenkins 1.424 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13968) Dashboard plugin: request for failing jobs portlet
Steve Roth created JENKINS-13968: Summary: Dashboard plugin: request for failing jobs portlet Key: JENKINS-13968 URL: https://issues.jenkins-ci.org/browse/JENKINS-13968 Project: Jenkins Issue Type: Improvement Components: dashboard-view Reporter: Steve Roth Assignee: Peter Hayes Priority: Minor The dashboard-view plugin is really nice. One thing which would be helpful for our team is have a portlet very similar to the 'unstable jobs' portlet, which shows only failing jobs (red ball jobs). This is high priority information, and it's useful to show it in the dashboard. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
[
https://issues.jenkins-ci.org/browse/JENKINS-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162840#comment-162840
]
Steve Roth commented on JENKINS-13114:
--
This is preventing our sites (which have many views) from upgrading to a
Jenkins version newer than 1.454. I presume others with many views may be in
the same situation.
dropdown views taskbar: error when saving jenkins config page
-
Key: JENKINS-13114
URL: https://issues.jenkins-ci.org/browse/JENKINS-13114
Project: Jenkins
Issue Type: Bug
Components: dropdown-viewstabbar
Affects Versions: current
Reporter: Steve Roth
Assignee: jieryn
I have the dropdown views tabbar enabled, and am usign Jenkins 1.455 When I
go to save the main Jenkins config page, I see this CNF exception in the
browser:
exception
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to
instantiate class hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:605)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
org.kohsuke.stapler.Stapler.service(Stapler.java:159)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
oracle.boulderlabs.jenkins.validatorkiller.ValidatorKiller.doFilter(ValidatorKiller.java:63)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
root cause
java.lang.IllegalArgumentException: Failed to instantiate class
hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
[JIRA] (JENKINS-11716) Renaming a job does not rename the build record root dir, for a Jenkins instance configured with this feature
[ https://issues.jenkins-ci.org/browse/JENKINS-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161869#comment-161869 ] Steve Roth commented on JENKINS-11716: -- This is still an issue with Jenkins v1.454. Renaming a job does not rename the build record root dir, for a Jenkins instance configured with this feature - Key: JENKINS-11716 URL: https://issues.jenkins-ci.org/browse/JENKINS-11716 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: Steve Roth We have a Jenkins instance (1.438) using the 'Build Record Root Directory' feature, so we can specify an alternate directory for storing build artifacts outside of the JENKINS HOME directory. This generally works fine. However, I noticed that when I rename a job, I lose the previous build records. I see a new build record directory is created, beneath the specified 'Build Record Root Directory'. However, the old build directory also exists, containing the previous records. They are not moved over to the new directory. In other words, when the 'Build Record Root Directory' feature is enabled, renaming a project causes the project's build records to be lost. Current workaround is to move the build record files over and use sed to replace the project name in them, then restart Jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11716) When 'Build Record Root Directory' is enabled, renaming a job does not create a new BRRD dir for the renamed job, and does not rename/copy artifacts from the original BRRD
[
https://issues.jenkins-ci.org/browse/JENKINS-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Roth updated JENKINS-11716:
-
Summary: When 'Build Record Root Directory' is enabled, renaming a job
does not create a new BRRD dir for the renamed job, and does not rename/copy
artifacts from the original BRRD (was: Renaming a job does not rename the
build record root dir, for a Jenkins instance configured with this feature)
Description:
We have a Jenkins instance (1.438) using the 'Build Record Root Directory'
feature, so we can specify an alternate directory for storing build artifacts
outside of the JENKINS HOME directory.
The 'Build Record Root Directory' (set in configure system, then click
Advanced... button at the top), is set to
/scratch/jbuildroot/${ITEM_FULLNAME}/builds. The Workspace Root dir is set to
${ITEM_ROOTDIR}/workspace.
This generally works fine. However, I noticed that when I rename a job, I lose
the previous build records.
I see a new build record directory is created, beneath the specified 'Build
Record Root Directory'. However, the old build directory also exists,
containing the previous records. They are not moved over to the new directory.
In other words, when the 'Build Record Root Directory' feature is enabled,
renaming a project causes the project's build records to be lost.
Current workaround is to move the build record files over and use sed to
replace the project name in them, then restart Jenkins.
was:
We have a Jenkins instance (1.438) using the 'Build Record Root Directory'
feature, so we can specify an alternate directory for storing build artifacts
outside of the JENKINS HOME directory.
This generally works fine. However, I noticed that when I rename a job, I lose
the previous build records.
I see a new build record directory is created, beneath the specified 'Build
Record Root Directory'. However, the old build directory also exists,
containing the previous records. They are not moved over to the new directory.
In other words, when the 'Build Record Root Directory' feature is enabled,
renaming a project causes the project's build records to be lost.
Current workaround is to move the build record files over and use sed to
replace the project name in them, then restart Jenkins.
I noticed that in Jenkins v1.454, renaming a job does not even create the build
record root dir entry. For example, if I have build record root dir set to
/scratch/jbuildroot/${ITEM_FULLNAME}/builds and I rename a job 'foo' to 'bar',
then /scratch/jbuildroot/foo exists, but the rename does not create
/scratch/jbuildroot/bar.
I think in a previous version, this directory was at least created (though it
was empty), but in v1.454, I dont see it created anymore.
Updating the summary to reflect the new information.
When 'Build Record Root Directory' is enabled, renaming a job does not create
a new BRRD dir for the renamed job, and does not rename/copy artifacts from
the original BRRD
---
Key: JENKINS-11716
URL: https://issues.jenkins-ci.org/browse/JENKINS-11716
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Reporter: Steve Roth
We have a Jenkins instance (1.438) using the 'Build Record Root Directory'
feature, so we can specify an alternate directory for storing build artifacts
outside of the JENKINS HOME directory.
The 'Build Record Root Directory' (set in configure system, then click
Advanced... button at the top), is set to
/scratch/jbuildroot/${ITEM_FULLNAME}/builds. The Workspace Root dir is set
to ${ITEM_ROOTDIR}/workspace.
This generally works fine. However, I noticed that when I rename a job, I
lose the previous build records.
I see a new build record directory is created, beneath the specified 'Build
Record Root Directory'. However, the old build directory also exists,
containing the previous records. They are not moved over to the new
directory.
In other words, when the 'Build Record Root Directory' feature is enabled,
renaming a project causes the project's build records to be lost.
Current workaround is to move the build record files over and use sed to
replace the project name in them, then restart Jenkins.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11716) When 'Build Record Root Directory' is enabled, renaming a job does not create a new BRRD dir for the renamed job, and does not rename/copy artifacts from the original BRRD
[
https://issues.jenkins-ci.org/browse/JENKINS-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158929#comment-158929
]
Steve Roth edited comment on JENKINS-11716 at 4/21/12 9:21 PM:
---
One shell script workaround for renaming the fileystem parts of job (presumes a
path like ${ITEM_FULLNAME}/builds is listed below. Save as 'renamejob.sh'.
First, backup your original job name directory, just in case.
Next, rename the job in the Jenkins UI.
Then run this script
Last, restart Jenkins (required).
Usage: renameJob.sh pathToBuildArtifactDir oldJobName newJobName
{code}
#!/bin/sh -eu
JOBROOT=$1
OLDJOB=$2
NEWJOB=$3
if [ ! -d $JOBROOT ]; then
echo ERROR: directory at JOBROOT=$JOBROOT does not exist
exit 1
fi
if [ ! -d $JOBROOT/$NEWJOB ]; then
mkdir -p $JOBROOT/$NEWJOB
#echo ERROR: newjob directory at $JOBROOT/$NEWJOB does not exist
#exit 1
fi
if [ ! -d $JOBROOT/$OLDJOB ]; then
echo ERROR: oldjob directory at $JOBROOT/$OLDJOB does not exist
exit 1
fi
echo RENAMING JOB from $OLDJOB == $NEWJOB
set +e
rm -rf $JOBROOT/$NEWJOB/builds/*
mv $JOBROOT/$OLDJOB/* $JOBROOT/$NEWJOB
set -e
echo RENAMING OLD JOB TO END IN .old
set +e
mv $JOBROOT/$OLDJOB $JOBROOT/${OLDJOB}.old
set -e
echo UPDATING RUNS...
for RUNDIR in `ls -d $JOBROOT/$NEWJOB/builds/2012*`; do
echo ... UPDATING RUN AT $RUNDIR
if [ -f $JOBROOT/$RUNDIR/junitResult.xml ]; then
sed -i s/$OLDJOB/$NEWJOB/g $JOBROOT/$RUNDIR/junitResult.xml
fi
if [ -f $JOBROOT/$RUNDIR/build.xml ]; then
sed -i s/$OLDJOB/$NEWJOB/g $JOBROOT/$RUNDIR/build.xml
fi
done
echo REMOVING .old JOB (this may fail if more work is needed)
rmdir $JOBROOT/${OLDJOB}.old
{code}
was (Author: sroth):
One shell script workaround for renaming the fileystem parts of job
(presumes a path like ${ITEM_FULLNAME}/builds is listed below. Save as
'renamejob.sh'.
First, backup your original job name directory, just in case.
Next, rename the job in the Jenkins UI.
Then run this script
Last, restart Jenkins (required).
Usage: renameJob.sh oldJobName newJobName pathToBuildArtifactDir
#!/bin/sh -eu
OLDJOB=$1
NEWJOB=$2
JOBROOT=$3
if [ ! -d $JOBROOT ]; then
echo ERROR: directory at JOBROOT=$JOBROOT does not exist
exit 1
fi
if [ ! -d $JOBROOT/$NEWJOB ]; then
echo ERROR: newjob directory at $JOBROOT/$NEWJOB does not exist
exit 1
fi
if [ ! -d $JOBROOT/$OLDJOB ]; then
echo ERROR: oldjob directory at $JOBROOT/$OLDJOB does not exist
exit 1
fi
echo RENAMING JOB from $OLDJOB == $NEWJOB
set +e
rm -f $JOBROOT/last*
rm -rf $JOBROOT/$NEWJOB/builds/*
mv $JOBROOT/$OLDJOB/* $JOBROOT/$NEWJOB
set -e
echo UPDATING RUNS...
for RUNDIR in `ls -d $JOBROOT/$NEWJOB/builds/*-*-*`; do
echo ... UPDATING RUN AT $RUNDIR
if [ -f $JOBROOT/$RUNDIR/junitResult.xml ]; then
sed -i s/$OLDJOB/$NEWJOB/g $JOBROOT/$RUNDIR/junitResult.xml
fi
if [ -f $JOBROOT/$RUNDIR/build.xml ]; then
sed -i s/$OLDJOB/$NEWJOB/g $JOBROOT/$RUNDIR/build.xml
fi
done
When 'Build Record Root Directory' is enabled, renaming a job does not create
a new BRRD dir for the renamed job, and does not rename/copy artifacts from
the original BRRD
---
Key: JENKINS-11716
URL: https://issues.jenkins-ci.org/browse/JENKINS-11716
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Reporter: Steve Roth
We have a Jenkins instance (1.438) using the 'Build Record Root Directory'
feature, so we can specify an alternate directory for storing build artifacts
outside of the JENKINS HOME directory.
The 'Build Record Root Directory' (set in configure system, then click
Advanced... button at the top), is set to
/scratch/jbuildroot/${ITEM_FULLNAME}/builds. The Workspace Root dir is set
to ${ITEM_ROOTDIR}/workspace.
This generally works fine. However, I noticed that when I rename a job, I
lose the previous build records.
I see a new build record directory is created, beneath the specified 'Build
Record Root Directory'. However, the old build directory also exists,
containing the previous records. They are not moved over to the new
directory.
In other words, when the 'Build Record Root Directory' feature is enabled,
renaming a project causes the project's build records to be lost.
Current workaround is to move the build record files over and use sed to
replace the project name in them, then restart Jenkins.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13517) CopyProjectLink plugin: does not work with jobs using 'display name' feature
Steve Roth created JENKINS-13517: Summary: CopyProjectLink plugin: does not work with jobs using 'display name' feature Key: JENKINS-13517 URL: https://issues.jenkins-ci.org/browse/JENKINS-13517 Project: Jenkins Issue Type: Bug Components: copy-project-link Affects Versions: current Reporter: Steve Roth Priority: Minor In Jenkins 1.454, the copy project link plugin does not work when copying a job which is using the new 'display name' feature. You can repro with these steps: - create job A and go to the configure page. - click the Advanced... button next in the 'Advanced Project Options section. - set the Display Name to something like 'My job' - save the config page - on the main job page, click the 'Copy project' link to copy it - note the URL has the (internal) job name -- 'A' (good) - enter a new job name, and click OK. At this point, you get an error message of the form: Error No such job: My job A workaround is to use the normal 'new job' approach for copying a job. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
[
https://issues.jenkins-ci.org/browse/JENKINS-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161102#comment-161102
]
Steve Roth commented on JENKINS-13114:
--
I've ruled out 1.454, so it's very likely this issue first appeared in v1.455.
dropdown views taskbar: error when saving jenkins config page
-
Key: JENKINS-13114
URL: https://issues.jenkins-ci.org/browse/JENKINS-13114
Project: Jenkins
Issue Type: Bug
Components: dropdown-viewstabbar
Affects Versions: current
Reporter: Steve Roth
Assignee: jieryn
I have the dropdown views tabbar enabled, and am usign Jenkins 1.455 When I
go to save the main Jenkins config page, I see this CNF exception in the
browser:
exception
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to
instantiate class hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:605)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
org.kohsuke.stapler.Stapler.service(Stapler.java:159)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
oracle.boulderlabs.jenkins.validatorkiller.ValidatorKiller.doFilter(ValidatorKiller.java:63)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
root cause
java.lang.IllegalArgumentException: Failed to instantiate class
hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
[
https://issues.jenkins-ci.org/browse/JENKINS-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160795#comment-160795
]
Steve Roth commented on JENKINS-13114:
--
This issue does not occur in Jenkins ver. 1.453 so it seems to be related to a
newer Jenkins version. (1.454 or 1.455)
dropdown views taskbar: error when saving jenkins config page
-
Key: JENKINS-13114
URL: https://issues.jenkins-ci.org/browse/JENKINS-13114
Project: Jenkins
Issue Type: Bug
Components: dropdown-viewstabbar
Affects Versions: current
Reporter: Steve Roth
Assignee: jieryn
I have the dropdown views tabbar enabled, and am usign Jenkins 1.455 When I
go to save the main Jenkins config page, I see this CNF exception in the
browser:
exception
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to
instantiate class hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:605)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
org.kohsuke.stapler.Stapler.service(Stapler.java:159)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
oracle.boulderlabs.jenkins.validatorkiller.ValidatorKiller.doFilter(ValidatorKiller.java:63)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
root cause
java.lang.IllegalArgumentException: Failed to instantiate class
hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)
[JIRA] (JENKINS-13035) Duplicate Views Tab Bar option
[ https://issues.jenkins-ci.org/browse/JENKINS-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160335#comment-160335 ] Steve Roth commented on JENKINS-13035: -- me too Duplicate Views Tab Bar option -- Key: JENKINS-13035 URL: https://issues.jenkins-ci.org/browse/JENKINS-13035 Project: Jenkins Issue Type: Bug Components: core Environment: Jenkins 1.454 Reporter: mdp Priority: Minor On the Configure System screen there are two identically named (Views Tab Bar) options. The first one has help and lets me choose between CountJobs Views TabBar (an installed plugin) and Default Views TabBar. The second one does not have help and its dropbox is empty. In config.xml there are two settings present: viewsTabBar class=ws.albors.CountJobsViewsTabBar/ myViewsTabBar class=hudson.views.DefaultMyViewsTabBar/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page
[
https://issues.jenkins-ci.org/browse/JENKINS-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160348#comment-160348
]
Steve Roth commented on JENKINS-13114:
--
With DD views taskbar installed (but not selected), I am able to save the
system config page.
With other navigation views selected, I am able to save the system config page.
Once I select the DD views taskbar and save the config page, any further
attempts to save the config page fail with an error like the above.
The main symptom is a ClassNotFoundException listing a set of classes such as
java.lang.ClassNotFoundException:
[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]
dropdown views taskbar: error when saving jenkins config page
-
Key: JENKINS-13114
URL: https://issues.jenkins-ci.org/browse/JENKINS-13114
Project: Jenkins
Issue Type: Bug
Components: dropdown-viewstabbar
Affects Versions: current
Reporter: Steve Roth
Assignee: jieryn
I have the dropdown views tabbar enabled, and am usign Jenkins 1.455 When I
go to save the main Jenkins config page, I see this CNF exception in the
browser:
exception
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to
instantiate class hudson.views.ViewsTabBar from
{showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:605)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
org.kohsuke.stapler.Stapler.service(Stapler.java:159)
javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
oracle.boulderlabs.jenkins.validatorkiller.ValidatorKiller.doFilter(ValidatorKiller.java:63)
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
root cause
java.lang.IllegalArgumentException: Failed to instantiate
[JIRA] (JENKINS-11716) Renaming a job does not rename the build record root dir, for a Jenkins instance configured with this feature
[ https://issues.jenkins-ci.org/browse/JENKINS-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158847#comment-158847 ] Steve Roth commented on JENKINS-11716: -- This is still an issue in Jenkins 1.450 Renaming a job does not rename the build record root dir, for a Jenkins instance configured with this feature - Key: JENKINS-11716 URL: https://issues.jenkins-ci.org/browse/JENKINS-11716 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: Steve Roth We have a Jenkins instance (1.438) using the 'Build Record Root Directory' feature, so we can specify an alternate directory for storing build artifacts outside of the JENKINS HOME directory. This generally works fine. However, I noticed that when I rename a job, I lose the previous build records. I see a new build record directory is created, beneath the specified 'Build Record Root Directory'. However, the old build directory also exists, containing the previous records. They are not moved over to the new directory. In other words, when the 'Build Record Root Directory' feature is enabled, renaming a project causes the project's build records to be lost. Current workaround is to move the build record files over and use sed to replace the project name in them, then restart Jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
