[JIRA] (JENKINS-14453) Generate empty cell for missing data
H Mlnarik created JENKINS-14453 Generate empty cell for missing data Issue Type: Bug Assignee: Ognjen Bubalo Attachments: Jenkins-jacoco.png Components: jacoco Created: 17/Jul/12 6:02 AM Description: Method descriptions in Jacoco XML file contains counts for different categories (INSTRUCTION, BRANCH etc.) that are rendered to HTML cells in reports. When some category is missing, nothing is generated. Empty cell is generated instead which is aesthetically not nice (and potentially might shift the results to wrong category?) For example, consider the following XML snippet: ... method name="checkIfRequiredElement" desc="(Ljava/lang/String;Ljava/util/List;Ljava/util/Stack;)Ljava/lang/String;" line="790" counter type="INSTRUCTION" missed="19" covered="51"/ counter type="BRANCH" missed="4" covered="8"/ counter type="LINE" missed="4" covered="19"/ counter type="COMPLEXITY" missed="3" covered="4"/ counter type="METHOD" missed="0" covered="1"/ /method method name="lt;clinitgt;" desc="()V" line="59" counter type="INSTRUCTION" missed="0" covered="4"/ counter type="LINE" missed="0" covered="1"/ counter type="COMPLEXITY" missed="0" covered="1"/ counter type="METHOD" missed="0" covered="1"/ /method ... BRANCH category is missing in clinit, rendering as shown in the attached Jenkins-jacoco.png image. The cell for branch is not rendered at all (confirmed also from HTML source where only four td elements are present). Should render an empty cell (i.e. td/td) or something similar. Project: Jenkins Priority: Major Reporter: H Mlnarik 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
H Mlnarik
updated JENKINS-14453
Generate empty cell for missing data
Change By:
H Mlnarik
(17/Jul/12 6:04 AM)
Description:
MethoddescriptionsinJacocoXMLfilecontainscountsfordifferentcategories(INSTRUCTION,BRANCHetc.)thatarerenderedtoHTMLcellsinreports.Whensomecategoryismissing,nothingisgenerated.Emptycellisgeneratedinsteadwhichisaestheticallynotnice(andpotentiallymightshifttheresultstowrongcategory?)Forexample,considerthefollowingXMLsnippet:...{code}methodname=checkIfRequiredElementdesc=(Ljava/lang/String;Ljava/util/List;Ljava/util/Stack;)Ljava/lang/String;line=790countertype=INSTRUCTIONmissed=19covered=51/countertype=BRANCHmissed=4covered=8/countertype=LINEmissed=4covered=19/countertype=COMPLEXITYmissed=3covered=4/countertype=METHODmissed=0covered=1//methodmethodname=lt;clinitgt;desc=()Vline=59countertype=INSTRUCTIONmissed=0covered=4/countertype=LINEmissed=0covered=1/countertype=COMPLEXITYmissed=0covered=1/countertype=METHODmissed=0covered=1//method{code}...BRANCHcategoryismissingin{{clinit}},renderingasshownintheattachedJenkins-jacoco.pngimage.Thecellforbranchisnotrenderedatall(confirmedalsofromHTMLsourcewhereonly
four
five
{{td}}elementsarepresent
,shouldbesix
).Shouldrenderanemptycell(i.e.{{tdnbsp;/td}})orsomethingsimilar.
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-14454) Cobertura Publisher does not keep settings when used in flexible-publish
Capn Keelhauler created JENKINS-14454 Cobertura Publisher does not keep settings when used in flexible-publish Issue Type: Bug Affects Versions: current Assignee: bap Components: flexible-publish Created: 17/Jul/12 6:13 AM Description: I am using Run Condition Plugin to run cobertura only on weekends. So I also need to use Flexible-Publish to run Publish Cobertura Coverage Report only on weekends. I installed flexible-publish and manually created a Flexible-Publish post-build action. I then manually copied the details from my original Publish Cobertura Coverage Report action into the flexible-publish version and hit save. The targets tags are empty in the Flexible-Publish version. If I add them via config.xml and then reload them via Jenkins, everything is fine. However, if I then save my project, the targts tags become empty again. BEFORE: healthyTarget targets class="enum-map" enum-type="hudson.plugins.cobertura.targets.CoverageMetric" entry hudson.plugins.cobertura.targets.CoverageMetricCONDITIONAL/hudson.plugins.cobertura.targets.CoverageMetric int74/int /entry entry hudson.plugins.cobertura.targets.CoverageMetricLINE/hudson.plugins.cobertura.targets.CoverageMetric int67/int /entry entry hudson.plugins.cobertura.targets.CoverageMetricMETHOD/hudson.plugins.cobertura.targets.CoverageMetric int64/int /entry /targets /healthyTarget unhealthyTarget targets class="enum-map" enum-type="hudson.plugins.cobertura.targets.CoverageMetric" entry hudson.plugins.cobertura.targets.CoverageMetricCONDITIONAL/hudson.plugins.cobertura.targets.CoverageMetric int0/int /entry entry hudson.plugins.cobertura.targets.CoverageMetricLINE/hudson.plugins.cobertura.targets.CoverageMetric int0/int /entry entry hudson.plugins.cobertura.targets.CoverageMetricMETHOD/hudson.plugins.cobertura.targets.CoverageMetric int0/int /entry /targets /unhealthyTarget failingTarget targets class="enum-map" enum-type="hudson.plugins.cobertura.targets.CoverageMetric" entry hudson.plugins.cobertura.targets.CoverageMetricCONDITIONAL/hudson.plugins.cobertura.targets.CoverageMetric int0/int /entry entry hudson.plugins.cobertura.targets.CoverageMetricLINE/hudson.plugins.cobertura.targets.CoverageMetric int0/int /entry entry hudson.plugins.cobertura.targets.CoverageMetricMETHOD/hudson.plugins.cobertura.targets.CoverageMetric int0/int /entry /targets /failingTarget After healthyTarget targets class="enum-map" enum-type="hudson.plugins.cobertura.targets.CoverageMetric"/ /healthyTarget unhealthyTarget targets class="enum-map" enum-type="hudson.plugins.cobertura.targets.CoverageMetric"/ /unhealthyTarget failingTarget targets class="enum-map" enum-type="hudson.plugins.cobertura.targets.CoverageMetric"/ /failingTarget Environment: Win Server 2008 R2 Jenkins 1.474 Jenkins Cobertura Plugin 1.5 Project: Jenkins Priority: Major Reporter: Capn Keelhauler This message is automatically generated
[JIRA] (JENKINS-14455) [cppcheck] Wrong job status set based on new errors treshold
M S created JENKINS-14455 [cppcheck] Wrong job status set based on new errors treshold Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: cppcheck Created: 17/Jul/12 8:21 AM Description: Even though CppCheck results page from the analyzis doesn't show new errors (and the sum of errors doesn't change between 2 runs), in the console output of the job we can see that it sets build as unstable as new errors were found. Cppcheck Setting build status to UNSTABLE since total number of new errors (With all severity values) exceeds the threshold value '1'. Cppcheck Ending the cppcheck analysis. Severity Error (nb/new) : 46/+0 Severity Warning (nb/new) : 2405/+0 Severity Style (nb/new) : 1736/+0 Severity Performance (nb/new) : 1506/+0 Severity Information (nb/new) : 0/+0 Severity Unknown (nb/new) : 11/0 Environment: Linux, cppcheck version 1.55, jenkins 1.471, cppcheck plugin 1.9 Project: Jenkins Priority: Major Reporter: M S 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-13892) Analysis collector marks some warnings as fixed even though they are not
naveen karnati updated JENKINS-13892 Analysis collector marks some warnings as fixed even though they are not Apologies for delayed response. Attached is the build.xml (I could retrieve the xml file from jobconfighistory plugin we are using). Thanks for your continued support to Jenkins Change By: naveen karnati (17/Jul/12 8:51 AM) Attachment: build_may21.xml 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-13253) Slave connection reset issues since 1.456
naveen karnati commented on JENKINS-13253 Slave connection reset issues since 1.456 We have similar issues over here. The socket gets disconnected intermittently. hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset Jenkins ver. 1.410 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-2556) Use svn switch where applicable
Damien Finck commented on JENKINS-2556 Use svn switch where applicable We have this problem too, we currently have to manualy switch the repo and then cascade the changes in the configuration. This is error-prone and not practical. 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-14456) Add support for Workspace Cleanup Plugin
Nickolay Rumyantsev created JENKINS-14456 Add support for Workspace Cleanup Plugin Issue Type: New Feature Assignee: mdonohue Components: configurationslicing Created: 17/Jul/12 9:58 AM Description: It would be great if you add new slicer for Workspace Cleanup Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin). I could do it by myself if you tell me how to contribute to your project. Project: Jenkins Priority: Major Reporter: Nickolay Rumyantsev 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-14121) Nunit plugin 0.13 misses tests sometimes, sometimes not
redsolo commented on JENKINS-14121 Nunit plugin 0.13 misses tests sometimes, sometimes not It would be nice to look into the NUnit XML file when it does miss and does not miss tests. Otherwise it will hard to find the 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-14458) Groovy-Postbuild fails very often
Christoph Moser
created JENKINS-14458
Groovy-Postbuild fails very often
Issue Type:
Bug
Affects Versions:
current
Assignee:
wolfs
Components:
groovy-postbuild
Created:
17/Jul/12 11:39 AM
Description:
We use the Groovy-Postbuild-Plugin to set successful Upstream-Builds to failed, when a downstream-Build failes.
The upstream-Build saves several Artefacts and creates Fingerprints from these.
Some times the Groovy-Postbuild-Plugin works with the code below for ten or more builds, afterwards we get the below mentioned NullPointerException several times without changing anything in the configuration.
Groovy-Code:
upstreamBuilds = manager.build.getUpstreamBuilds();
upstreamJob = upstreamBuilds.keySet().iterator().next();
lastUpstreamBuild = upstreamJob.getLastBuild();
if(lastUpstreamBuild.getResult().isBetterThan(manager.build.result)) {
lastUpstreamBuild.setResult(manager.build.result);
}
Exception:
Groovy script failed:
java.lang.NullPointerException: Cannot invoke method isBetterThan() on null object
at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at Script1.run(Script1.groovy:23)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589)
at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:273)
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.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
at hudson.model.Run.execute(Run.java:1485)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Due Date:
17/Jul/12 12:00 AM
Environment:
Groovy-Postbuild-Plugin-Version: 1.7
Jenkins-Version: 1.470
Machine: Windows XP SP02
Project:
Jenkins
Priority:
Major
Reporter:
Christoph Moser
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-7087) As a build manager, I want to be able to build all branches except for master (BranchSpec needs to support exclusion )
Tomasz Bartczak commented on JENKINS-7087 As a build manager, I want to be able to build all branches except for master (BranchSpec needs to support exclusion ) I would say the only proper solution is to support regexp as branch specifier. For exclusion one can use https://github.com/jenkinsci/git-plugin/pull/45 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-7641) Slaves hang when archiving artifacts
Oliver Bock commented on JENKINS-7641 Slaves hang when archiving artifacts Same behavior here on OS X 10.4 slave (JRE 1.5.0_19, slave.jar 2.16). As described by @crusius, although I can cancel the job if I try it twice. Then I get the following, slightly different error: Archiving artifacts ERROR: Failed to archive artifacts: build.log, dist/* hudson.util.IOException2: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175) at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61) at java.io.FilterInputStream.read(FilterInputStream.java:107) at hudson.util.HeadBufferingStream.fillSide(HeadBufferingStream.java:83) at hudson.FilePath$TarCompression$2.extract(FilePath.java:619) at hudson.FilePath.copyRecursiveTo(FilePath.java:1771) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116) 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.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1513) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) at hudson.FilePath.copyRecursiveTo(FilePath.java:1778) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116) 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.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1513) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.util.concurrent.ExecutionException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request$1.get(Request.java:278) at hudson.remoting.Request$1.get(Request.java:210) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.FilePath.copyRecursiveTo(FilePath.java:1774) ... 10 more Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:719) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:90) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 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-11586) Regression introduced with Slave Side ChannelPinger
Oliver Bock commented on JENKINS-11586 Regression introduced with Slave Side ChannelPinger Any update on 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
[JIRA] (JENKINS-14301) Failed to use multiple update sites (plugin repositories)
Nickolay Rumyantsev edited a comment on JENKINS-14301 Failed to use multiple update sites (plugin repositories) I seek through code and found the reason of that bug: list of updates is generated by UpdateCenter.getUpdates(); UpdateCenter.getUpdates() -(call) UpdateSite.getUpdates() for each update site in UpdateCenter.sites. UpdateSite.getUpdates() iterates through ALL plugins from PluginManager.getPlugins() and gets only those that have new version. That means that as a result we have a list which contains (all updates list)x(number of update sites). It works perfectly if we have only one update site. I don't know the best way to fix it while preserving architecture integrity, so I ask someone to fix it. UPD. I put this comment's body into the issue description, so it might be deleted now, but I have not such permissions. 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-14459) Failed to record SCM polling with envinject plugin
Sylvain C. created JENKINS-14459 Failed to record SCM polling with envinject plugin Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 17/Jul/12 12:21 PM Description: When I use envinject plugin to load a property file, I have this error in "Subversion Polling Log" : Started on Jul 17, 2012 2:01:00 PM ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@333e9df3MY_PROJECT java.lang.NullPointerException at java.util.TreeMap.putAll(TreeMap.java:290) at org.jenkinsci.plugins.envinject.EnvInjectBuilderContributionAction.buildEnvVars(EnvInjectBuilderContributionAction.java:23) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:867) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1114) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1377) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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) Environment: Jenkins 1.473 Project: Jenkins Priority: Major Reporter: Sylvain C. 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-14459) Failed to record SCM polling with envinject plugin
Sylvain C. commented on JENKINS-14459 Failed to record SCM polling with envinject plugin With envinject 1.59 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-14460) Anonymous user with no build rights can retrigger a build
Adrian Vlad created JENKINS-14460 Anonymous user with no build rights can retrigger a build Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-pipeline Created: 17/Jul/12 12:28 PM Description: 1. Set up security configuration for Anonymous user with no rights for building jobs, but with rights for reading jobs. 2. Create a pipeline with another user (eg: user FOO) that has all rights and trigger a pipeline build with user FOO. 3. Logout from user FOO. You are now as Anonymous user. Enter the pipeline view and press the trigger button for a build (not the run button from the upside of the pipeline view, but the trigger button from a finished build). 4. The build will start even if the Anonymous user has no rights to start a build. Expectations: the build should not start or, better, the trigger button should not be visible if a user has no rights to build a job Due Date: 17/Jul/12 12:00 AM Environment: Ubuntu 12.04 Jenkins 1.474 Project: Jenkins Priority: Major Reporter: Adrian Vlad 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-14438) Build cause condition fails on matrix projects
cjo9900 commented on JENKINS-14438 Build cause condition fails on matrix projects Test case and fix created and added as pull #7 https://github.com/jenkinsci/run-condition-plugin/pull/7 Note: this requires that the minimum Jenkins version is now 1.424 rather than 1.409 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-13892) Analysis collector marks some warnings as fixed even though they are not
naveen karnati updated JENKINS-13892 Analysis collector marks some warnings as fixed even though they are not oops.. Attached config.xml rather than build.xml in my earlier post. sry.. Attached is the requested build.xml (both reference failed). thanks Change By: naveen karnati (17/Jul/12 1:34 PM) Attachment: failed_build.xml Attachment: reference_build.xml 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-12126) Test Trend Chart should be able to show only the failures
Marco Ambu resolved JENKINS-12126 as Fixed Test Trend Chart should be able to show only the failures Fixed in version 2.3 Change By: Marco Ambu (17/Jul/12 1:33 PM) Status: Open Resolved Fix Version/s: current 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-14461) Warnings plugin no Java 1.5 compatible?
Trevor Bekolay created JENKINS-14461 Warnings plugin no Java 1.5 compatible? Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 17/Jul/12 1:38 PM Description: After upgrading Jenkins and Warnings, my projects no longer showed up. System log was pointing to the Warnings plugin, so I disabled it and they came back. I disabled the post-build trigger and reeanbled Warnings, which didn't cause a problem. However, when I tried to re-add the console output as a post-build step, nothing happens. Looking at the log, I get this output: WARNING: Failed to evaluate the template closure org.apache.commons.jelly.JellyTagException: file:/srv/hudson/plugins/warnings/WEB-INF/classes/hudson/plugins/warnings/WarningsPublisher/config.jelly:4:124: j:invokeStatic Bad version number in .class file at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:735) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:290) 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.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.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java: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.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.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at hudson.widgets.RenderOnDemandClosure$1.generateResponse(RenderOnDemandClosure.java:91) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:104) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:62) at org.kohsuke.stapler.Function.renderResponse(Function.java:103) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:92) at org.kohsuke.stapler.MetaClass$_javascript_ProxyMethodDispatcher.doDispatch(MetaClass.java:439) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625) 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:125) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at
[JIRA] (JENKINS-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay updated JENKINS-14461 Warnings plugin not Java 1.5 compatible? Change By: Trevor Bekolay (17/Jul/12 1:42 PM) Summary: Warningsplugin no not Java1.5compatible? 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-12555) Git checkout fails with JSONException
markewaite commented on JENKINS-12555 Git checkout fails with JSONException There is a similar report in pastebin from 3 Jan 2012 at http://pastebin.com/gncHWbtP . It has the same symptoms and the same message (target class is an array), but uses a different workspace. There is a similar report for the same message against the MongoDB component at https://issues.jenkins-ci.org/browse/JENKINS-12159. I suspect both issues have since been resolved by changes to core. 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-7781) Test Statistics Grid double counting aggregated tests
Marco Ambu commented on JENKINS-7781 Test Statistics Grid double counting aggregated tests Is this still an issue? It seems that the dashboard is behaving correctly anyway because you said: In actuality, my main job has 4 tests, and the three sub jobs have 684 tests in total. dashboard-view is reporting that the main job has 684 tests (so it is counting the subs, but not its own), in addition to the sub jobs, for a total of 1368 tests. So if jenkins is not reporting the 4 tests in the main job either, then I don't think we are doing anything wrong in the dashboard portlet. 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-7781) Test Statistics Grid double counting aggregated tests
Marco Ambu resolved JENKINS-7781 as Not A Defect Test Statistics Grid double counting aggregated tests I'm closing this one. Reopen it, if still an issue. Change By: Marco Ambu (17/Jul/12 1:54 PM) Status: Open Resolved Resolution: NotADefect 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-14333) Clang warning with cmake get parsed incorrectly
SCM/JIRA link daemon resolved JENKINS-14333 as Fixed Clang warning with cmake get parsed incorrectly Change By: SCM/JIRA link daemon (17/Jul/12 2:00 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-14333) Clang warning with cmake get parsed incorrectly
SCM/JIRA link daemon commented on JENKINS-14333 Clang warning with cmake get parsed incorrectly Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/AppleLLVMClangParser.java src/test/java/hudson/plugins/warnings/parser/AppleLLVMClangParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue14333.txt http://jenkins-ci.org/commit/warnings-plugin/2643f1f13b737621f0450f3e6021f514b5c4debd Log: FIXED JENKINS-14333 Ignore progress percentage in warning messages. Compare: https://github.com/jenkinsci/warnings-plugin/compare/84e78dd1371e...2643f1f13b73 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-14462) cppcheck plugin doesn't show results until a build is successful
Chris Welch created JENKINS-14462 cppcheck plugin doesnt show results until a build is successful Issue Type: Bug Assignee: Gregory Boissinot Attachments: cppcheckscreen.bmp Components: cppcheck Created: 17/Jul/12 2:20 PM Description: We have setup our projects so that they fail if there are any cppcheck errors. Unfortunately, we can't see any results on new projects, because the plugin won't display results until a build is successful. But, these builds can't be successful until there are no cppcheck errors. Suppressing the results display for a failed build adds no value and makes it very difficult to fix the cppcheck errors that are causing the build failure. Please turn off all logic related to suppressing results display. The results should be displayed regardless of the status of the build so that cppcheck problems can be investigated and fixed. Environment: Jenkins 1.434 on CentOS 5.7 running as VM Project: Jenkins Priority: Major Reporter: Chris Welch 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-14463) email ext plugin : full console log mail
dev D created JENKINS-14463 email ext plugin : full console log mail Issue Type: Bug Assignee: Slide-O-Mix Components: email-ext Created: 17/Jul/12 2:21 PM Description: I am using email-ext plugin for my success and failure notification. Problem is I amnot able to see full log in the mail. Most the line get truncated. How to show full console in the mail ? Example : ...truncated 22859 lines... Successfully Build Project: Jenkins Priority: Minor Reporter: dev 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-12504) cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure
Chris Welch updated JENKINS-12504 cppcheck-plugin doesnt display the latest source when cppcheck-plugin is the cause of a build failure This problem is still not fixed. We are still seeing old results making it difficult to fix the current problems and giving us confusing information. 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-12504) cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure
Chris Welch reopened JENKINS-12504 cppcheck-plugin doesnt display the latest source when cppcheck-plugin is the cause of a build failure This problem is still not fixed (using plugin 1.9). We are still seeing old results from the last successful build when cppcheck fails the build. Very confusing. Change By: Chris Welch (17/Jul/12 2:24 PM) Resolution: Fixed Status: Resolved Reopened 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-14464) Wipeout permission isn't implied by administer
Yury Mikhailenko commented on JENKINS-14464 Wipeout permission isnt implied by administer ARTIFACTS permission should also have the same problem. It's implied by null as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14464) Wipeout permission isn't implied by administer
Yury Mikhailenko
created JENKINS-14464
Wipeout permission isnt implied by administer
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
17/Jul/12 2:25 PM
Description:
In 1.418 (2011/06/27) there was WipeOut permission introduced.
But when enabling it admins loose ability to do wipeouts.
I think, this happens because permission isn't linked with basic one.
I believe changing line in hudson.model.Item to something like that will fix the problem:
Permission WIPEOUT = new Permission(PERMISSIONS, "WipeOut", Messages._AbstractProject_WipeOutPermission_Description(), Permission.DELETE, Functions.isWipeOutPermissionEnabled(), new PermissionScope[]{PermissionScope.ITEM});
Project:
Jenkins
Priority:
Major
Reporter:
Yury Mikhailenko
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-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? I updated to 4.11 (the latest at http://updates.jenkins-ci.org/download/plugins/warnings/ ) and am still having the same issue. The start of the stack trace (not sure if the rest is useful?): 17-Jul-2012 9:35:01 AM hudson.widgets.RenderOnDemandClosure$1 generateResponse WARNING: Failed to evaluate the template closure org.apache.commons.jelly.JellyTagException: file:/srv/hudson/plugins/warnings/WEB-INF/classes/hudson/plugins/warnings/WarningsPublisher/config.jelly:4:124: j:invokeStatic Bad version number in .class file 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-14278) A parameterized buildstep in a matrix project causes IllegalArgumentException
cjo9900 commented on JENKINS-14278 A parameterized buildstep in a matrix project causes IllegalArgumentException I have also seen this while trying to test other behaviour for the conditional buildstep plugin. However in this case I do not see the exception as this is consumed by the conditional buildstep Runner. however I do see the the following "ERROR: Build aborted. No projects to trigger. Check your configuration!" Looking at the code it points to the function at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.getProjectList(BuildTriggerConfig.java:132) returning an empty list. This is called as ListAbstractProject projectList = config.getProjectList(build.getProject().getParent(),env); However when this is a Matrix project build is a MatrixBuild, and get Project gets the MatrixConfiguration and the parent of that is the MatrixProject which implements the ItemGroupMatrixConfiguration So when Items.fromNameList(context, projectNames.toString(), AbstractProject.class) is called in the context is the MatrixProject so tries to get the project from that. public ListAbstractProject getProjectList(ItemGroup context, EnvVars env) Possible solution would be to do build.getRootBuild().getProject().getParent() which should give the topbuild item in the tree 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-7781) Test Statistics Grid double counting aggregated tests
ellisonch reopened JENKINS-7781 Test Statistics Grid double counting aggregated tests It still seems like an issue to me. I will try to attach more information. Change By: ellisonch (17/Jul/12 2:59 PM) Resolution: NotADefect Status: Resolved Reopened 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-7781) Test Statistics Grid double counting aggregated tests
ellisonch updated JENKINS-7781 Test Statistics Grid double counting aggregated tests Change By: ellisonch (17/Jul/12 3:00 PM) Attachment: stats.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
ellisonch commented on JENKINS-7781 Test Statistics Grid double counting aggregated tests I've added an attachment showing what I mean. If you add up all the child tests except for the csmith-tests, you get 1554. This number is being reported for c-semantics as well. So these tests are double counted in the 3669 total (which makes the % success total meaningless). Furthermore, the 5 tests that belong to c-semantics itself are not counted at all in these numbers. Finally, the csmith-tests are not being double counted, perhaps because the job is disabled. I don't really understand any of these behaviors. Let me know if you need more info. 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-14465) Buttons and lists don't work as expected
Adrian Vlad created JENKINS-14465 Buttons and lists dont work as expected Issue Type: Bug Affects Versions: current Assignee: domi Attachments: jenkins-plugins.png, option-list.png, option-list1.png Components: conditional-buildstep Created: 17/Jul/12 3:37 PM Description: When configuring a build step and selecting conditional steps (multiple), any option in the dropdown list for the condition is not functioning. If I select Execute Shell from this list, no box to write the shell script appears. Same happens with all the other options. More, I cannot delete this build step; the delete button simply does nothing, the Advanced button does nothing. I attached some pics to understand better. Due Date: 17/Jul/12 12:00 AM Environment: Ubuntu 12.04 Jenkins 1.474 Run Condition Plugin 0.10 Token Macro Plugin 1.5.1 Conditional Buildstep 1.1 Project: Jenkins Priority: Major Reporter: Adrian Vlad 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-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Nikolay Diakov edited a comment on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses We have this same situation too: Installing c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe [jdk-1.6.0_31] $ c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe /s /v /qn /L \"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe.install.log\" REBOOT=ReallySuppress INSTALLDIR=\"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\" However after that in the build: java.io.IOException: Cannot run program "c:\java\jenkins\tools\JDK\jdk-1.6.0_31/bin/java" (in directory "c:\java\jenkins\workspace\fas-windows\fas"): CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:709) at hudson.Launcher$ProcStarter.start(Launcher.java:338) The directory has only the .installedByHudson file marker. Now, I find a partial installation in the c:\java\hudson\tools\JDK\jdk-1.6.0_31 - which is the previous configuration for the node - I had changed it from c:\java\hudson to c:\java'jenkins and restarted it. I however did not restart the Master instance, could it be keeping the old config? 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-13864) JDK auto installer installs to a different path than JAVA_HOME for a build uses
Nikolay Diakov edited a comment on JENKINS-13864 JDK auto installer installs to a different path than JAVA_HOME for a build uses We have this same situation too: Installing c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe [jdk-1.6.0_31] $ c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe /s /v /qn /L \"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\jdk.exe.install.log\" REBOOT=ReallySuppress INSTALLDIR=\"c:\java\jenkins\tools\JDK\jdk-1.6.0_31\" However after that in the build: java.io.IOException: Cannot run program "c:\java\jenkins\tools\JDK\jdk-1.6.0_31/bin/java" (in directory "c:\java\jenkins\workspace\fas-windows\fas"): CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:709) at hudson.Launcher$ProcStarter.start(Launcher.java:338) The directory has only the .installedByHudson file marker. Now, I find a partial installation in the c:\java\hudson\tools\JDK\jdk-1.6.0_31 - which is the previous configuration for the node - I had changed it from c:\java\hudson to c:\java\jenkins and restarted it. I however did not restart the Master instance, could it be keeping the old config? 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-14466) cppcheck plugin fails build even when
Chris Welch created JENKINS-14466 cppcheck plugin fails build even when Issue Type: Bug Assignee: Gregory Boissinot Components: cppcheck Created: 17/Jul/12 4:02 PM Project: Jenkins Priority: Major Reporter: Chris Welch 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-13018) The IRC bot cannot connect over SSL to a server with a self-signed cert.
charles-erid dessart commented on JENKINS-13018 The IRC bot cannot connect over SSL to a server with a self-signed cert. Worked for me http://www.erikzaadi.com/2011/09/09/connecting-jenkins-to-self-signed-certificated-servers/ 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-14466) cppcheck plugin fails build even when all severity evaluation check boxes are unchecked.
Chris Welch updated JENKINS-14466 cppcheck plugin fails build even when all severity evaluation check boxes are unchecked. Change By: Chris Welch (17/Jul/12 4:09 PM) Summary: cppcheckpluginfailsbuildevenwhen allseverityevaluationcheckboxesareunchecked. Attachment: cppcheckscreen.bmp Environment: Jenkins1.434CentOS5.7 Description: cppcheck1.9Whenalloftheseverityevaluationcheckboxesareuncheckedtofailbuildsfromcppcheck,thebuildstillfails.Thecommentwiththeseverityevaluationcheckboxesis:Determineswhichseverityoferrorsshouldbeconsideredwhenevaluatingthebuildstatusandhealth.iftheyarealluncheck,nothingshouldbeconsideredwhenevaluationthebuildstatusandhealth.Seetheattachedscreenshot,thiscausesabuildfailureforus(wehavecppcheckerrors,butcannotseethemduetoanotherbugwiththecppcheckplugin). 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-14467) Server login set by default to PircBotx
charles-erid dessart created JENKINS-14467 Server login set by default to PircBotx Issue Type: Improvement Assignee: kutzi Components: ircbot Created: 17/Jul/12 4:12 PM Description: Is it possible to be able to define the login used for the connection to the irc server? https://github.com/jenkinsci/ircbot-plugin/blob/master/src/main/java/hudson/plugins/ircbot/v2/IRCConnection.java#L62 Project: Jenkins Priority: Major Reporter: charles-erid dessart 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-14468) Not reconnect if libvirt is restarted
Eduardo Gonzalez created JENKINS-14468 Not reconnect if libvirt is restarted Issue Type: Bug Affects Versions: current Assignee: mmornati Components: libvirt-slave, libvirtslave Created: 17/Jul/12 4:16 PM Description: If the host (or service) where the libvirtd is running, is restarted, the connection from Jenkins will be lost. However, is expected to be reconnected and that is not happening. I have to manually restart Jenkins in order to regain the connection (there is no option to reconnect to libvirt host). This affects all the slaves in that host, no builds can be done in those slaves (if those slave are offline). Environment: Centos 5 i386 (jenkins) Centos 6 x86_64 / libvirtd 0.9.4 (VM host) Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: Eduardo Gonzalez 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-14468) Not reconnect if libvirt is restarted
Eduardo Gonzalez updated JENKINS-14468 Not reconnect if libvirt is restarted Change By: Eduardo Gonzalez (17/Jul/12 4:18 PM) Description: Ifthehost(orservice)wherethelibvirtdisrunning,isrestarted,theconnectionfromJenkinswillbelost.However,isexpectedtobereconnectedandthatisnothappening.IhavetomanuallyrestartJenkinsinordertoregaintheconnection(thereisnooptiontoreconnecttolibvirthost).Thisaffectsalltheslavesinthathost,nobuildscanbedoneinthoseslaves(ifthoseslaveareoffline). Log:Gettingconnectiontothevirtualdatacenterorg.libvirt.LibvirtException:cannotsenddata:Brokenpipe atorg.libvirt.ErrorHandler.processError(UnknownSource) atorg.libvirt.Connect.processError(UnknownSource) atorg.libvirt.Connect.numOfDefinedDomains(UnknownSource) atorg.libvirt.Connect.listDefinedDomains(UnknownSource) athudson.plugins.libvirt.Hypervisor.getDomains(Hypervisor.java:146) athudson.plugins.libvirt.VirtualMachineLauncher.launch(VirtualMachineLauncher.java:99) athudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) 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:679) 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-14469) anit-pattern for build exclusions
Alex Lorenz created JENKINS-14469 anit-pattern for build exclusions Issue Type: Improvement Assignee: Simon Westcott Components: bulk-builder Created: 17/Jul/12 5:01 PM Description: there should be another pattern field via which one could determine which builds NOT to run. useful for situations like: "build all jobs, except the release jobs" Project: Jenkins Priority: Major Reporter: Alex Lorenz 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-14470) S3 Plugin publishing fails spontaneously
Theral Mackey created JENKINS-14470 S3 Plugin publishing fails spontaneously Issue Type: Bug Affects Versions: current Assignee: Michael Watt Components: s3 Created: 17/Jul/12 5:03 PM Description: We use the S3 plugin in both a newer Jenkins install (v1.471, waiting for some important stuff to clear before we update it to 1.474) and a few older Hudson builds. The current Jenkins w/S3 (v0.3) works for a while, then all our builds stop uploading to S3 with an "Access Denied" error from Amazon. The builds on the older Hudson/S3 still work to the same bucket, and our credentials still work when I test with s3fs on the same machine. Error from Jenkins build console of one failure (buckets and filenames changed to x): Archiving artifacts Publish artifacts to S3 Bucket Using S3 profile: builds2 Publish artifacts to S3 Bucket bucket=xxx/store, file=xxx.latest.apk ERROR: Failed to upload files java.io.IOException: put Destination bucketName=x, objectName=xxx/store/xxx.latest.apk: Status Code: 403, AWS Request ID: 85F9CB0156BF7CF6, AWS Error Code: AccessDenied, AWS Error Message: Access Denied, S3 Extended Request ID: swP7ylP4SQNW3o9uP3alhBO/VZthqvuFxWiZ2Pn54mqhSHk2uEtSrIlhPXlJLPUM at hudson.plugins.s3.S3Profile.upload(S3Profile.java:82) at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:119) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) 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:1509) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Build step 'Publish artifacts to S3 Bucket' changed build result to UNSTABLE Project: Jenkins Priority: Major Reporter: Theral Mackey 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-14471) add support to track StarTeam changes
smadden created JENKINS-14471 add support to track StarTeam changes Issue Type: Improvement Affects Versions: current Assignee: Rob Petti Components: display-upstream-changes Created: 17/Jul/12 5:23 PM Description: Hi, first off, thanks for creating such a useful plugin! It would be awesome if you could support StarTeam changes too. We have a mixed setup in our company where some projects are in StarTeam (upstream projects) and some in Perforce (downstream projects). It would be great if the upstream projects changes could also show up in the downstream Perforce projects changelist. At the moment it only seems to work if both up- and downstream projects live in Perforce. Thanks! Sandra Environment: Jenkins 1.474, Hudson StarTeam plugin 0.6.7, Display Upstream Changes 0.1 Fix Versions: current Project: Jenkins Priority: Major Reporter: smadden 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-14428) Provide group operations for Disable build slicer
eguess74 commented on JENKINS-14428 Provide group operations for Disable build slicer The string variant worked very well, thank you! AS for the configuration by views - We do have views and we use them to separate our hundreds of projects to groups, but even if I would want to use it - it will still require me to click through dozens of check boxes if i want to disable the whole group. Therefore "check all"/"uncheck all" still makes a lot of sense to me. What if i need to disable three/four groups?? Our job names are actually including group name (in a format of group+jobname), therefore if I would like to work with one or more groups I will now go to the string slicer, cause it has jobs listed in alphabetic order so i can manage them much easier, but never to "by view" - too many clicks. 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-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? Okay, I installed the most recent LTS (1.447.2). Now, I am not getting any errors in the log, but projects cannot be configured. If I try to configure a project, it continues to display the LOADING text with grey overlay; scrolling down, the post-build actions are loaded up until the Warnings plugin, it seems. But, as I said, nothing shows up in the log. This is with the updated 4.11 plugin. It might be worth mentioning that the previously installed version, before upgrading to 4.10, was 3.21, and it worked perfectly then. 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-6963) CGit browser support.
eguess74 commented on JENKINS-6963 CGit browser support. works fine for us! Thanks a lot! I'm taking a liberty to close the 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-6963) CGit browser support.
eguess74 closed JENKINS-6963 as Fixed CGit browser support. Done! Change By: eguess74 (17/Jul/12 6:01 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
[JIRA] (JENKINS-14472) Columns cannot be deleted from configure view page
Wesley Hartford created JENKINS-14472 Columns cannot be deleted from configure view page Issue Type: Bug Affects Versions: current Assignee: Jacob Robertson Components: view-job-filters Created: 17/Jul/12 6:11 PM Description: When creating or editing a view (under by views or global views), the Delete button under columns has no effect. I've tried with a new, unsaved view, editing a saved view, deleting default columns, deleting added columns before and after saving. In every case, the delete button appears to do nothing. The bug is being observed in version 1.474. I have another Jenkins instance running LTS version 1.447.1 which does not exhibit this bug. Project: Jenkins Priority: Major Reporter: Wesley Hartford 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-14472) Columns cannot be deleted from configure view page
Jacob Robertson updated JENKINS-14472 Columns cannot be deleted from configure view page As much as I'd like to take the credit for this bug, it is in no way related to the view-job-filters plugin. Change By: Jacob Robertson (17/Jul/12 7:02 PM) Assignee: JacobRobertson Component/s: core Component/s: view-job-filters 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-11362) Strange delay during a maven job build
jglick assigned JENKINS-11362 to jglick Strange delay during a maven job build Change By: jglick (17/Jul/12 8:12 PM) Assignee: kutzi jglick 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-11305) cppcheck has problems handling file paths with a space in them
Gregory Boissinot closed JENKINS-11305 as Not A Defect cppcheck has problems handling file paths with a space in them Happy to hear that. If it works, I'm closing the issue. Thanks Change By: Gregory Boissinot (17/Jul/12 8:13 PM) Status: Open Closed Resolution: NotADefect 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-11362) Strange delay during a maven job build
jglick resolved JENKINS-11362 as Wont Fix Strange delay during a maven job build Found http://jira.codehaus.org/browse/MNG-5312 as the root cause. The hudson.maven.PomInfo constructor calls MavenProject.getParent and this can be exceedingly slow. Options for Jenkins include Wait for a Maven release (3.0.5?) with the performance problem fixed. Bundle a patched version of maven-core with the plugin. Stop calling getParent from PomInfo, at least at the user's option. But this might cause Jenkins to be missing dependency information needed for build triggers: an update to a parent POM (other than the relativePath default of ../pom.xml) would not be "noticed" by modules using it. Provisionally going with option #1, hence closing this issue since we would anyway bundle any new Maven release with the plugin when it becomes available. But I could work on #2 or #3 instead if anyone thinks it would be a good idea. Unclear if many users are affected by this issue; the impact is on projects using lots of scopeimport/scope. Change By: jglick (17/Jul/12 8:35 PM) Status: Open Resolved Resolution: WontFix 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-12504) cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure
Chris Welch updated JENKINS-12504 cppcheck-plugin doesnt display the latest source when cppcheck-plugin is the cause of a build failure My mistake, we had another error that was causing the failure. Issue is 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-14466) cppcheck plugin fails build even when all severity evaluation check boxes are unchecked.
Chris Welch resolved JENKINS-14466 as Cannot Reproduce cppcheck plugin fails build even when all severity evaluation check boxes are unchecked. Not a problem. My mistake, our build had a failure in it. Change By: Chris Welch (17/Jul/12 8:38 PM) 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
[JIRA] (JENKINS-12504) cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure
Chris Welch resolved JENKINS-12504 as Fixed cppcheck-plugin doesnt display the latest source when cppcheck-plugin is the cause of a build failure Change By: Chris Welch (17/Jul/12 8:37 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
[JIRA] (JENKINS-14462) cppcheck plugin doesn't show results until a build is successful
Chris Welch resolved JENKINS-14462 as Cannot Reproduce cppcheck plugin doesnt show results until a build is successful Not a defect, our problem. Our build had a failure in it. Change By: Chris Welch (17/Jul/12 8:39 PM) 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
[JIRA] (JENKINS-14473) Jenkins server memory leak
Anoop Karollil created JENKINS-14473 Jenkins server memory leak Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: JavaMelody__build_7_17_12.pdf, usedMemory-month.png, usedMemory.png Components: core Created: 17/Jul/12 8:52 PM Description: I am not sure I have filed this under the right component. We are seeing steady gradual increases in memory usage for our Jenkins (see attached graphs). It does not result in the OutOfMemoryError but usually results in Jenkins utilizing 100% of CPU (one core in our case). Attached is a memory histogram report and heap dump generated using the Monitoring Plugin. This happens consistently and our work around for now is to restart Jenkins each time it gets too bloated. If this doesn't get fixed, we will have to stop using Winstone and use Jetty - because there seems to be a connection between the servlet wrapper (winstone/jetty) and the leak - pretty sure we did not see this when using Jetty. Environment: Ubuntu 7.10 running on 32bit dual core. Jenkins with Winstone. Project: Jenkins Labels: jenkins memory-leak memory winstone Priority: Major Reporter: Anoop Karollil 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-9336) Culprits Email List - Names Can be Dropped
Jim Searle commented on JENKINS-9336 Culprits Email List - Names Can be Dropped Yes, this does still seem to be an issue. We are on Email-ext 2.21 with Jenkins 1.472. My example was slightly different because the final job is using the blame-subversion plugin, but I will test with just using straight svn. 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-14337) Multi-configuration job disappearing from list whether the file config.xml is edited.
Sarah Woodall commented on JENKINS-14337 Multi-configuration job disappearing from list whether the file config.xml is edited. Please see a new issue that I have just created: https://issues.jenkins-ci.org/browse/JENKINS-14474 I think you are seeing the same bug as I am! Have you tried just reloading from disk without editing config.xml at all? 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-14443) Build is broken out of the box
jglick updated JENKINS-14443 Build is broken out of the box John Hsing on jenkins-dev also running into trouble; bumping priority. (Assignee is on vacation, so perhaps another maintainer wants to apply this fix?) Change By: jglick (17/Jul/12 9:37 PM) 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-14471) add support to track StarTeam changes
Rob Petti commented on JENKINS-14471 add support to track StarTeam changes That's odd, it should be completely agnostic. In my tests, it displayed information from mixed SCM projects without any issues, though admittedly I didn't test every single SCM combination. Do you see any exceptions pop up in the Jenkins log when you view the page? 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-14471) StarTeam changes are not displayed
Rob Petti updated JENKINS-14471 StarTeam changes are not displayed Changing issue type to bug. Change By: Rob Petti (17/Jul/12 10:33 PM) Summary: addsupporttotrack StarTeamchanges arenotdisplayed Issue Type: Improvement Bug 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-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Matthew Cooper commented on JENKINS-14474 Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk I have the same symptoms and this is in the log: 18/07/2012 8:44:42 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job z_multi java.lang.NullPointerException at hudson.matrix.MatrixProject.updateTransientActions(MatrixProject.java:431) at hudson.model.AbstractProject.onLoad(AbstractProject.java:292) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:466) at hudson.model.Items.load(Items.java:115) at jenkins.model.Jenkins$17.run(Jenkins.java:2492) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:878) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) 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:679) 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-14475) Conditional build steps should be available as post-build actions
owenmehegan created JENKINS-14475 Conditional build steps should be available as post-build actions Issue Type: New Feature Affects Versions: current Assignee: domi Components: conditional-buildstep Created: 18/Jul/12 1:14 AM Description: I have matrix builds which run on several nodes, and if a "deploy" checkbox param was selected when the build ran we call a deploy job to push the code out for testing. Unfortunately, using a conditional build step for this causes the deploy to happen for every build node. It should only be run once in our case, after all builds succeed. If I could use a conditional build step as a post-build action, this would work perfectly! Project: Jenkins Priority: Major Reporter: owenmehegan 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-9671) NODE_NAME not defined for master node
owenmehegan reopened JENKINS-9671 NODE_NAME not defined for master node This seems to be broken in 1.465. $NODE_NAME is unset, but $NODE_LABELS includes "master" on the master node. Change By: owenmehegan (18/Jul/12 1:56 AM) Resolution: Fixed Status: Closed Reopened 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-14476) Option to set gravatar to only check for new gravatar every x minutes to cut down on requests from jenkins server to gravatar.com
Mike Caspar created JENKINS-14476 Option to set gravatar to only check for new gravatar every x minutes to cut down on requests from jenkins server to gravatar.com Issue Type: Improvement Assignee: redsolo Components: gravatar Created: 18/Jul/12 2:55 AM Description: I love the Gravatar plug-in. I'm wondering if there's any possibility of having it only check for a new gravatar every "x" minutes to keep bandwidth utilization down. Thanks Project: Jenkins Labels: plugin Priority: Minor Reporter: Mike Caspar 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-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Matthew Cooper commented on JENKINS-14474 Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk look alike it has been fixed on trunk so should be in the next drop I guess... commit a811f406e785a8c8e6cb4b9246829dce9c7b97ae Author: lvotypko lvoty...@redhat.com Date: Mon Jul 2 14:11:20 2012 +0200 Fix NPE during loading matrix job 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-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Matthew Cooper edited a comment on JENKINS-14474 Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk looks like it has been fixed on trunk so should be in the next drop I guess... commit a811f406e785a8c8e6cb4b9246829dce9c7b97ae Author: lvotypko lvoty...@redhat.com Date: Mon Jul 2 14:11:20 2012 +0200 Fix NPE during loading matrix job 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-12157) Refspec and branch should have whitespace stripped
David Pursehouse commented on JENKINS-12157 Refspec and branch should have whitespace stripped Can you give more specific steps to reproduce this? Where are you pasting the refspec/branch? 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-14345) Grails wrapper doesn't respect Project Base Directory
SCM/JIRA link daemon commented on JENKINS-14345 Grails wrapper doesnt respect Project Base Directory Code changed in jenkins User: kiy0taka Path: src/main/java/com/g2one/hudson/grails/GrailsBuilder.java http://jenkins-ci.org/commit/grails-plugin/a54cbb2a133e08b88711b53715a0f33bea5aed51 Log: fixed bug. refs JENKINS-14345 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
