[JIRA] (JENKINS-15354) Add option to fail the build if specified "Files to deploy" do not exist
Brent Duffy commented on JENKINS-15354 Add option to fail the build if specified "Files to deploy" do not exist Hi Gregory, I'm thinking if the 'Files to deploy' _expression_ does not match any files relative to the $WORKSPACE, the option, if selected, should trigger a build failure. For example, the following _expression_ could trigger a build failure if no .jar files were present under the 'output' directory: output/*.jar This new option, 'Fail build if there are no files to deploy' could be added within the 'Advanced...' button options for the 'Files to deploy' field. The problem we're having is that if there are zero files to deploy, the ArtifactDeployer plugin currently indicates that zero artifacts being deployed is a success condition. I'd be useful to have an option to say that, if no artifacts were found to deploy, some error prevented the artifacts from being available for deployment when they were expected per the build configuration. Thanks for your quick response! 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-12972) Add option to run 'git bisect' to find which commit added new bugs
Dan F commented on JENKINS-12972 Add option to run 'git bisect' to find which commit added new bugs Hi everyone. I need this bug/feature so much that I'm willing to pay for it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/33/add-option-to-run-git-bisect-to-find-which-commit-added-new-bugs). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors! I will try to get my employers to kick in more money. 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-12972) Add option to run 'git bisect' to find which commit added new bugs
Dan F commented on JENKINS-12972 Add option to run 'git bisect' to find which commit added new bugs Anyone thought about working on this? Right now, our Jenkins emails out all sorts of emails about things breaking or being fixed, but doesn't pin-point the person who should fix breakages. Finding the responsible party seems more important than the "minor" on this 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
[JIRA] (JENKINS-13126) Create empty directories on remote server
SCM/JIRA link daemon resolved JENKINS-13126 as Fixed Create empty directories on remote server Change By: SCM/JIRA link daemon (28/Sep/12 11:26 PM) Status: Open Resolved Resolution: Fixed 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-13831) Need a way to copy empty directories with Publish Over SSH Plugin
SCM/JIRA link daemon resolved JENKINS-13831 as Fixed Need a way to copy empty directories with Publish Over SSH Plugin Change By: SCM/JIRA link daemon (28/Sep/12 11:26 PM) Status: Open Resolved Resolution: Fixed 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-13831) Need a way to copy empty directories with Publish Over SSH Plugin
SCM/JIRA link daemon commented on JENKINS-13831 Need a way to copy empty directories with Publish Over SSH Plugin Code changed in jenkins User: bap2000 Path: src/main/java/jenkins/plugins/publish_over_ssh/BapSshTransfer.java src/main/java/jenkins/plugins/publish_over_ssh/descriptor/BapSshTransferDescriptor.java src/main/java/jenkins/plugins/publish_over_ssh/options/SshOverrideTransferDefaults.java src/main/resources/jenkins/plugins/publish_over_ssh/BapSshTransfer/config.jelly src/main/resources/jenkins/plugins/publish_over_ssh/BapSshTransfer/help-makeEmptyDirs.html src/main/resources/jenkins/plugins/publish_over_ssh/options/SshOverrideTransferDefaults/config.jelly src/test/java/jenkins/plugins/publish_over_ssh/BapSshClientTest.java src/test/java/jenkins/plugins/publish_over_ssh/BapSshHostConfigurationTest.java src/test/java/jenkins/plugins/publish_over_ssh/jenkins/IntegrationTest.java src/test/java/jenkins/plugins/publish_over_ssh/jenkins/LegacyConfigurationTest.java http://jenkins-ci.org/commit/publish-over-ssh-plugin/02b6aa8c02abf62072f3ecdde9020932bd0f3a55 Log: [FIXED JENKINS-13831] Option to create empty directories 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-13126) Create empty directories on remote server
SCM/JIRA link daemon commented on JENKINS-13126 Create empty directories on remote server Code changed in jenkins User: bap2000 Path: src/main/java/jenkins/plugins/publish_over_ftp/BapFtpTransfer.java src/main/java/jenkins/plugins/publish_over_ftp/descriptor/BapFtpTransferDescriptor.java src/main/java/jenkins/plugins/publish_over_ftp/options/FtpOverrideTransferDefaults.java src/main/resources/jenkins/plugins/publish_over_ftp/BapFtpTransfer/config.jelly src/main/resources/jenkins/plugins/publish_over_ftp/BapFtpTransfer/help-makeEmptyDirs.html src/main/resources/jenkins/plugins/publish_over_ftp/options/FtpOverrideTransferDefaults/config.jelly src/test/java/jenkins/plugins/publish_over_ftp/jenkins/CurrentConfigurationTest.java src/test/java/jenkins/plugins/publish_over_ftp/jenkins/IntegrationTest.java src/test/java/jenkins/plugins/publish_over_ftp/jenkins/LegacyConfigurationTest.java http://jenkins-ci.org/commit/publish-over-ftp-plugin/42df64142b9c97c32f5f99352782549bed5c69cf Log: [FIXED JENKINS-13126] Option to create empty directories 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-13831) Need a way to copy empty directories with Publish Over SSH Plugin
SCM/JIRA link daemon commented on JENKINS-13831 Need a way to copy empty directories with Publish Over SSH Plugin Code changed in jenkins User: bap2000 Path: src/main/java/jenkins/plugins/publish_over/BPBuildInfo.java src/main/java/jenkins/plugins/publish_over/BPTransfer.java src/main/java/jenkins/plugins/publish_over/FileFinder.java src/main/java/jenkins/plugins/publish_over/FileFinderResult.java src/main/java/jenkins/plugins/publish_over/options/GlobalDefaults.java src/main/java/jenkins/plugins/publish_over/options/TransferOptions.java src/main/resources/jenkins/plugins/publish_over/view_defaults/BPTransfer/Messages.properties src/main/resources/jenkins/plugins/publish_over/view_defaults/BPTransfer/Messages_no_BV.properties src/test/java/jenkins/plugins/publish_over/BPBuildInfoTest.java src/test/java/jenkins/plugins/publish_over/BPTransferTest.java src/test/java/jenkins/plugins/publish_over/BapPublisherTest.java src/test/java/jenkins/plugins/publish_over/FileFinderTest.java http://jenkins-ci.org/commit/publish-over-plugin/d2b08c13cec1e6bb02d1df89344adfeaeb921500 Log: [FIXED JENKINS-13126] [FIXED JENKINS-13831] Option to create empty directories 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-13126) Create empty directories on remote server
SCM/JIRA link daemon commented on JENKINS-13126 Create empty directories on remote server Code changed in jenkins User: bap2000 Path: src/main/java/jenkins/plugins/publish_over/BPBuildInfo.java src/main/java/jenkins/plugins/publish_over/BPTransfer.java src/main/java/jenkins/plugins/publish_over/FileFinder.java src/main/java/jenkins/plugins/publish_over/FileFinderResult.java src/main/java/jenkins/plugins/publish_over/options/GlobalDefaults.java src/main/java/jenkins/plugins/publish_over/options/TransferOptions.java src/main/resources/jenkins/plugins/publish_over/view_defaults/BPTransfer/Messages.properties src/main/resources/jenkins/plugins/publish_over/view_defaults/BPTransfer/Messages_no_BV.properties src/test/java/jenkins/plugins/publish_over/BPBuildInfoTest.java src/test/java/jenkins/plugins/publish_over/BPTransferTest.java src/test/java/jenkins/plugins/publish_over/BapPublisherTest.java src/test/java/jenkins/plugins/publish_over/FileFinderTest.java http://jenkins-ci.org/commit/publish-over-plugin/d2b08c13cec1e6bb02d1df89344adfeaeb921500 Log: [FIXED JENKINS-13126] [FIXED JENKINS-13831] Option to create empty directories 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-14951) In a Matrix job, Environment Script variables are not expanded in a Parameterized Build Trigger
Don Lindsay commented on JENKINS-14951 In a Matrix job, Environment Script variables are not expanded in a Parameterized Build Trigger This may be a duplicate of JENKINS-15117. I note that in the example given, the variable wasn't "export"ed. However, fixing that doesn't seem to fix the issue. Seen with jenkins 1.482, Parameterized Trigger Plugin 2.15 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-15354) Add option to fail the build if specified "Files to deploy" do not exist
Gregory Boissinot commented on JENKINS-15354 Add option to fail the build if specified "Files to deploy" do not exist Like ArtifactDeployer enables you to specify several sections of 'Files to deploy', do you want an option for each section or a global option? In first use-case, build fails only if there are no maching files and the option (checkbox) is selected. In the second use-case, the build fails only if the option is selected and there is at least one section that doesn't meet the conditions (no matching files). 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-15354) Add option to fail the build if specified "Files to deploy" do not exist
Gregory Boissinot started work on JENKINS-15354 Add option to fail the build if specified "Files to deploy" do not exist Change By: Gregory Boissinot (28/Sep/12 7:58 PM) Status: Open In Progress 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-15324) email-ext static-analysis template show empty data for Findbugs if job is a Maven project
hhuynh commented on JENKINS-15324 email-ext static-analysis template show empty data for Findbugs if job is a Maven project While waiting for this fix, is there a different way to expose new findbugs warning count via token? I see from the doc that this token $FINDBUGS_NEW is produced but I'm not sure how to make use of it in the email template (or is it even possible?) 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-12861) klocwork - update to recognize 9.5.x xml schema
Gregory Boissinot commented on JENKINS-12861 klocwork - update to recognize 9.5.x xml schema I'm afraid I don't understand your last question about logger. Do you ask me which kind of tool to use when you'll have new issues? 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
[JIRA] (JENKINS-12207) get warnings in log
lars Nordin commented on JENKINS-12207 get warnings in log on Jenkins ver. 1.466.2 The Warnings look like this: Sep 28, 2012 1:56:35 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.getNodeName(job). Reason: java.lang.RuntimeException: String has no matching NumeralEnum value java.lang.RuntimeException: String has no matching NumeralEnum value at hudson.plugins.nodenamecolumn.NodeNameColumn.getName(NodeNameColumn.java:75) at hudson.plugins.nodenamecolumn.NodeNameColumn.getNodeName(NodeNameColumn.java:53) at sun.reflect.GeneratedMethodAccessor100.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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) 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:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.CallTagLibScript.run(CallTagLibScript.java:119) at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:283) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at $Proxy28.projectView(Unknown Source) at lib.JenkinsTagLib$projectView.call(Unknown Source) at hudson.model.View.main.run(main.groovy:14) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:66) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:59) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91
[JIRA] (JENKINS-14152) Configuration Matrix combination filter ignored
Bruno P. Kinoshita closed JENKINS-14152 as Fixed Configuration Matrix combination filter ignored Closing as user confirmed that after upgrading from 1.475 to 1.481 the issue disappeared. Change By: Bruno P. Kinoshita (28/Sep/12 5:43 PM) Status: Open Closed Resolution: Fixed 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-14453) Generate empty cell for missing data
Ognjen Bubalo resolved JENKINS-14453 as Fixed Generate empty cell for missing data Can be reopened if the issue is still actual Change By: Ognjen Bubalo (28/Sep/12 3:52 PM) Status: Open Resolved Resolution: Fixed 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-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
Thomas Zlika updated JENKINS-15344 Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException Change By: Thomas Zlika (28/Sep/12 3:35 PM) Environment: The problem occurs at least on the following tested environments:- Jenkins 1.483 & 1.437 on both Windows and Linux- analysis-core plugin 1.47 and findbugs plugin 4.44- Multi-module Maven 3 project using Maven Findbugs plugin 2.5.2- JDK 1.7 or JRE1.6 - Jenkins launched in standalone mode (java -jar jenkins.war) or deployed in a Tomcat server- It is not a slave build 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-15292) RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml
Stefan Thurnherr commented on JENKINS-15292 RedeployPublisher no longer falls back to $M2_HOME/conf/settings.xml Same problem here after having upgraded from v1.479 to v1.483: ... [WARNINGS] Parsing warnings in console log with parser Java Compiler (javac) Maven RedeployPublisher use maven settings from : /pathto/tomcat/.m2/settings.xml ERROR: Publisher hudson.maven.RedeployPublisher aborted due to exception hudson.util.IOException2: Failed to copy /pathto/tomcat/.m2/settings.xml to /pathto/tomcat/temp/jenkins6746977447219049704temp-settings.xml at hudson.FilePath.copyTo(FilePath.java:1650) at hudson.maven.RedeployPublisher.createEmbedder(RedeployPublisher.java:287) at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:153) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:994) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.FileNotFoundException: /pathto/tomcat/.m2/settings.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:138) at hudson.FilePath$33.invoke(FilePath.java:1676) at hudson.FilePath$33.invoke(FilePath.java:1671) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.FilePath.copyTo(FilePath.java:1671) at hudson.FilePath.copyTo(FilePath.java:1645) ... 11 more Email was triggered for: Failure ... 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-15315) Slave polling hungup
Rob Petti commented on JENKINS-15315 Slave polling hungup It looks like your p4 client executable is hanging for some reason. Double check all your settings, and make sure you are using a client version that matches your server version. Also make sure that you aren't using any special characters in your workspace name. 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-15356) NPE caused executor thread death
Krzysztof Malinowski created JENKINS-15356 NPE caused executor thread death Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 28/Sep/12 2:52 PM Description: The following information was available on a "Thread has died" page: java.lang.NullPointerException at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:218) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:64) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1197) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:136) at hudson.model.Executor.run(Executor.java:211) Environment: Jenkins 1.480 on RHEL 5 x86_64 Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski 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-15348) Perforce plugin loses configuration for System Root
SCM/JIRA link daemon resolved JENKINS-15348 as Fixed Perforce plugin loses configuration for System Root Change By: SCM/JIRA link daemon (28/Sep/12 2:50 PM) Status: Open Resolved Resolution: Fixed 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-15348) Perforce plugin loses configuration for System Root
SCM/JIRA link daemon commented on JENKINS-15348 Perforce plugin loses configuration for System Root Code changed in jenkins User: Rob Petti Path: src/main/java/hudson/plugins/perforce/PerforceSCM.java src/test/java/hudson/plugins/perforce/PerforceSCMTest.java http://jenkins-ci.org/commit/perforce-plugin/a807f5ea3c7c3afa6b234c8c55a3513d35c82026 Log: [FIXED JENKINS-15348] applying patch provided in ticket 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-15239) Tags feature is broken
Francis Upton commented on JENKINS-15239 Tags feature is broken This might have been broken by my recent changes to support restarting of stopped nodes. 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-4995) Support windows AMI's in EC2 plugin
Francis Upton commented on JENKINS-4995 Support windows AMI's in EC2 plugin Hey Frank, have you made any progress on this one? 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-15355) AdjunctManager: exception upon startup
Krzysztof Malinowski created JENKINS-15355 AdjunctManager: exception upon startup Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 28/Sep/12 2:45 PM Description: Upon startup there are few instances of exception logged: Sep 28, 2012 4:41:33 PM org.kohsuke.stapler.jelly.AdjunctTag doTag WARNING: AdjunctManager is not installed for this application. Skipping tags java.lang.Exception at org.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:74) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.CallTagLibScript.run(CallTagLibScript.java:119) 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.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at hudson.util.HudsonIsLoading.doDynamic(HudsonIsLoading.java:45) 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.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:363) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEnco
[JIRA] (JENKINS-15354) Add option to fail the build if specified "Files to deploy" do not exist
Brent Duffy created JENKINS-15354 Add option to fail the build if specified "Files to deploy" do not exist Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: artifactdeployer Created: 28/Sep/12 2:43 PM Description: It'd be nice to have a checkbox option for the [ArtifactDeployer] plugin to cause the build to fail if the artifacts specified in the "Files to deploy" field do not exist. The current behavior of the plugin is to succeed even if there are zero artifacts matching the specified file/wildcard _expression_. Environment: Jenkins LTS 1.466.1 on RHEL 6.1 x86_64 java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.3) (rhel-1.48.1.11.3.el6_2-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Project: Jenkins Priority: Minor Reporter: Brent Duffy 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-15353) Missing descriptor exception in Jenkins log for Throttle Concurrent Builds plugin
Brent Duffy created JENKINS-15353 Missing descriptor exception in Jenkins log for Throttle Concurrent Builds plugin Issue Type: Bug Affects Versions: current Assignee: abayer Components: throttle-concurrents Created: 28/Sep/12 2:31 PM Description: Getting the following exception when browsing to Manage Jenkins -> Configure System. There's a link in the output that describes how to fix the exception: See https://wiki.jenkins-ci.org/display/JENKINS/My+class+is+missing+descriptor Sep 28, 2012 10:28:25 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor6302.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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:72) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) 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.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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:270) 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.CallTagLibScript.run(CallTagLibScript.java:119) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.CallTagLibScript.run(CallTagLibScript.java:119) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.defi
[JIRA] (JENKINS-15352) Unknown URL in Jenkins CLI help
Jim McCaskey created JENKINS-15352 Unknown URL in Jenkins CLI help Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cli Created: 28/Sep/12 2:27 PM Description: This was found on Jenkins 1.477. When you execute the jenkins-cli.jar with no options you get the below text. E:\test>java -jar jenkins-cli.jar Neither -s nor the JENKINS_URL env var is specified. Jenkins CLI Usage: java -jar jenkins-cli.jar [-s URL] command [opts...] args... Options: -s URL : the server URL (defaults to the JENKINS_URL env var) -i KEY : SSH private key file used for authentication -p HOST:PORT : HTTP proxy host and port for HTTPS proxy tunneling. See http://jenkins-ci.org/https-proxy-tunnel The available commands depend on the server. Run the help command to see the list. The URL referencing http://jenkins-ci.org/https-proxy-tunnel gives a page not found error message. Environment: Windows Project: Jenkins Priority: Trivial Reporter: Jim McCaskey 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-14339) Jenkins slave as windows service set as invalid password
Chris Romano closed JENKINS-14339 as Not A Defect Jenkins slave as windows service set as invalid password Change By: Chris Romano (28/Sep/12 2:18 PM) Status: Open Closed Resolution: Not A Defect 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-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
Thomas Zlika commented on JENKINS-15344 Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException Just made a test with JRE6 : same problem. 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-15351) Exception while processing cpd report.
Mat Lowery updated JENKINS-15351 Exception while processing cpd report. Change By: Mat Lowery (28/Sep/12 1:52 PM) Description: Jenkins version: 1.476 Plugin version: 2.30My Maven build creates a cpd.xml that looks like this:And I'm seeing the following exception in the Jenkins log when the DRY plugin is enabled:org.apache.commons.digester3.Digester errorSEVERE: Parse Error at line 2 column 10: Document root element "pmd-cpd", must match DOCTYPE root "null".org.xml.sax.SAXParseException: Document root element "pmd-cpd", must match DOCTYPE root "null".at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)at org.apache.xerces.impl.dtd.XMLDTDValidator.rootElementSpecified(Unknown Source)at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source)at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)at org.apache.commons.digester3.Digester.parse(Digester.java:1642)at org.apache.commons.digester3.Digester.parse(Digester.java:1701)at hudson.plugins.dry.parser.cpd.CpdParser.accepts(CpdParser.java:48)at hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:77)at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:261)at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:220)at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:169)at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31)at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2196)at hudson.remoting.UserRequest.perform(UserRequest.java:118)at hudson.remoting.UserRequest.perform(UserRequest.java:48)at hudson.remoting.Request$2.run(Request.java:326)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)at java.util.concurrent.FutureTask.run(FutureTask.java:138)at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)at java.lang.Thread.run(Thread.java:662)org.apache.commons.digester3.Digester errorSEVERE: Parse Error at line 2 column 10: Document is invalid: no grammar found.org.xml.sax.SAXParseException: Document is invalid: no grammar found.at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElemen
[JIRA] (JENKINS-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
Thomas Zlika commented on JENKINS-15344 Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException analysis-core : 1.47 findbugs : 4.44 Starting Jenkins in standalone mode (java -jar) or deployed in a Tomcat server leads to the same problem. I've not tried with a JDK6 yet. 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-15351) Exception while processing cpd report.
Dennis Lundberg commented on JENKINS-15351 Exception while processing cpd report. We're seing this as well using Jenkins 1.470 and DRY Plugin 2.28. The stack trace scared a colleague because he though that his release build had failed, when in fact it had succeeded. 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-15315) Slave polling hungup
Alexey Larsky commented on JENKINS-15315 Slave polling hungup Treaddump has attached. Perforce Polling Log Started on Sep 27, 2012 9:31:26 PM Looking for changes... Using node: Builder Using remote perforce client: Alexey.Larsky_NM_v01_builder ...nothing here... 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-15315) Slave polling hungup
Alexey Larsky edited a comment on JENKINS-15315 Slave polling hungup Treaddump is attached. Perforce Polling Log Started on Sep 27, 2012 9:31:26 PM Looking for changes... Using node: Builder Using remote perforce client: Alexey.Larsky_NM_v01_builder ...nothing here... 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-15315) Slave polling hungup
Alexey Larsky updated JENKINS-15315 Slave polling hungup Change By: Alexey Larsky (28/Sep/12 1:42 PM) Attachment: Thread dump [Jenkins] (2012-09-28 17-35-47).htm 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-15319) Failure starting slave nodes
Francis Upton commented on JENKINS-15319 Failure starting slave nodes Hi John, The project is active; if you look at the release history you can see many things have been fixed and functionality added in the last 6 months since I have started working as the main committer (both code I have done personally and many contributions from others). However there remains a lot of work to do. I'm a very part time (and busy) committer on this as a volunteer, so I cannot respond immediately to issues. I realize this is a very important issue and will try to get to it when I have time. The quickest way to get this fixed is to make and test a pull request that resolves the issue (bonus points if you can identify all of the JIRAs that your fix resolves). If you can do this, I can have a look and commit it pretty quickly. Others have had success also offering to pay for my time to resolve problems, that's another option and you can contact me at fran...@oaklandsoftware.com. Kind regards, Francis 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-15351) Exception while processing cpd report.
Mat Lowery created JENKINS-15351 Exception while processing cpd report. Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: dry Created: 28/Sep/12 1:26 PM Description: Plugin version: 2.30 My Maven build creates a cpd.xml that looks like this: And I'm seeing the following exception in the Jenkins log when the DRY plugin is enabled: org.apache.commons.digester3.Digester error SEVERE: Parse Error at line 2 column 10: Document root element "pmd-cpd", must match DOCTYPE root "null". org.xml.sax.SAXParseException: Document root element "pmd-cpd", must match DOCTYPE root "null". at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.rootElementSpecified(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester3.Digester.parse(Digester.java:1642) at org.apache.commons.digester3.Digester.parse(Digester.java:1701) at hudson.plugins.dry.parser.cpd.CpdParser.accepts(CpdParser.java:48) at hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:77) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:261) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:220) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:169) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2196) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) org.apache.commons.digester3.Digester error SEVERE: Parse Error at line 2 column 10: Document is invalid: no grammar found. org.xml.sax.SAXParseException: Document is invalid: no grammar found. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.ap
[JIRA] (JENKINS-15169) Warning Plugin - Graph Configuration Error
Chris Engler commented on JENKINS-15169 Warning Plugin - Graph Configuration Error Interesting, I was setting up the server to get you to look at the URL. Local host now keeps the pictures, the save button launches to the named Jenkins URL and not in local host. Using LDAP, I'm still logged into Jenkins. Outside of the login, the graphs work, and the save button still lauches to the named Jenkins URL. 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-14590) Redeploy Artifacts button no longer appears on main build page of multi-module builds, requiring individual reployment of modules
Jeff Maxwell updated JENKINS-14590 Redeploy Artifacts button no longer appears on main build page of multi-module builds, requiring individual reployment of modules Change By: Jeff Maxwell (28/Sep/12 1:21 PM) Summary: Redeploy Artifacts needs to executed for each button no longer appears on main build page of multi- module when it used redeploy all builds, requiring individual reployment of modules 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-15350) Wall display: Gravatar plugin causes instability
Gavin Davies created JENKINS-15350 Wall display: Gravatar plugin causes instability Issue Type: Bug Affects Versions: current Assignee: Christian Pelster Components: walldisplay Created: 28/Sep/12 1:12 PM Description: I recently merged from upstream and my build wall became unstable - I get a lot of timeouts. I've raised this with Aurelien (we both work at Box UK) and for now I've updated my fork: https://github.com/boxuk/walldisplay-plugin/ I isolated the problem and it is definitely the gravatar integration causing it Environment: Linux Project: Jenkins Priority: Major Reporter: Gavin Davies 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-15319) Failure starting slave nodes
John Dyer commented on JENKINS-15319 Failure starting slave nodes Is this project still active ? I ask because i have seen many tickets posted without any update -John 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-15016) Unable to see console logs from remote jobs ran on jcloud slaves
John Dyer resolved JENKINS-15016 as Not A Defect Unable to see console logs from remote jobs ran on jcloud slaves Figured this out, user error Change By: John Dyer (28/Sep/12 1:06 PM) Status: Open Resolved Resolution: Not A Defect 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-15349) missing maven 2/3 job type from the list of available type for a new job
Natalia Britvikhina created JENKINS-15349 missing maven 2/3 job type from the list of available type for a new job Issue Type: Bug Assignee: Unassigned Components: maven Created: 28/Sep/12 1:07 PM Description: When clicking New Job in Jenkins we don't get a "maven 2/3 project" job type on the list. Based on what it says here https://wiki.jenkins-ci.org/display/JENKINS/Building+a+maven2+project it sounds like it should be available. Environment: Ubuntu 10.04.3 Project: Jenkins Priority: Major Reporter: Natalia Britvikhina 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-15016) Unable to see console logs from remote jobs ran on jcloud slaves
John Dyer closed JENKINS-15016 as Not A Defect Unable to see console logs from remote jobs ran on jcloud slaves Change By: John Dyer (28/Sep/12 1:07 PM) Status: Resolved Closed 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
iPhone App To Help You Regain 20/20 Vision Naturally
http://goo.gl/fHiCv - "20/20 Vision" is an iPhone app that will help you regain 20/20 vision naturally, by looking at images that relaxes your eyes and performing eye exercises that strengthen your eyes, anywhere within your busy life (i.e. office cubicle, crowded subway, waiting at the hair salon, etc.), thanks.
[JIRA] (JENKINS-15348) Perforce plugin loses configuration for System Root
Simon Howkins updated JENKINS-15348 Perforce plugin loses configuration for System Root Change By: Simon Howkins (28/Sep/12 11:58 AM) Assignee: Rob Petti 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-15348) Perforce plugin loses configuration for System Root
Simon Howkins updated JENKINS-15348 Perforce plugin loses configuration for System Root Change By: Simon Howkins (28/Sep/12 11:58 AM) Attachment: JENKINS-15348.patch 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-15348) Perforce plugin loses configuration for System Root
Simon Howkins updated JENKINS-15348 Perforce plugin loses configuration for System Root Change By: Simon Howkins (28/Sep/12 11:52 AM) Description: # Create a test job.# Set it up with Perforce for the SCM.# In the Advanced section, set the Windows System Drive and System Root to empty strings.# Save the config.# Re-open the configuration window.# _*Note that the empty strings have been replaced with C: and C:\Windows*_# Set the Windows System Root and System Drive to strings of a single space.# Save the config.# Re-open the configuration window.# Note that the single space strings have been replaced with empty strings# Save the congig config again, and it's back to the C: based defaults :-(According to JENKINS-4908, empty strings should mean that the perforce plugin should just get the data from the environment.As we have some slaves where the system drive is C: and some where it's D: (don't ask...) we need to rely on the empty string configuration. Unfortunately, anyone who changes the job configuration needs to also change these fields to single spaces so they will be saved correctly (as empty strings). Otherwise, there will be arbitrary failures when a D: based slave is next chosen for a build.I've patched the source to make it behave as I would expect and tested locally - will attach... 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-15348) Perforce plugin loses configuration for System Root
Simon Howkins created JENKINS-15348 Perforce plugin loses configuration for System Root Issue Type: Bug Assignee: Unassigned Components: perforce Created: 28/Sep/12 11:51 AM Description: Create a test job. Set it up with Perforce for the SCM. In the Advanced section, set the Windows System Drive and System Root to empty strings. Save the config. Re-open the configuration window. Note that the empty strings have been replaced with C: and C:\Windows Set the Windows System Root and System Drive to strings of a single space. Save the config. Re-open the configuration window. Note that the single space strings have been replaced with empty strings Save the congig again, and it's back to the C: based defaults According to JENKINS-4908, empty strings should mean that the perforce plugin should just get the data from the environment. As we have some slaves where the system drive is C: and some where it's D: (don't ask...) we need to rely on the empty string configuration. Unfortunately, anyone who changes the job configuration needs to also change these fields to single spaces so they will be saved correctly (as empty strings). Otherwise, there will be arbitrary failures when a D: based slave is next chosen for a build. I've patched the source to make it behave as I would expect and tested locally - will attach... Environment: Windows master and slaves, with perforce SCM Project: Jenkins Priority: Major Reporter: Simon Howkins 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-3034) Pegging the externals when tagging.
Gabriele Giuseppini commented on JENKINS-3034 Pegging the externals when tagging. +1 Also in my opinion. This is the only thing that is making Jenkins not fully suitable to our processes - we promote builds and release and tag and all, but we can't freeze externals. 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-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
Ulli Hafner commented on JENKINS-15344 Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException Please add the plug-in versions of findbugs and analysis-core. And how do you start Jenkins? java -jar or Tomcat? Note: does this error occur when Jenkins runs using a JDK 6? 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-15347) Improper parsing of KW 9.2 results file
Mirek Gwiżdż created JENKINS-15347 Improper parsing of KW 9.2 results file Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: klocwork Created: 28/Sep/12 11:38 AM Description: After update to 1.12 Klocwork plugin is no longer able to properly parse report from Klocwork 9.2. The same issue exists in 1.13 version of the plugin. I have Klocwork 9.2 installed and the plugin improperly detects KW 9.6 I get following error from Jenkins log: Starting the klocwork analysis. Version 9.6 or later of Klocwork detected. Only Klocwork review is available. Parse_errors.log and build.log can be accessed on the review ERROR: Publisher com.thalesgroup.hudson.plugins.klocwork.KloPublisher aborted due to exception java.lang.NullPointerException at com.thalesgroup.hudson.plugins.klocwork.KloPublisher.perform(KloPublisher.java:141) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Project: Jenkins Priority: Major Reporter: Mirek Gwiżdż 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-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
Thomas Zlika commented on JENKINS-15344 Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException I've updated the environment section of the issue. Tell me if you need other details. 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-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
Thomas Zlika updated JENKINS-15344 Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException Change By: Thomas Zlika (28/Sep/12 11:32 AM) Environment: The problem occurs at least on the following tested environments:- Jenkins 1.483 & 1.437 on both Windows and Linux- Multi-module Maven 3 project using Maven Findbugs plugin 2.5.2- JDK 1.7- It is not a slave build 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-15330) Test Connection error
Ross Rowe resolved JENKINS-15330 as Fixed Test Connection error This issue has been fixed in version 1.23 Change By: Ross Rowe (28/Sep/12 11:08 AM) Status: In Progress Resolved Resolution: Fixed 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-15326) Error running ant with matrix build
Ross Rowe resolved JENKINS-15326 as Fixed Error running ant with matrix build I've included your patch in version 1.23, please let me know if there are any further issues. Change By: Ross Rowe (28/Sep/12 11:06 AM) Status: In Progress Resolved Resolution: Fixed 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-15261) Mobile browsers not selectable
Ross Rowe resolved JENKINS-15261 as Fixed Mobile browsers not selectable I've updated the plugin to present a list of the supported browsers for Selenium RC and WebDriver. This change has been included in version 1.23, please let me know if you have any further issues. Change By: Ross Rowe (28/Sep/12 11:07 AM) Status: In Progress Resolved Resolution: Fixed 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-15346) svn PROPFIND NPE on svn checkout
Kanstantsin Shautsou created JENKINS-15346 svn PROPFIND NPE on svn checkout Issue Type: Bug Assignee: Unassigned Components: subversion Created: 28/Sep/12 10:46 AM Description: imho NPE should be handled. Started by an SCM change Building in workspace /opt/jenkins/workspace/aa Cleaning local Directory aa Checking out https://SERVER/PROJECT/trunk/aa ERROR: Failed to check out https://SERVER/PROJECT/trunk/aa org.tmatesoft.svn.core.SVNException: svn: PROPFIND /PROJECT/trunk/aa failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:136) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineProperties(DAVUtil.java:226) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineInfo(DAVUtil.java:184) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:184) at org.tmatesoft.svn.core.wc.SVNBasicClient.getRevisionNumber(SVNBasicClient.java:482) at org.tmatesoft.svn.core.wc.SVNBasicClient.getLocations(SVNBasicClient.java:876) at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:534) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:901) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:84) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:788) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:769) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1502) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: PROPFIND /PROJECT/trunk/aa failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:146) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:89) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doPropfind(DAVConnection.java:126) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getProperties(DAVUtil.java:73) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getResourceProperties(DAVUtil.java:79) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getStartingProperties(DAVUtil.java:103) at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:125) ... 24 more Caused by: org.tmatesoft.svn.core.SVNException: svn: PROPFIND request failed on '/PROJECT/trunk/aa' svn: timed out waiting for server at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:662) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:292) ... 31 more Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: PROPFI
[JIRA] (JENKINS-15345) Wrong help for dynamic trigger configuration
rin_ne created JENKINS-15345 Wrong help for dynamic trigger configuration Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 28/Sep/12 10:42 AM Description: In help-DynamicTriggerConfiguration.html, "the URL to an xml file containing the Gerrit trigger configuration." But In wiki help, configuration text is not xml but DSL. I also think simple description for this format should be included in this help. Project: Jenkins Priority: Minor Reporter: rin_ne 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-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
Ulli Hafner commented on JENKINS-15344 Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException Can you please add some details about your environment? Is this a slave build? Which JDK, findbugs, Jenkins, etc. is installed? 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-15037) Option to consider only stable builds when calculating new warnings
SCM/JIRA link daemon commented on JENKINS-15037 Option to consider only stable builds when calculating new warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/checkstyle/CheckStyleMavenResultAction.java src/main/resources/hudson/plugins/checkstyle/CheckStylePublisher/config.jelly src/main/resources/hudson/plugins/checkstyle/CheckStyleReporter/config.jelly http://jenkins-ci.org/commit/checkstyle-plugin/d8c652dc9f5826e7ed72a255b3776b60bca4c0f2 Log: JENKINS-15037: Upgrade to new API in order to compute warnings only for stable builds (if option is checked). 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-15037) Option to consider only stable builds when calculating new warnings
SCM/JIRA link daemon commented on JENKINS-15037 Option to consider only stable builds when calculating new warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/WarningsAnnotationsAggregator.java src/main/java/hudson/plugins/warnings/WarningsBuildHistory.java src/main/java/hudson/plugins/warnings/WarningsProjectAction.java src/main/java/hudson/plugins/warnings/WarningsPublisher.java src/main/java/hudson/plugins/warnings/WarningsResult.java src/main/resources/hudson/plugins/warnings/WarningsPublisher/config.jelly src/test/java/hudson/plugins/warnings/WarningsPublisherTest.java http://jenkins-ci.org/commit/warnings-plugin/559c94f82212c265803bd14efa5fe5c3d00f172d Log: JENKINS-15037: Upgrade to new API in order to compute warnings only for stable builds (if option is checked). 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-15037) Option to consider only stable builds when calculating new warnings
SCM/JIRA link daemon commented on JENKINS-15037 Option to consider only stable builds when calculating new warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/tasks/MavenTasksResultAction.java src/main/java/hudson/plugins/tasks/TasksAnnotationsAggregator.java src/main/java/hudson/plugins/tasks/TasksMavenResult.java src/main/java/hudson/plugins/tasks/TasksMavenResultAction.java src/main/java/hudson/plugins/tasks/TasksPublisher.java src/main/java/hudson/plugins/tasks/TasksReporter.java src/main/java/hudson/plugins/tasks/TasksReporterResult.java src/main/java/hudson/plugins/tasks/TasksResult.java src/main/java/hudson/plugins/tasks/TasksResultAction.java src/main/resources/hudson/plugins/tasks/FixedTasksDetail/index.jelly http://jenkins-ci.org/commit/tasks-plugin/7fc0ef593e20049dd7f627834945f22ce8d5f6ff Log: JENKINS-15037: Upgrade to new API in order to compute warnings only for stable builds (if option is checked). 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-15037) Option to consider only stable builds when calculating new warnings
SCM/JIRA link daemon commented on JENKINS-15037 Option to consider only stable builds when calculating new warnings Code changed in jenkins User: Ulli Hafner Path: plugin/src/main/java/hudson/plugins/findbugs/FindBugsAnnotationsAggregator.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsMavenResult.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsMavenResultAction.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsPublisher.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporter.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporterResult.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsResult.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsResultAction.java plugin/src/main/java/hudson/plugins/findbugs/MavenFindBugsResultAction.java plugin/src/main/resources/hudson/plugins/findbugs/FindBugsPublisher/config.jelly plugin/src/main/resources/hudson/plugins/findbugs/FindBugsResult/index.jelly http://jenkins-ci.org/commit/findbugs-plugin/070456af4914838b5bb3dd16bd9f1aef242056a0 Log: JENKINS-15037: Upgrade to new API in order to compute warnings only for stable builds (if option is checked). 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-15037) Option to consider only stable builds when calculating new warnings
SCM/JIRA link daemon commented on JENKINS-15037 Option to consider only stable builds when calculating new warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/pmd/MavenPmdResultAction.java src/main/java/hudson/plugins/pmd/PmdAnnotationsAggregator.java src/main/java/hudson/plugins/pmd/PmdMavenResult.java src/main/java/hudson/plugins/pmd/PmdMavenResultAction.java src/main/java/hudson/plugins/pmd/PmdPublisher.java src/main/java/hudson/plugins/pmd/PmdReporter.java src/main/java/hudson/plugins/pmd/PmdReporterResult.java src/main/java/hudson/plugins/pmd/PmdResult.java src/main/java/hudson/plugins/pmd/PmdResultAction.java src/main/resources/hudson/plugins/pmd/PmdReporter/config.jelly http://jenkins-ci.org/commit/pmd-plugin/fba349e969bfdfaebfdfaa9785dd6b9d4841c88e Log: JENKINS-15037: Upgrade to new API in order to compute warnings only for stable builds (if option is checked). 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-15037) Option to consider only stable builds when calculating new warnings
SCM/JIRA link daemon commented on JENKINS-15037 Option to consider only stable builds when calculating new warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/dry/DryAnnotationsAggregator.java src/main/java/hudson/plugins/dry/DryMavenResult.java src/main/java/hudson/plugins/dry/DryMavenResultAction.java src/main/java/hudson/plugins/dry/DryPublisher.java src/main/java/hudson/plugins/dry/DryReporter.java src/main/java/hudson/plugins/dry/DryReporterResult.java src/main/java/hudson/plugins/dry/DryResult.java src/main/java/hudson/plugins/dry/DryResultAction.java src/main/java/hudson/plugins/dry/MavenDryResultAction.java src/main/resources/hudson/plugins/dry/DryPublisher/config.jelly src/main/resources/hudson/plugins/dry/DryReporter/config.jelly http://jenkins-ci.org/commit/dry-plugin/a715b62caf14f978da2e50dd89fc48beabe2356f Log: JENKINS-15037: Upgrade to new API in order to compute warnings only for stable builds (if option is checked). 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-15037) Option to consider only stable builds when calculating new warnings
SCM/JIRA link daemon commented on JENKINS-15037 Option to consider only stable builds when calculating new warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/collector/AnalysisAnnotationsAggregator.java src/main/java/hudson/plugins/analysis/collector/AnalysisPublisher.java src/main/java/hudson/plugins/analysis/collector/AnalysisResult.java src/main/java/hudson/plugins/analysis/collector/AnalysisResultAction.java src/main/resources/hudson/plugins/analysis/collector/AnalysisPublisher/config.jelly http://jenkins-ci.org/commit/analysis-collector-plugin/019fe5126b9ee42fff7ffeae9d322eec2582e17e Log: JENKINS-15037: Upgrade to new API in order to compute warnings only for stable builds (if option is checked). 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-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
Thomas Zlika created JENKINS-15344 Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Attachments: jenkins.txt Components: findbugs Created: 28/Sep/12 10:08 AM Description: When using the Jenkins Findbugs plugin on a multi-module Maven plugin, the build fails with the root cause exception: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory (cf. attachment for full stack-trace). Note: the Findbugs Maven plugin is not able to generate an aggregated report for multi-module Maven, so maybe this is the origin of the problem ? Project: Jenkins Priority: Major Reporter: Thomas Zlika 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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
Arvid Arntzen commented on JENKINS-15335 Jenkins briefly displays build queue and then it disappears until the page is reloaded We got this issue as well after updating to Jenkins 1.483. 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-7666) ClassCastException parsing JUnit result
Thomas Zlika commented on JENKINS-7666 ClassCastException parsing JUnit result Hi guys, I think I may have found a possible cause for the problem: it seems that the Jenkins Findbugs plugin does not manage correctly multi-module maven builds (maybe because the Maven Findbugs plugin is not able to produce an aggregated report for multi-module projets ?) Anyway, if I uncheck the checkbox "Publish Findbugs analysis results" in my project configuration, the problem disappears ! Regards, Thomas 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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
Krzysztof Malinowski commented on JENKINS-15335 Jenkins briefly displays build queue and then it disappears until the page is reloaded I am also affected by the issue. Voting for fix in the very near future. 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-15293) Can't configure Maven Installations on Jenkins ver. 1.483
Mirko Friedenhagen commented on JENKINS-15293 Can't configure Maven Installations on Jenkins ver. 1.483 Downgrading to 1.482 fixed this for me as well on Ubuntu 10.04 LTS. 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-15237) Dependent Maven Jobs ignore version-number
Marco Rothe updated JENKINS-15237 Dependent Maven Jobs ignore version-number Changed priority to major because this bug cause a heavy load to build infrastructure. Change By: Marco Rothe (28/Sep/12 9:40 AM) Priority: Minor Major 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-15237) Dependent Maven Jobs ignore version-number
Marco Rothe commented on JENKINS-15237 Dependent Maven Jobs ignore version-number I can confirm the problem too (jenkins 1.483) It seems that not only the SNAPSHOT version is ignored. I see a project (which depends on a release version dependency!) build triggert by a upstream build of the completely unrelated SNAPSHOT version of that dependency. Therefore our complete jenkins build server kept busy by building unrelated projects. Very annoying! 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-10635) java.io.IOException: Bad file descriptor storing Junit results
evernat resolved JENKINS-10635 as Incomplete java.io.IOException: Bad file descriptor storing Junit results No response from the reporter, so closing as incomplete. Change By: evernat (28/Sep/12 9:06 AM) Status: Open Resolved Resolution: Incomplete 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-12794) Occasional crash of plugin
Waldek M updated JENKINS-12794 Occasional crash of plugin Change By: Waldek M (28/Sep/12 8:55 AM) Environment: RHEL. Jenkins 1.451 and the latest versions of plugins - clearcase and cobertura Also present on latest 1.482 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-12794) Occasional crash of plugin
Waldek M commented on JENKINS-12794 Occasional crash of plugin Still failing, I'm afraid. Is there something I could do to have it fixed? ERROR: Publisher hudson.plugins.cobertura.CoberturaPublisher aborted due to exception java.lang.NullPointerException at hudson.FilePath.isAbsolute(FilePath.java:236) at hudson.FilePath.resolvePathIfRelative(FilePath.java:221) at hudson.FilePath.(FilePath.java:217) at hudson.FilePath.child(FilePath.java:1053) at hudson.plugins.clearcase.AbstractClearCaseScm.getModuleRoot(AbstractClearCaseScm.java:345) at hudson.scm.SCM.getModuleRoots(SCM.java:543) at hudson.model.AbstractBuild.getModuleRoots(AbstractBuild.java:290) at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:314) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) 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-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Shobha Dashottar commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel We have been facing this issue for some time. Yesterday, we upgraded to 1.466 and the issue persists. Jenkins master is running on Windows and the slaves are mainly Windows but a few are Linux. The issue randomly appears on any slave. Thanks Shobha script file c:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\hudson920936561807305456.bat hudson.util.IOException2: remote file operation failed: c:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\hudson920936561807305456.bat at hudson.remoting.Channel@5f1603a2: Slave123 at hudson.FilePath.act(FilePath.java:835) at hudson.FilePath.act(FilePath.java:821) at hudson.FilePath.delete(FilePath.java:1126) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480) at hudson.model.Run.run(Run.java:1438) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: hudson.remoting.ChannelClosedException: channel is already closed 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-15335) Jenkins briefly displays build queue and then it disappears until the page is reloaded
Dirk Kuypers commented on JENKINS-15335 Jenkins briefly displays build queue and then it disappears until the page is reloaded I downgraded to 1.482 which fixed the problem. So it must have been introduced with the changes from 1.483 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
