[JIRA] (JENKINS-17110) Hover-over Build Now broken for parameterized jobs: This page expects a form submission
mwebber commented on JENKINS-17110 Hover-over Build Now broken for parameterized jobs: This page expects a form submission I'm getting this too. 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 -- 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] (JENKINS-16287) Race condition in 'build' CLI command
Viktor Tarasov commented on JENKINS-16287 Race condition in build CLI command The same for me. jenkins-1.499, SLES-11-64 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] (JENKINS-17125) FingerprintAction Serializiation Bug
kutzi updated JENKINS-17125 FingerprintAction Serializiation Bug Not related to the fingerprint plugin but to core. Change By: kutzi (08/Mar/13 9:16 AM) Component/s: core Component/s: fingerprint 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] (JENKINS-5413) SCM polling getting hung
Linards L commented on JENKINS-5413 SCM polling getting hung Have not noticed that for long time now. But .. in the v1.48x version series I had similar problems, but the dissapeared. Remember we also did some scheduled rebooting temperings ... now using v1.494. 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] (JENKINS-17125) FingerprintAction Serializiation Bug
kutzi assigned JENKINS-17125 to Kohsuke Kawaguchi FingerprintAction Serializiation Bug Change By: kutzi (08/Mar/13 9:19 AM) Assignee: MarcSanfacon KohsukeKawaguchi 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] (JENKINS-5413) SCM polling getting hung
Linards L edited a comment on JENKINS-5413 SCM polling getting hung Have not noticed that for long time now. But .. in the v1.48x version series I had similar problems, but then they dissapeared. Remember we also did some scheduled rebooting temperings ... now using v1.494. 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] (JENKINS-17003) JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect
Linards L assigned JENKINS-17003 to Kohsuke Kawaguchi JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect Change By: Linards L (08/Mar/13 10:34 AM) Assignee: LinardsL KohsukeKawaguchi 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] (JENKINS-15931) Build is hanging on newly created EC2 slaves
Antti Rasinen commented on JENKINS-15931 Build is hanging on newly created EC2 slaves Further test cases have resolved that the limiting factor is, in fact, dependent on number of testcase files and the number of runs. The size of the files or the number of testcases within the files do not seem to matter. To be precise, when we have 0 or 1 file in the result set, the number of runs follows this equation: runs * (1.38 + number of files) = 338. When we have 2 or more files, the numbers are somewhat different: runs * (1.33 + number of files) = 790. 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] (JENKINS-16974) Build Now link on MultiJob page doesn't work
Philipp Mohrenweiser commented on JENKINS-16974 Build Now link on MultiJob page doesnt work any solutions yet? plugin is fantastic, but cant use it in productive right now cause all the folks in the company complain clicking build now doesnt work 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] (JENKINS-13785) Use Google Apis SDK Add-on via Target ID fails
Christopher Orr commented on JENKINS-13785 Use Google Apis SDK Add-on via Target ID fails Sorry, I somehow completely missed this issue being created... Can you perhaps explain more what you mean by "leads to problems in the build"? I just re-tested using target names like "Google Inc.:Google APIs:7" in both freestyle and matrix jobs and had no problems, with either automatically installing these targets, or starting emulators. 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] (JENKINS-17126) Don't enable snapshots by default as they're horrendously unreliable
Christopher Orr created JENKINS-17126 Dont enable snapshots by default as theyre horrendously unreliable Issue Type: Improvement Assignee: Christopher Orr Components: android-emulator Created: 08/Mar/13 11:09 AM Description: Do snapshots actually work at all in the latest Android SDK or platform versions? The Android folk really seem to have given up on making this actually stable, which is annoying. Since I made snapshots default to "on" a long time ago, this is probably screwing up builds for people. Plus the snapshot functionality is arguably not required now that we have super-speedy x86 images... Project: Jenkins Priority: Major Reporter: Christopher Orr 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] (JENKINS-17055) Git 1.2: only one remote is actually added
Tomasz Bartczak commented on JENKINS-17055 Git 1.2: only one remote is actually added @Frederic Lonngren you're right the problem is on fetch. I see that the problem on fetch has its root cause in not having a Remote Git defined. Making Jenkins clone all remotes may be not very effective, but ensures remotes are added. I don't know why they are not added. In normal flow they should be added https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L792 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] (JENKINS-17055) Git 1.2: only one remote is actually added
Tomasz Bartczak edited a comment on JENKINS-17055 Git 1.2: only one remote is actually added @Fredric Lonngren you're right the problem is on fetch. I see that the problem on fetch has its root cause in not having a Remote Git defined. Making Jenkins clone all remotes may be not very effective, but ensures remotes are added. I don't know why they are not added. In normal flow they should be added https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L792 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] (JENKINS-17127) Pass DISPLAY as environment variable to Maven builds
Uwe Stuehler created JENKINS-17127 Pass DISPLAY as environment variable to Maven builds Issue Type: Improvement Assignee: zregvart Components: xvfb Created: 08/Mar/13 12:04 PM Description: For a freestyle project with an "Invoke top-level Maven targets" build step and the Xvfb plugin enabled, the display number is not passed in the DISPLAY environment variable, but as a property, instead: jenkins@ci4:~$ env|grep DISPLAY DISPLAY=:85 jenkins@ci4:~$ ps -ef|grep firef jenkins 31202 22976 0 17:48 ?00:00:00 /bin/sh /opt/maven3.0.4/bin/mvn -f pom.xml -Dtestsuite=Document -DDISPLAY=:7 clean install -B -Dwebdriver.firefox.bin=/opt/firefox-esr/firefox -Dtest=TestSuiteDocument -Djava.io.tmpdir=/home/jenkins/workspace/selenium-tests/tmp -Dmaven.repo.local=/home/jenkins/workspace/selenium-tests/.repository jenkins 31236 31202 19 17:48 ?00:00:09 /opt/java/bin/java -Djava.io.tmpdir=/tmp/tmp_maven.31202.tmp -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m -classpath /opt/maven3.0.4/boot/plexus-classworlds-2.4.jar -Dclassworlds.conf=/opt/maven3.0.4/bin/m2.conf -Dmaven.home=/opt/maven3.0.4 org.codehaus.plexus.classworlds.launcher.Launcher -f pom.xml -Dtestsuite=Document -DDISPLAY=:7 clean install -B -Dwebdriver.firefox.bin=/opt/firefox-esr/firefox -Dtest=TestSuiteDocument -Djava.io.tmpdir=/home/jenkins/workspace/selenium-tests/tmp -Dmaven.repo.local=/home/jenkins/workspace/selenium-tests/.repository jenkins 31375 31323 40 17:49 ?00:00:16 /opt/firefox-esr/firefox -foreground jenkins 31416 27994 0 17:49 pts/000:00:00 grep firef jenkins@ci4:~$ sed -e 's/.*DISPLAY=//' /proc/31375/environ :85... Outside of the build, the DISPLAY variable is set to :85, Jenkins passes -DDISPLAY=:7 to Maven, but the firefox process still has DISPLAY=:85 in its environment. If we convert our build step to "Execute shell", everything works as expected but then we have to "hard-code" the Maven version instead of choosing one from the Maven installations that we configured globally. Would it be hard to change the behaviour so that the DISPLAY environment variable gets set instead, or in addition to the Java property? Environment: Debian 6.0.3 Jenkins 1.501 Xvfb plugin 1.0.7 Project: Jenkins Priority: Minor Reporter: Uwe Stuehler 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] (JENKINS-17128) Quoted label expression can result into throwing exception
vjuranek created JENKINS-17128 Quoted label _expression_ can result into throwing exception Issue Type: Bug Assignee: vjuranek Components: core Created: 08/Mar/13 12:59 PM Description: If user use quoted label _expression_ which already exists, it will result in ClassCastException (whole exception is bellow). The result is that all on slave page no labels are shown and also no tied project are shown. 2013-03-07 06:53:59,668 WARNING [hudson.ExpressionFactory2$JexlExpression] (Handling GET /hudson/computer/vmg36-ipv6-rhel6-x86_64/ : ajp-127.0.0.1-8009-51) Caught exception evaluating: it.tiedJobs. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1632.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: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.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:269) 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.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.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:269) 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.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.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.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
[JIRA] (JENKINS-17128) Quoted label expression can result into throwing exception
vjuranek commented on JENKINS-17128 Quoted label _expression_ can result into throwing exception proposed solution: https://github.com/jenkinsci/jenkins/pull/730 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] (JENKINS-16627) Fail to parse jmeter report
Reinier Boon commented on JENKINS-16627 Fail to parse jmeter report I had a similar issue. I was using Jmeter-2.9 so i downgraded Jmeter to an older version. I have now Jmeter-2.6 and that solved the issue for me. 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] (JENKINS-12340) Maven job type disables slf4j logging
evernat resolved JENKINS-12340 as Fixed Maven job type disables slf4j logging I think that the last comment was fixed by JENKINS-12650, so resolving as fixed. With JENKINS-12650, slf4j-api and slf4j-jdk14 are now bundled in core. Change By: evernat (08/Mar/13 1:33 PM) Status: Reopened 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 -- 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] (JENKINS-15954) [RTC Plugin] NullPointerException
Danny Beerens commented on JENKINS-15954 [RTC Plugin] NullPointerException From the logs of Jenkins, it appears as if the lscm accept function is called without the login details (i.e. -r -u -P parameters). All previously called lscm commands are called with these login 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 -- 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] (JENKINS-15954) [RTC Plugin] NullPointerException
Danny Beerens edited a comment on JENKINS-15954 [RTC Plugin] NullPointerException I previously added my request to the comments failing to realize to check the Issue Log of this plugin. Hence this remark here: From the logs of Jenkins, it appears as if the lscm accept function is called without the login details (i.e. -r -u -P parameters). All previously called lscm commands are called with these login 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 -- 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] (JENKINS-15954) [RTC Plugin] NullPointerException
Danny Beerens edited a comment on JENKINS-15954 [RTC Plugin] NullPointerException I previously added my complaint to the comments failing to realize to check the Issue Log of this plugin. Hence this remark here: From the logs of Jenkins, it appears as if the lscm accept function is called without the login details (i.e. -r -u -P parameters). All previously called lscm commands are called with these login 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 -- 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] (JENKINS-15954) [RTC Plugin] NullPointerException
Danny Beerens edited a comment on JENKINS-15954 [RTC Plugin] NullPointerException I previously added my complaint to the comments failing to realize to check the Issue Log of this plugin. Hence this remark here: From the logs of Jenkins, it appears as if the 'lscm accept'-function is called without the login details (i.e. -r -u -P parameters). Because the function doesn't know which RTC Repository to contact, it throws the java.NullPointerException's. By-the-way: All previously called lscm commands are called with these login details. And if you run the lscm accept command yourself from the command line, using the login details, all is okay. We now have a command script running as a work-around, but we'd REALLY like this issue solved. 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] (JENKINS-17129) Gradle plugin does not support HudsonTestCase
Roland Gruber created JENKINS-17129 Gradle plugin does not support HudsonTestCase Issue Type: Bug Assignee: abayer Components: gradle-jpi-plugin Created: 08/Mar/13 2:11 PM Description: It is not possible to run JUnit tests with the standard test class HudsonTestCase in a Gradle build script. This is the error message: java.lang.NoClassDefFoundError: hudson/tasks/Ant$AntInstallation at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.getDeclaredMethods(Class.java:1791) at junit.framework.TestSuite.addTestsFromTestCase(TestSuite.java:149) at junit.framework.TestSuite.init(TestSuite.java:129) at org.junit.internal.runners.JUnit38ClassRunner.init(JUnit38ClassRunner.java:71) at org.junit.internal.builders.JUnit3Builder.runnerForClass(JUnit3Builder.java:14) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:52) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:42) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:71) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:49) 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.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at $Proxy2.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:103) 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.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:355) at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:66) 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) Caused by: java.lang.ClassNotFoundException: hudson.tasks.Ant$AntInstallation at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 36 more If I manually add the dependency jenkinsPlugins(group: org.jenkins-ci.plugins, name: ant, version: 1.1, ext: jar) then I get this:
[JIRA] (JENKINS-17130) Plugin messes up repository URLs
Roland Gruber
created JENKINS-17130
Plugin messes up repository URLs
Issue Type:
Bug
Assignee:
abayer
Components:
gradle-jpi-plugin
Created:
08/Mar/13 2:21 PM
Description:
The plugin injects the public Maven repositories. When running a build behind a firewall with local Maven repository this will cause the build to take a very long time (30-60min).
I had to remove the repository URLs after the plugin was loaded.
It would be better if the repository URLs are documented in the Wiki but not injected by default.
Workaround:
// remove external repositories that were injected by JPI plugin - we only use our local Nexus
repositories {
all { repo -
if (repo.url.toString().contains("http://repo1.maven.org/") || repo.url.toString().contains("http://maven.jenkins-ci.org/")) {
logger.warn "Repository ${repo.url} REMOVED"
remove repo
}
}
}
Project:
Jenkins
Priority:
Critical
Reporter:
Roland Gruber
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] (JENKINS-17094) Parametrized Build not running in Jenkins Version 1.504 on Mouse Over event
cjo9900 updated JENKINS-17094 Parametrized Build not running in Jenkins Version 1.504 on Mouse Over event This is core parameters not parameterized trigger plugin Change By: cjo9900 (08/Mar/13 2:39 PM) Labels: parameter Assignee: huybrechts Component/s: parameters Component/s: parameterized-trigger 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] (JENKINS-17009) Parameters with newlines should be stored as TextParameterValue
cjo9900 commented on JENKINS-17009 Parameters with newlines should be stored as TextParameterValue Can you create a pull request on github for this? 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/groups/opt_out.
[JIRA] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
rsandell commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit I think the "posting configuration xml" feature is using the same code in core that reload config from disk is using, so yes it is a very likely it is a similar issue. When we had the bug in the past it was due to the way the GerritHandler (a class in the trigger plugin) was storing each listener i.e. each GerritTrigger instance to notify when an event arrives. And when reload from disk is performed Jenkins actually creates new instances of each job and for some reason the old job instance wasn't removed from the listeners list. We solved it by implementing the list as a HashMap with the project name as the key so when a project added itself twice the instance from the last invocation was the one saved in the map. But that caused a bug when a project was renamed, so that was fixed by using a Set instead I think, maybe that caused the original bug to reappear. Anyways; some hints on how the flow goes during startup might be of help to anyone wanting to dig into this bug. When Jenkins starts: PluginImpl.start() is called before any jobs are loaded. PluginImpl will instanciate a GerritHandler that handles the communication and stream-events coordination towards Gerrit. Then when each job has been loaded GerritTrigger.start() is called, and that will add the GerritTrigger instance as a listener in GerritHandler (via a call to PluginImpl.addListener). When a job is removed or unloaded GerritTrigger.stop is called and that will remove the GerritTrigger instance as a listener. The same happens when you reconfigure a job in Jenkins. When save is clicked first stop will be called on the old instance of GerritTrigger, then a new instance is created by Jenkins and start is called on that. So in theory everything should be fine, but something is handled differently when the config is changed from disk or other than clicking save in the UI. Maybe stop is never called or called in a different order so the old instance isn't removed. Or maybe it's a new bug completely (but probably unlikely). 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] (JENKINS-17013) Git plugin fails with NPE (Jenkins 1.502, 1.503)
Jesse Glick updated JENKINS-17013 Git plugin fails with NPE (Jenkins 1.502, 1.503) Change By: Jesse Glick (08/Mar/13 3:49 PM) Priority: Major Blocker 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] (JENKINS-10520) clone-workspace-scm performance is poor
Pedro Rodriguez commented on JENKINS-10520 clone-workspace-scm performance is poor I'm getting this slow performance locally (unzipping and zipping locally, no slaves or anything) and it is still very slow (4min for something that takes 1s if done manually). Looking at the code, it looks like they are just using the FilePath.zip and tar methods. So not sure if this is an issue in the plugin or in the FilePath. 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] (JENKINS-17013) Git plugin fails with NPE (Jenkins 1.502, 1.503)
Jesse Glick commented on JENKINS-17013 Git plugin fails with NPE (Jenkins 1.502, 1.503) resolveGitTool() returning 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/groups/opt_out.
[JIRA] (JENKINS-17131) Some weird exceptions while archiving with raspberry as slave
C. S. created JENKINS-17131 Some weird exceptions while archiving with raspberry as slave Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Mar/13 4:59 PM Description: Executing the archive artifacts step you can find in the slave log following messages: Failed to load native POSIX impl; falling back on Java impl. Stacktrace follows. java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native at org.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96) at org.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65) at org.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24) at hudson.os.PosixAPI.clinit(PosixAPI.java:41) at hudson.util.IOUtils.mode(IOUtils.java:125) at hudson.util.io.TarArchiver.visit(TarArchiver.java:102) at hudson.util.DirScanner$Glob.scan(DirScanner.java:133) at hudson.FilePath.writeToTar(FilePath.java:1939) at hudson.FilePath.access$1000(FilePath.java:168) at hudson.FilePath$36.invoke(FilePath.java:1880) at hudson.FilePath$36.invoke(FilePath.java:1876) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) 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:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) This error only occurs when trying to archive the artifcats. I have a full build process which works without any errors. Installing the package "libjna-posix-java" fix the above shown exception and result into another exception: Failed to load native POSIX impl; falling back on Java impl. Stacktrace follows. java.lang.UnsatisfiedLinkError: Unable to load library 'libc.so.6': com.sun.jna.Native.open(Ljava/lang/String;)J at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166) at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239) at com.sun.jna.Library$Handler.init(Library.java:140) at com.sun.jna.Native.loadLibrary(Native.java:366) at org.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96) at org.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65) at org.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24) at hudson.os.PosixAPI.clinit(PosixAPI.java:41) at hudson.util.IOUtils.mode(IOUtils.java:125) at hudson.util.io.TarArchiver.visit(TarArchiver.java:102) at hudson.util.DirScanner$Glob.scan(DirScanner.java:133) at hudson.FilePath.writeToTar(FilePath.java:1939) at hudson.FilePath.access$1000(FilePath.java:168) at hudson.FilePath$36.invoke(FilePath.java:1880) at hudson.FilePath$36.invoke(FilePath.java:1876) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) 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:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) But in general it seems to work. There is only an information in the log: log4j:WARN No appenders could be found for logger (org.apache.commons.beanutils.converters.BooleanConverter). log4j:WARN Please initialize the log4j system properly. If there is a possibility to get more details from the slave client, please tell me. I couldn't find anything in the wiki.
[JIRA] (JENKINS-17131) Some weird exceptions while archiving with raspberry as slave
C. S.
updated JENKINS-17131
Some weird exceptions while archiving with raspberry as slave
Just formatted the text.
Change By:
C. S.
(08/Mar/13 5:01 PM)
Description:
Executingthearchiveartifactsstepyoucanfindintheslavelogfollowingmessages:
{quote}
FailedtoloadnativePOSIXimpl;fallingbackonJavaimpl.Stacktracefollows.java.lang.NoClassDefFoundError:Couldnotinitializeclasscom.sun.jna.Native atorg.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96) atorg.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65) atorg.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24) athudson.os.PosixAPI.clinit(PosixAPI.java:41) athudson.util.IOUtils.mode(IOUtils.java:125) athudson.util.io.TarArchiver.visit(TarArchiver.java:102) athudson.util.DirScanner$Glob.scan(DirScanner.java:133) athudson.FilePath.writeToTar(FilePath.java:1939) athudson.FilePath.access$1000(FilePath.java:168) athudson.FilePath$36.invoke(FilePath.java:1880) athudson.FilePath$36.invoke(FilePath.java:1876) athudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) atjava.lang.Thread.run(Thread.java:722)
{quote}
Thiserroronlyoccurswhentryingtoarchivetheartifcats.Ihaveafullbuildprocesswhichworkswithoutanyerrors.Installingthepackage
*
libjna-posix-java
*
fixtheaboveshownexceptionandresultintoanotherexception:
{quote}
FailedtoloadnativePOSIXimpl;fallingbackonJavaimpl.Stacktracefollows.java.lang.UnsatisfiedLinkError:Unabletoloadlibrarylibc.so.6:com.sun.jna.Native.open(Ljava/lang/String;)J atcom.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166) atcom.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239) atcom.sun.jna.Library$Handler.init(Library.java:140) atcom.sun.jna.Native.loadLibrary(Native.java:366) atorg.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96) atorg.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65) atorg.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24) athudson.os.PosixAPI.clinit(PosixAPI.java:41) athudson.util.IOUtils.mode(IOUtils.java:125) athudson.util.io.TarArchiver.visit(TarArchiver.java:102) athudson.util.DirScanner$Glob.scan(DirScanner.java:133) athudson.FilePath.writeToTar(FilePath.java:1939) athudson.FilePath.access$1000(FilePath.java:168) athudson.FilePath$36.invoke(FilePath.java:1880) athudson.FilePath$36.invoke(FilePath.java:1876) athudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) atjava.lang.Thread.run(Thread.java:722)
{quote}
Butingeneralitseemstowork.Thereisonlyaninformationinthelog:
{quote}
log4j:WARNNoappenderscouldbefoundforlogger(org.apache.commons.beanutils.converters.BooleanConverter).log4j:WARNPleaseinitializethelog4jsystemproperly.
{quote}
Ifthereisapossibilitytogetmoredetailsfromtheslaveclient,pleasetellme.Icouldntfindanythinginthewiki.
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:
[JIRA] (JENKINS-16415) Unable to add project roles using Role stratedy plugin
Chris Engler commented on JENKINS-16415 Unable to add project roles using Role stratedy plugin Issues still exists in verion 1.504 Jenkins. Plug in version 1.1.2. 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] (JENKINS-16415) Unable to add project roles using Role stratedy plugin
Chris Engler edited a comment on JENKINS-16415 Unable to add project roles using Role stratedy plugin Issue still exists in verion 1.504 Jenkins in Windows XP. Plug in version 1.1.2. 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] (JENKINS-16415) Unable to add project roles using Role stratedy plugin
Chris Engler edited a comment on JENKINS-16415 Unable to add project roles using Role stratedy plugin Issue still exists in version 1.504 Jenkins in Windows XP. Plug in version 1.1.2. 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] (JENKINS-17132) Warnings plugin stuck parsing the console with a regex and blocks other builds using the same plugin to complete
jhurne created JENKINS-17132 Warnings plugin stuck parsing the console with a regex and blocks other builds using the same plugin to complete Issue Type: Bug Assignee: Ulli Hafner Attachments: warnings-plugin-thread-dump.txt Components: warnings Created: 08/Mar/13 5:10 PM Description: Some of our builds are getting "stuck" when running the Warnings plugin during the publish phase of the build. The builds affected are configured to use the "Javac (Eclipse)" parser and the "Javadoc" parser. The parsers are configured against the console log only. When a build gets stuck running the Warnings plugin, any other build that also uses the Warnings plugin and is running at about the same time also gets stuck. Eventually, all of our slaves are consumed with builds stuck at the warnings plugin step and no further builds can be built. We are able to kill all of the builds except the one build which triggered the problem. In order to kill the original build we end up restarting the entire Jenkins system. We did some investigation and it appears that the Warnings plugin is getting stuck while using a regular _expression_ to parse the console log. The thread dump of Jenkins shows that the Warnings plugin has a deep stack running a regular _expression_ (see attached), and a quick peak at the system itself shows that the plugin is consuming 100% of one of our server's cpu cores. It is clear from the thread stack and the build console log that the plugin is getting stuck when using the "Java (Eclipse)" plugin. We know there have been problems in the past with parsing very large logs or files, however, the build console log is not very large (23kb). We let the stuck build run for about 18 hours before we decided to kill it. We know the plugin was doing work (a) because the CPU core was pegged at 100%, and (b) the stack trace for the plugin worker thread would change periodically. Environment: Jenkins 1.480.3 running on Oracle Java version 1.7.0_03-b04 on 64-bit Linux Warnings Plugin 4.32 Project: Jenkins Labels: warnings Priority: Major Reporter: jhurne 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] (JENKINS-17133) Implement a script based trigger to allow users to have customized triggers
Alex Earl created JENKINS-17133 Implement a script based trigger to allow users to have customized triggers Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 08/Mar/13 6:31 PM Description: Many users would like to create their own trigger logic, providing a method to use a script to test whether or not to send an email would be valuable. Project: Jenkins Priority: Major Reporter: Alex Earl 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] (JENKINS-17134) plugin description source inconsistency
Max Spring created JENKINS-17134 plugin description source inconsistency Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Mar/13 6:37 PM Description: For uninstalled plugins, the Plugin Manager uses the content of the excerpt macro from a plugin's Wiki page as description string. For installed plugins, the description string is coming from the plugin's src/main/resources/index.jelly file. This inconsistency is confusing. Can this be resolved, so that there's a single point of truth? Project: Jenkins Priority: Trivial Reporter: Max Spring 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] (JENKINS-17132) Warnings plugin stuck parsing the console with a regex and blocks other builds using the same plugin to complete
Christian Höltje commented on JENKINS-17132 Warnings plugin stuck parsing the console with a regex and blocks other builds using the same plugin to complete We can try to sanitize the log file so we can post it. (I work with jhurne) Better would be tell us what you're looking for and we can post just that. Or if you have tests you'd like us to run (like a raw regex) we can run that. It's also worth mentioning that we weren't sure why it was set to the Eclipse parser. We have switched that build to use the javac parser instead, because we're just doing a straight maven build. I'm not even sure how you can compile in Jenkins with Eclipse. 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] (JENKINS-17135) TAP should display test name/description if available
TJ Fontaine created JENKINS-17135 TAP should display test name/description if available Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: Screen Shot 2013-03-08 at 10.47.25 AM.png Components: tap Created: 08/Mar/13 6:50 PM Description: The "TAP Stream Results"/testTapReport page should show the test description if it's available instead of just the test number. In my local plugin I've replaced getTestNumber with getDescription in TapTestResultResult.java and attached a screenshot of the result. Project: Jenkins Labels: tap testreport Priority: Major Reporter: TJ Fontaine 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] (JENKINS-17134) plugin description source inconsistency
Max Spring commented on JENKINS-17134 plugin description source inconsistency This is in particular unfortunate, if you want to have a hyperlink in the description. The excerpt macro doesn't treat a href's properly in Wiki, you have to use the '...' syntax. But this syntax doesn't work when the excerpt string is shown in the Plugin Manager. 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] (JENKINS-17136) TAP testReport not listing failing tests for configurations
TJ Fontaine created JENKINS-17136 TAP testReport not listing failing tests for configurations Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: Screen Shot 2013-03-08 at 10.51.29 AM.png Components: tap Created: 08/Mar/13 6:56 PM Description: On the aggregate test result page we can see how many tests pass/fail/skip for each configuration, but where it should be displaying failing tests for that configuration none are displayed Environment: jenkins 1.504 tap plugin 1.10 smartos host Project: Jenkins Labels: tap testreport Priority: Major Reporter: TJ Fontaine 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] (JENKINS-17134) plugin description source inconsistency
Max Spring commented on JENKINS-17134 plugin description source inconsistency It appears that only simple 'Wiki Page' links don't see to work. A full link 'text' seems to get converted propery into the plugin description in the Plugin Manager. 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] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
Pedro Rodriguez commented on JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they dont exist This was reported 2 years ago and it isn't even assigned? 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] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
evernat commented on JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they dont exist @Pedro "isn't even assigned" I see the name of a few people involved in this issue and who can take this issue, including you if you just want to. 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] (JENKINS-17135) TAP should display test name/description if available
TJ Fontaine commented on JENKINS-17135 TAP should display test name/description if available I submitted a pull request https://github.com/jenkinsci/tap-plugin/pull/2 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] (JENKINS-17137) Bogus permalinks created when using external builds directory
Jesse Glick
created JENKINS-17137
Bogus permalinks created when using external builds directory
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
core
Created:
08/Mar/13 11:58 PM
Description:
If you set the external builds directory for Jenkins to e.g. /tmp/builds/${ITEM_FULL_NAME} and build some job, you will get a symlink /tmp/builds/lastStable pointing to builds/2013-... which does not exist. The symlink should be created in the job's root directory, as it would be if the builds dir were not set (except with an absolute target path in this case).
Project:
Jenkins
Priority:
Minor
Reporter:
Jesse Glick
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] (JENKINS-17138) Deleting/renaming jobs using external builds directory does not move builds
Jesse Glick
created JENKINS-17138
Deleting/renaming jobs using external builds directory does not move builds
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
core
Created:
09/Mar/13 12:00 AM
Description:
If you set the external builds directory for Jenkins to e.g. /tmp/builds/${ITEM_FULL_NAME} and build some job, then rename it, the existing build records will remain in /tmp/builds/oldname/* and be inaccessible. Similarly, if you delete the job, the build records will be left behind, potentially consuming a great deal of disk space.
Project:
Jenkins
Priority:
Major
Reporter:
Jesse Glick
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] (JENKINS-17138) Deleting/renaming jobs using external builds directory does not move builds
Jesse Glick commented on JENKINS-17138 Deleting/renaming jobs using external builds directory does not move builds Job.renameTo needs to take getBuildDir into account. Also the workspace on master should be moved if it exists. 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] (JENKINS-17139) Grinder: Always Update Graphs
Ville Koskela created JENKINS-17139 Grinder: Always Update Graphs Issue Type: Improvement Assignee: asgeirn Attachments: grinder.hpi, grinder.jenkins.diff, grinder.jenkins.png Components: grinder Created: 09/Mar/13 12:43 AM Description: The Grinder Jenkins plugin only reloads graphs if the underlying project has changed: https://github.com/jenkinsci/grinder-plugin/blob/master/src/main/java/hudson/plugins/grinder/AbstractGrinderAction.java#L29 In my use case the performance tests are initiated by a separate project from the actual code and until we integrate continuous deployment the tests are run by users on demand. Consequently, the project has not changed and the graphs are not updated. In order for the graphs to be updated I added a configuration switch to the plugin to always update the graphs. I've never worked in the codebase (Jenkins or Grinder) so I may have misunderstood the model; but this did solve our problem. I have included a screenshot, diff and compiled HPI file. The results were tested under Jenkins 1.503. Project: Jenkins Priority: Major Reporter: Ville Koskela 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] (JENKINS-17137) Bogus permalinks created when using external builds directory
SCM/JIRA link daemon resolved JENKINS-17137 as Fixed Bogus permalinks created when using external builds directory Change By: SCM/JIRA link daemon (09/Mar/13 1:09 AM) 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 -- 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] (JENKINS-17137) Bogus permalinks created when using external builds directory
SCM/JIRA link daemon commented on JENKINS-17137 Bogus permalinks created when using external builds directory Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractBuild.java test/src/test/java/hudson/model/AbstractProjectTest.java http://jenkins-ci.org/commit/jenkins/b90b20227e7e2497856404a1ca4e771e282504ff Log: FIXED JENKINS-17137 Bogus permalinks created when using external builds directory. Compare: https://github.com/jenkinsci/jenkins/compare/400fa878e66c...b90b20227e7e You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-17133) Implement a script based trigger to allow users to have customized triggers
SCM/JIRA link daemon commented on JENKINS-17133 Implement a script based trigger to allow users to have customized triggers Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/EmailExtensionPlugin.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/plugins/EmailTriggerDescriptor.java src/main/java/hudson/plugins/emailext/plugins/trigger/AbortedTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/AbstractScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FirstFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FixedTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/ImprovementTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/NotBuiltTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/NthFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/PreBuildScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/PreBuildTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/ScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/SecondFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/StillFailingTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/StillUnstableTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/SuccessTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/UnstableTrigger.java src/main/resources/hudson/plugins/emailext/plugins/trigger/Messages.properties src/main/resources/hudson/plugins/emailext/plugins/trigger/PreBuildScriptTrigger/local-config.groovy src/main/resources/hudson/plugins/emailext/plugins/trigger/ScriptTrigger/local-config.groovy src/main/resources/hudson/plugins/emailext/tags/mailtype.jelly src/main/webapp/help/projectConfig/trigger/ScriptTrigger.html src/test/java/hudson/plugins/emailext/plugins/trigger/FirstFailureTriggerTest.java src/test/java/hudson/plugins/emailext/plugins/trigger/SecondFailureTriggerTest.java http://jenkins-ci.org/commit/email-ext-plugin/d81fd835c8b948080a2ffe30521742066d33916e Log: Fix JENKINS-17133 Implemented a script based trigger and a prebuild script based trigger You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-17133) Implement a script based trigger to allow users to have customized triggers
Alex Earl resolved JENKINS-17133 as Fixed Implement a script based trigger to allow users to have customized triggers Change By: Alex Earl (09/Mar/13 1:13 AM) 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 -- 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] (JENKINS-17133) Implement a script based trigger to allow users to have customized triggers
Alex Earl updated JENKINS-17133 Implement a script based trigger to allow users to have customized triggers Snapshot of 2.28 with initial script trigger support. Change By: Alex Earl (09/Mar/13 1:29 AM) Attachment: email-ext.hpi 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] (JENKINS-17138) Deleting/renaming jobs using external builds directory does not move builds
SCM/JIRA link daemon resolved JENKINS-17138 as Fixed Deleting/renaming jobs using external builds directory does not move builds Change By: SCM/JIRA link daemon (09/Mar/13 1:45 AM) 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 -- 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] (JENKINS-17138) Deleting/renaming jobs using external builds directory does not move builds
SCM/JIRA link daemon commented on JENKINS-17138 Deleting/renaming jobs using external builds directory does not move builds Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/Job.java test/src/test/java/hudson/model/AbstractProjectTest.java http://jenkins-ci.org/commit/jenkins/d98716dfbad96f566938b90a5a8b50ce9765575b Log: FIXED JENKINS-17138 Deleting/renaming jobs using external builds directory does not move builds. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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] (JENKINS-17140) Attemp to re-load plugins if there is a failure
Casey McGinty created JENKINS-17140 Attemp to re-load plugins if there is a failure Issue Type: Improvement Assignee: Unassigned Components: plugin Created: 09/Mar/13 2:15 AM Description: Somehow my Jenkins instance started without the Perforce SCM plugin loading correctly. I restarted Jenkins, and it resolved the issue. There was a suggestion on IRC that Jenkins might need to "re-drive plugin load for any failed load at the end of its plugin load process; at least give it another try". Please consider this feature request. If I can reproduce the issue, I'll update the ticket. Project: Jenkins Priority: Minor Reporter: Casey McGinty 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] (JENKINS-17137) Bogus permalinks created when using external builds directory
dogfood commented on JENKINS-17137 Bogus permalinks created when using external builds directory Integrated in jenkins_main_trunk #2357 FIXED JENKINS-17137 Bogus permalinks created when using external builds directory. (Revision b90b20227e7e2497856404a1ca4e771e282504ff) Result = SUCCESS Jesse Glick : b90b20227e7e2497856404a1ca4e771e282504ff Files : core/src/main/java/hudson/model/AbstractBuild.java changelog.html test/src/test/java/hudson/model/AbstractProjectTest.java 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] (JENKINS-14105) Build timeout plugin 1.9 always sets timeout period to 3 minutes
sogabe commented on JENKINS-14105 Build timeout plugin 1.9 always sets timeout period to 3 minutes uum... I can not reproduce this problem. If you specify "absolute timeout" less than 3 minutes, then This plugin saved it as 3 minitues. 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] (JENKINS-14869) ClamAV plugin successfully scans but crashes immediately after
sogabe resolved JENKINS-14869 as Cannot Reproduce ClamAV plugin successfully scans but crashes immediately after If you have this problem yet, please reopen Change By: sogabe (09/Mar/13 2:40 AM) Status: Open Resolved 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/groups/opt_out.
[JIRA] (JENKINS-15606) CloverPHP : error during configuration of cloverPHP in job
sogabe resolved JENKINS-15606 as Cannot Reproduce CloverPHP : error during configuration of cloverPHP in job If you have this problem yet, Please reopen! Change By: sogabe (09/Mar/13 2:42 AM) Status: Open Resolved 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/groups/opt_out.
[JIRA] (JENKINS-16840) Unable to connect to Mantis
sogabe commented on JENKINS-16840 Unable to connect to Mantis any logs? 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] (JENKINS-17138) Deleting/renaming jobs using external builds directory does not move builds
dogfood commented on JENKINS-17138 Deleting/renaming jobs using external builds directory does not move builds Integrated in jenkins_main_trunk #2358 FIXED JENKINS-17138 Deleting/renaming jobs using external builds directory does not move builds. (Revision d98716dfbad96f566938b90a5a8b50ce9765575b) Result = SUCCESS Jesse Glick : d98716dfbad96f566938b90a5a8b50ce9765575b Files : changelog.html test/src/test/java/hudson/model/AbstractProjectTest.java core/src/main/java/hudson/model/Job.java 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] (JENKINS-16449) When a job hits 'Max # of builds to keep' Nunit Publisher starts to throw NPE
Darren Gibson commented on JENKINS-16449 When a job hits Max # of builds to keep Nunit Publisher starts to throw NPE I have the same NPE running on Windows 2008R2 64bit, Jenkins 1.504 and NUnit plugin 0.14. This issue only arose when I upgraded from 1.501 to 1.504 (the next day), but it didn't start immediately and I have other NUnit publications that are working without issue. I do not have the job currently configured to "Discard Old Builds" and I have a around 170 builds in my build history. Recording NUnit tests results ERROR: Publisher hudson.plugins.nunit.NUnitPublisher aborted due to exception java.lang.NullPointerException at hudson.model.Run.getRootDir(Run.java:935) at hudson.tasks.junit.TestResultAction.getDataFile(TestResultAction.java:91) at hudson.tasks.junit.TestResultAction.load(TestResultAction.java:147) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:97) at hudson.tasks.junit.TestResultAction.getResult(TestResultAction.java:55) at hudson.tasks.test.AbstractTestResultAction.findCorrespondingResult(AbstractTestResultAction.java:183) at hudson.tasks.test.TestResult.getPreviousResult(TestResult.java:145) at hudson.tasks.junit.SuiteResult.getPreviousResult(SuiteResult.java:296) at hudson.tasks.junit.CaseResult.getPreviousResult(CaseResult.java:375) at hudson.tasks.junit.CaseResult.freeze(CaseResult.java:486) at hudson.tasks.junit.SuiteResult.freeze(SuiteResult.java:338) at hudson.tasks.junit.TestResult.freeze(TestResult.java:604) at hudson.tasks.junit.TestResultAction.setResult(TestResultAction.java:74) at hudson.tasks.junit.TestResultAction.init(TestResultAction.java:67) at hudson.plugins.nunit.NUnitPublisher.recordTestResult(NUnitPublisher.java:150) at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:109) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) 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.
