[JIRA] [test-stability] (JENKINS-21156) No history for tests stability plugin
kutzi commented on JENKINS-21156 No history for tests stability plugin What do you mean with 'only aware of the current tests result'? The plugin is only recording the test history after it has been enabled for a given project. Is that what you're referring to? If so that's not a bug, but working as designed. 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] [ownership] (JENKINS-21158) Logs fills with warnings about Fails to load OwnerRoleMacroNoSid
Per Arnold Blaasmo created JENKINS-21158 Logs fills with warnings about Fails to load OwnerRoleMacroNoSid Issue Type: Bug Affects Versions: current Assignee: Oleg Nenashev Components: ownership Created: 27/Dec/13 10:27 AM Description: The log fills up with the following warnings from the ownership plugin: Dec 27, 2013 11:18:35 AM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout com.synopsys.arc.jenkins.plugins.ownership.security.rolestrategy.CoOwnerRoleMacroNoSid java.lang.InstantiationException: /storage/hudson-home/plugins/ownership/WEB-INF/lib/classes.jar might need to be rebuilt: java.lang.ClassNotFoundException: com.synopsys.arc.jenkins.plugins.ownership.security.rolestrategy.CoOwnerRoleMacroNoSid at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:666) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:310) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:309) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.getComponents(ExtensionList.java:149) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at org.jenkinsci.plugins.xunit.AliasInitializer.addAliases(AliasInitializer.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:897) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.ClassNotFoundException: com.synopsys.arc.jenkins.plugins.ownership.security.rolestrategy.CoOwnerRoleMacroNoSid at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:984) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 26 more Project: Jenkins Priority: Major Reporter: Per Arnold Blaasmo 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
[JIRA] [ownership] (JENKINS-21158) Logs fills with warnings about Fails to load OwnerRoleMacroNoSid
Oleg Nenashev commented on JENKINS-21158 Logs fills with warnings about Fails to load OwnerRoleMacroNoSid Hello, What version of Jenkins do you use? What version of Ownership plugin do you use? Do you use role-strategy plugin? If yes, what version do you use? 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] [test-stability] (JENKINS-21156) No history for tests stability plugin
Pedro Algarvio commented on JENKINS-21156 No history for tests stability plugin The plugin has been enabled for months now(the ain't that much history because we recently started cleaning up old builds). A recurring failing tests will always show as failing for one build. http://jenkins.saltstack.com/job/salt-rs-arch/1159/testReport/integration.states.pkg/PkgTest/test_pkg_004_installed_multipkg_with_version/ http://jenkins.saltstack.com/job/salt-rs-arch/1160/testReport/integration.states.pkg/PkgTest/test_pkg_004_installed_multipkg_with_version/ http://jenkins.saltstack.com/job/salt-rs-arch/1161/testReport/integration.states.pkg/PkgTest/test_pkg_004_installed_multipkg_with_version/ See? Always "Failed 1 times in the last 1 runs. Stability: 0 %" This is a python project which runs it's unittests and reports it's results through a junit compatible xml file. These xml files are cleaned up from the file system when starting a new build. Is there any more info I can provide? 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] [test-stability] (JENKINS-21156) No history for tests stability plugin
Pedro Algarvio commented on JENKINS-21156 No history for tests stability plugin Is the history stored on any file in the build directory? Certainly not on the builder machine right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
Dominik Bartholdi created JENKINS-21159 buildTimeTrend only shows last day of builds Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Dec/13 11:56 AM Description: The SIMILE timeline control only shows the last day with any builds, every other day dos not show any builds. This can be seen at multiple locations: on Job level: https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_main_trunk/buildTimeTrend on view level: https://ci.jenkins-ci.org/view/Infrastructure/builds on slave level: https://ci.jenkins-ci.org/computer/remote-slave-6/builds Environment: Jenkins 1.538 Project: Jenkins Priority: Major Reporter: Dominik Bartholdi 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] [config-file-provider] (JENKINS-20431) Can't select Settings file for maven build step in free-style project
Dominik Bartholdi resolved JENKINS-20431 as Fixed Cant select Settings file for maven build step in free-style project fixed with core 1.526 Change By: Dominik Bartholdi (27/Dec/13 2:17 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19635) Copy existing job does not clone the repository
Dominik Bartholdi updated JENKINS-19635 Copy existing job does not clone the repository Change By: Dominik Bartholdi (27/Dec/13 2:39 PM) Component/s: createjobadvanced This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19635) Copy existing job does not clone the repository
Dominik Bartholdi assigned JENKINS-19635 to Unassigned Copy existing job does not clone the repository Change By: Dominik Bartholdi (27/Dec/13 2:39 PM) Assignee: bertrandgressier 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] [jobgenerator] (JENKINS-21072) White screen after submitting job generation
Alex Artyukhovskii
commented on JENKINS-21072
White screen after submitting job generation
Hello, Sylvain,
Looks like I found how this issue can be resolved.
The symptoms are similar to https://issues.jenkins-ci.org/browse/JENKINS-18425, thus the changes should be the same.
In src\main\resources\org\jenkinsci\plugins\jobgenerator\parameters\GeneratorParametersDefinitionProperty\index.jelly the last "f:block /" entry should be extended with two hidden input fields:
f:block
!-- Changes, similar to https://issues.jenkins-ci.org/browse/JENKINS-18425 --
input type="hidden" name="statusCode" value="303" /
input type="hidden" name="redirectTo" value="." /
f:submit value="${%Generate}" /
/f:block
After updating this file and rebuilding the plugin JPI I've got your plugin working as expected. Sorry, now I have no time to produce a valid Git pull request.
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] [cli] (JENKINS-21160) Jenkins CLI cannot handle arguments with equals signs (=)
Bob Bell
created JENKINS-21160
Jenkins CLI cannot handle arguments with equals signs (=)
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
cli
Created:
27/Dec/13 4:11 PM
Description:
The Jenkins CLI can pass in parameters to a parameterized build. It uses the "-p" option for this. The arguments are parsed using args4j. The version of args4j that has been incorporated has a bug in the MapOptionHandler code where it will not accept a parameter value that has an equals sign ("=") in it; instead it will take everything up to the equals sign. The problem appears to be fixed in newer args4j code.
Project:
Jenkins
Priority:
Major
Reporter:
Bob Bell
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] [cli] (JENKINS-21161) Jenkins CLI hangs all executors when no file parameter given
Bob Bell created JENKINS-21161 Jenkins CLI hangs all executors when no file parameter given Issue Type: Bug Assignee: Unassigned Components: cli Created: 27/Dec/13 4:18 PM Description: If the Jenkins CLI is invoked in a particular way, no Jenkins jobs will be able to run. The criteria to trigger this issue are: (1) A job must have a file parameter AND another parameter for the build (I use a string parameter). The file parameter is critical to trigger the bug, and it doesn't occur unless there's also another parameter. (2) You must start the build via the CLI the web interface and REST interfaces do not have an issue. (The SSH interface also has an issue, but that appears to just be a wrapper for the CLI, so that would be expected) (3) You must specific a value for the string parameter, but NOT the file parameter. If you supply a parameter, all will be OK. If don't supply any parameters, it will also be OK. Given these conditions, instead of running, the job will enter a "(pending)" state. Any other job, regardless of where it is to be executed, will be stuck at "(pending - waiting for executor)". Those states will persist indefinitely. If you then cancel the original "(pending)" job, the problem will be resolved, and the other jobs will get a chance to run. I view this as a serious bug because a relatively simple task can prevent all Jenkins jobs from running. Project: Jenkins Priority: Critical Reporter: Bob Bell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21163) Git Plugin causes Jenkins to stop working
C. Alex Reober created JENKINS-21163 Git Plugin causes Jenkins to stop working Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: core, git, git-client, git-server Created: 27/Dec/13 6:53 PM Description: Adding the Git plugin cause the Jenkins server to fail on next restart. Jenkins shows the following error: hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:234) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:908) at jenkins.model.Jenkins.init(Jenkins.java:807) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:109) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:897) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) ... 8 more Caused by: java.lang.NullPointerException at hudson.plugins.git.GitTool.onLoaded(GitTool.java:105) ... 13 more Environment: Ubuntu 12.04 in AWS Project: Jenkins Priority: Critical Reporter: C. Alex Reober This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-21162) CopyArtifact plugin 1.28 no longer creates COPYARTIFACT_BUILD_NUMBER_* variables in the same way
Michael Chmielewski created JENKINS-21162 CopyArtifact plugin 1.28 no longer creates COPYARTIFACT_BUILD_NUMBER_* variables in the same way Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 27/Dec/13 6:53 PM Description: I upgraded from 1.27 to 1.28 and all my builds that used the COPYARTIFACT_BUILD_NUMBER_ enfironment variable failed. Looking at the build logs, the variable was empty. I am guessing the issue is due to the folder work done in 1.28 (the builds I checked were in a folder). Reverting to 1.27 restored the variable. Environment: Centos 6.4, jenkins 1.544, Folders plugin 3.15 Fix Versions: current Project: Jenkins Priority: Critical Reporter: Michael Chmielewski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-21162) CopyArtifact plugin 1.28 no longer creates COPYARTIFACT_BUILD_NUMBER_* variables in the same way
Michael Chmielewski commented on JENKINS-21162 CopyArtifact plugin 1.28 no longer creates COPYARTIFACT_BUILD_NUMBER_* variables in the same way Some more details: When in 1.28, the build job that had the artifacts (Job A) was at the top level of jenkins (not in any folder), while the downstream job (Job B) was 2 folders deep. This issue was fixed by reverting to 1.27 of the CopyArtifact plugin. However, even in 1.27, I can get the same issue to occur if I move Job A into a subfolder. 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] [subversion] (JENKINS-21164) Audit Failures in Windows Event Log
Michael Haderman created JENKINS-21164 Audit Failures in Windows Event Log Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: EventLogError.txt Components: subversion Created: 27/Dec/13 7:45 PM Description: We have our SVN repository hosted on a Windows Server 2008 box (recently migrated from 2003) and every minute we get 20+ Audit Failure logs from the account that our Jenkins CI server uses to connect to the repository. However, the Jenkins CI server is able to get check for updates just fine and jobs are always triggered when there are new commits. The real issue we have is that when there are real login failures its pretty hard to debug the problem, when there are all the false failures from Jenkins. I've attached the Widnows Event Log details. Our repo and the jenkins ci installation are on different servers. Environment: Windows Server 2003/2008 Project: Jenkins Priority: Minor Reporter: Michael Haderman 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] [m2release] (JENKINS-20753) Explain Append Hudson Build Number
Anders Hammar assigned JENKINS-20753 to Anders Hammar Explain Append Hudson Build Number Change By: Anders Hammar (27/Dec/13 8:05 PM) Assignee: teilo AndersHammar 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] [xunit] (JENKINS-20024) com.thoughtworks.xstream.converters.ConversionException: QTestLibType on Jenkins 1.524 and later
Gregory Boissinot started work on JENKINS-20024 com.thoughtworks.xstream.converters.ConversionException: QTestLibType on Jenkins 1.524 and later Change By: Gregory Boissinot (27/Dec/13 8:20 PM) Status: Open InProgress 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] [xunit] (JENKINS-20024) com.thoughtworks.xstream.converters.ConversionException: QTestLibType on Jenkins 1.524 and later
Gregory Boissinot commented on JENKINS-20024 com.thoughtworks.xstream.converters.ConversionException: QTestLibType on Jenkins 1.524 and later It should be OK with the version 1.68. Please could you check? 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] [xunit] (JENKINS-19797) xUnit says that my junit report files are invalid, but they can be read with the performance plugin?
Gregory Boissinot commented on JENKINS-19797 xUnit says that my junit report files are invalid, but they can be read with the performance plugin? Sorry for my late reply. xUnit plugin uses XSD JUnit files for validating JUnit outputs, before to be recorded by Jenkins. It is a security mechanism. Performance plugin seems to not use any validation on output JUnit files. It works for your use cases but maybe you could have unexpected results with other inputs. Please upload your wrong JUnit file, I'll check. 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] [xunit] (JENKINS-19797) xUnit says that my junit report files are invalid, but they can be read with the performance plugin?
Gregory Boissinot started work on JENKINS-19797 xUnit says that my junit report files are invalid, but they can be read with the performance plugin? Change By: Gregory Boissinot (27/Dec/13 8:27 PM) Status: Open InProgress 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] [xunit] (JENKINS-19732) Support cmake / ctest test reports in xunit
Gregory Boissinot resolved JENKINS-19732 as Fixed Support cmake / ctest test reports in xunit From version 1.58, CTest is supposed to be supported. Please check it with your inputs. Thanks Change By: Gregory Boissinot (27/Dec/13 8:30 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 -- 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] [subversion] (JENKINS-21164) Audit Failures in Windows Event Log
Michael Haderman updated JENKINS-21164 Audit Failures in Windows Event Log Change By: Michael Haderman (27/Dec/13 8:34 PM) Description: WehaveourSVNrepositoryhostedonaWindowsServer2008box(recentlymigratedfrom2003)andeveryminuteweget20+AuditFailurelogsfromtheaccountthatourJenkinsCIserverusestoconnecttotherepository. IfweputJenkinsintoShutdownModewestopseeingtheAuditFailures. However,the Jenkins CIserver isabletogetcheckfor svn updatesjustfineandjobsarealwaystriggeredwhentherearenewcommits.Therealissuewehaveisthatwhentherearerealloginfailuresitsprettyhardtodebugtheproblem,whenthereareallthefalsefailuresfromJenkins.Iveattachedthe Widnows Windows EventLogdetails.Ourrepoandthejenkins ci installationareondifferentservers. 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] [xunit] (JENKINS-19637) Select filename for generated jUnit File
Gregory Boissinot commented on JENKINS-19637 Select filename for generated jUnit File At the moment, there is no way to give a filename to the generated JUnit files. It is only managed internally by the xUnit plugin. What is your real use case? 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] [xunit] (JENKINS-18755) xUnit Test Result Trend not showing
Gregory Boissinot resolved JENKINS-18755 as Wont Fix xUnit Test Result Trend not showing Not an xUnit issue Change By: Gregory Boissinot (27/Dec/13 8:43 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 -- 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] [xunit] (JENKINS-19185) xUnit fails to correctly parse Boost.Test log
Gregory Boissinot started work on JENKINS-19185 xUnit fails to correctly parse Boost.Test log Change By: Gregory Boissinot (27/Dec/13 8:58 PM) Status: Open InProgress 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] [m2release] (JENKINS-21165) Icon for Perform Maven Release (in side bar) is not transparent
Anders Hammar
created JENKINS-21165
Icon for Perform Maven Release (in side bar) is not transparent
Issue Type:
Bug
Assignee:
teilo
Components:
m2release
Created:
27/Dec/13 9:18 PM
Description:
The icon ("installer.gif") is not transparent.
Project:
Jenkins
Priority:
Trivial
Reporter:
Anders Hammar
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] [m2release] (JENKINS-21165) Icon for Perform Maven Release (in side bar) is not transparent
Anders Hammar commented on JENKINS-21165 Icon for Perform Maven Release (in side bar) is not transparent This image is part of Jenkins core. Not sure what component to assign 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] [m2release] (JENKINS-20753) Remove unused Append Hudson Build Number option
Anders Hammar commented on JENKINS-20753 Remove unused Append Hudson Build Number option Pull request sent. 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] [m2release] (JENKINS-20753) Remove unused Append Hudson Build Number option
Anders Hammar updated JENKINS-20753 Remove unused Append Hudson Build Number option Updated summary to better reflect what's to be done. Change By: Anders Hammar (27/Dec/13 9:21 PM) Summary: Explain Removeunused AppendHudsonBuildNumber option 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] [xunit] (JENKINS-18575) xUnit failed to parse a JUnit .xml report without any debug in log
SCM/JIRA link daemon commented on JENKINS-18575 xUnit failed to parse a JUnit .xml report without any debug in log Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/types/JUnitInputMetric.java src/main/java/org/jenkinsci/plugins/xunit/types/model/JUnit8.java src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-8.xsd http://jenkins-ci.org/commit/xunit-plugin/15da098793691c4d5a6b1a934a83587e4594643f Log: Fix JENKINS-18095 and JENKINS-18575 Compare: https://github.com/jenkinsci/xunit-plugin/compare/88672e87da9f...15da09879369 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] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59
SCM/JIRA link daemon commented on JENKINS-18095 nose generated xunit reports are rejected by xunit 1.59 Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/types/JUnitInputMetric.java src/main/java/org/jenkinsci/plugins/xunit/types/model/JUnit8.java src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-8.xsd http://jenkins-ci.org/commit/xunit-plugin/15da098793691c4d5a6b1a934a83587e4594643f Log: Fix JENKINS-18095 and JENKINS-18575 Compare: https://github.com/jenkinsci/xunit-plugin/compare/88672e87da9f...15da09879369 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] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59
Gregory Boissinot resolved JENKINS-18095 as Fixed nose generated xunit reports are rejected by xunit 1.59 Change By: Gregory Boissinot (27/Dec/13 10:05 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 -- 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] [xunit] (JENKINS-18575) xUnit failed to parse a JUnit .xml report without any debug in log
Gregory Boissinot resolved JENKINS-18575 as Fixed xUnit failed to parse a JUnit .xml report without any debug in log Change By: Gregory Boissinot (27/Dec/13 10:05 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 -- 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] [xunit] (JENKINS-18341) xUnit cannot parse JUnit output from a Gradle build because of empty properties element
Gregory Boissinot resolved JENKINS-18341 as Fixed xUnit cannot parse JUnit output from a Gradle build because of empty properties element Change By: Gregory Boissinot (27/Dec/13 10:09 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 -- 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] [xunit] (JENKINS-18339) xunit plugin fails to verify Boost generated xml result file
Gregory Boissinot resolved JENKINS-18339 as Fixed xunit plugin fails to verify Boost generated xml result file Change By: Gregory Boissinot (27/Dec/13 10:15 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 -- 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] [xunit] (JENKINS-18339) xunit plugin fails to verify Boost generated xml result file
Gregory Boissinot commented on JENKINS-18339 xunit plugin fails to verify Boost generated xml result file It is OK for now. Please reopen if it is not the case. 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] [xunit] (JENKINS-18277) Testcase isn't marked as failed
Gregory Boissinot commented on JENKINS-18277 Testcase isnt marked as failed By default, the build is always OK. If you want to have a failed build or an unstable build, please configure the threshold section. 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] [xunit] (JENKINS-18277) Testcase isn't marked as failed
Gregory Boissinot resolved JENKINS-18277 as Fixed Testcase isnt marked as failed Change By: Gregory Boissinot (27/Dec/13 10:18 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 -- 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] [xunit] (JENKINS-18277) Testcase isn't marked as failed
Ivan Kurnosov commented on JENKINS-18277 Testcase isnt marked as failed @Gregory Boissinot, threshold is configured to fail if at least one test is failing. But the thing is - even though there are failed tests - plugin doesn't mark it so. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21163) Git Plugin causes Jenkins to stop working
C. Alex Reober commented on JENKINS-21163 Git Plugin causes Jenkins to stop working More Info: System that does NOT work: jenkins-1a java -version java version "1.6.0_27" OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.12.04.4) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) git --version git version 1.7.9.5 Git Plugin 2.0 This plugin allows use of Git as a build SCM. a recent Git runtime is required (1.7 recommended). Base feature may work on earlier versions, but can't guarantee. System that does work: jenkins-1b java -version java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.14) (amazon-65.1.11.14.57.amzn1-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) git --version git version 1.8.3.1 Jenkins GIT plugin 2.0 This plugin integrates GIT with Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21166) Environment variables are NOT passed further build steps when using Block until the triggered projects finish their builds
Dilip M created JENKINS-21166 Environment variables are NOT passed further build steps when using Block until the triggered projects finish their builds Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 27/Dec/13 10:52 PM Description: In section Usage as a Build step in https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin its mentioned that, When using the Trigger/Call builds on another project item. If the trigger is configured with the Block until the triggered projects finish their builds enabled, the following Environment variables are made available for further build steps Env variables for future build steps LAST_TRIGGERED_JOB_NAME="Last project started" TRIGGERED_BUILD_NUMBER_project name="Last build number triggered" version 2.17 onwards TRIGGERED_JOB_NAMES="Comma separated list of all triggered projects" TRIGGERED_BUILD_NUMBERS_project name="Comma separated list of build numbers triggered" TRIGGERED_BUILD_RESULT_project name="Last triggered build result of project" TRIGGERED_BUILD_RESULT_project nameRUNbuild number="Result of triggered build for build number" TRIGGERED_BUILD_RUN_COUNT_project name="Number of builds triggered for the project" I tried configuring one upstream and downstream job. But I don’t see these ENV variables being passed to downstream jobs? PS: I am checking for these ENV variables in Build step of downstream job like 'env|grep TRIGGERED' Environment: Parameterized Trigger Plugin: 2.20 Jenkins: 1.509.4 Project: Jenkins Labels: plugin parameterized-trigger Priority: Major Reporter: Dilip M 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] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
SCM/JIRA link daemon commented on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing Code changed in jenkins User: Gregory Boissinot Path: src/main/resources/com/thalesgroup/dtkit/metrics/hudson/api/descriptor/TestTypeDescriptor/config.jelly http://jenkins-ci.org/commit/xunit-plugin/2bb32262c45b23dd37dc07b0b27b1e3a027a077e Log: Fix JENKINS-18443 Compare: https://github.com/jenkinsci/xunit-plugin/compare/7ce17fa7f1ad...2bb32262c45b 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] [xunit] (JENKINS-18263) py.test generated test reports are no longer being parsed as valid
SCM/JIRA link daemon commented on JENKINS-18263 py.test generated test reports are no longer being parsed as valid Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/types/JUnitInputMetric.java src/main/java/org/jenkinsci/plugins/xunit/types/model/JUnit9.java src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-9.xsd http://jenkins-ci.org/commit/xunit-plugin/25cb3575c602bd342667dc3cdd250018d286d102 Log: Fix JENKINS-18263 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] [ownership] (JENKINS-21158) Logs fills with warnings about Fails to load OwnerRoleMacroNoSid
Oleg Nenashev commented on JENKINS-21158 Logs fills with warnings about Fails to load OwnerRoleMacroNoSid Have you seen the issue before the update to 1.544? I test the plugin on 1.509.3, 1.509.4 and 1.532.1, so there can be issues in "Latest and Sometimes Stable" versions. The issue is quite similar to JENKINS-17425, but it requires some investigation. 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] [postbuildscript] (JENKINS-21167) NullPointerException on User.get when executing shell sudo service tomcat stop in post step
Vard Lott created JENKINS-21167 NullPointerException on User.get when executing shell sudo service tomcat stop in post step Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Attachments: jenkins_env.txt Components: postbuildscript Created: 28/Dec/13 1:35 AM Description: While executing shell post-step, I am attempting to do a "sudo service tomcat stop", the jenkins server crashes completely and the build fails with exception below: workspace $ /bin/sh -xe /tmp/hudson1433417204994586409.sh + sudo service tomcat stop Stopping Tomcat JVM: Build was aborted FATAL: null java.lang.NullPointerException at hudson.model.User.get(User.java:322) at hudson.model.User.get(User.java:300) at hudson.model.User.get(User.java:365) at jenkins.model.CauseOfInterruption$UserInterruption.getUser(CauseOfInterruption.java:82) at jenkins.model.CauseOfInterruption$UserInterruption.print(CauseOfInterruption.java:91) at hudson.model.Executor.recordCauseOfInterruption(Executor.java:189) at hudson.model.Run.execute(Run.java:1695) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) On my ci box tomcat is running as a service as the tomcat user. Running "sudo service tomcat start/stop" works fine from the command prompt. I need to issue the same commands from within jenkins build. This is a new install of v1.544, I'm running on 64-bit Amazon Linux (Centos/RedHat) with plenty of memory and storage. Jenkins is configured as a service and started stopped in the same way "sudo service jenkins start". There are no other stack traces or errors that I can identify in the jenkins log in /etc/sysconfig or in /var/log/messages. Environment: See attached Project: Jenkins Priority: Blocker Reporter: Vard Lott 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] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite commented on JENKINS-19994 Unable to delete workspace The leaked files plugin (run on Debian Linux) showed at least one leaked file handle from the RevWalk allocated in the ChangelogCommand of the JGit implementation. I've created a series of changes which were able to fix the condition detected by the leaked files plugin, but still did not allow me to delete the workspace on my Windows machine. I assume the fixes to the issues detected by the leaked files plugin are a necessary part of the final fix, but they are not sufficient to fix the problem on Windows. Unfortunately, I don't know how to run the leaked files plugin on Windows, it fails to execute there. If you'd like to see my current prototype (not yet ready for a pull request), refer to https://github.com/MarkEWaite/git-client-plugin/tree/JENKINS-19994-cannot-delete-jgit-workspace 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] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite started work on JENKINS-19994 Unable to delete workspace Change By: Mark Waite (28/Dec/13 4:10 AM) Status: Open InProgress 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] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite assigned JENKINS-19994 to Mark Waite Unable to delete workspace Change By: Mark Waite (28/Dec/13 4:10 AM) Assignee: MarkWaite 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] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Sebastian Schuberth created JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 28/Dec/13 7:46 AM Description: There seems to be a problem related to the core.symlinks config option. Usually, if core.symlinks is not set (the default), Git will probe the target file system for symlinks support when cloning (see 1). As Windows does not support symlinks in the POSIX sense, Git for Windows internally uses core.symlinks=false if that option is otherwise unset. However, relying on this results in this error for me (see 2): Cloning the remote Git repository Cloning repository git://github.com/sschuberth/git.git Fetching upstream changes from git://github.com/sschuberth/git.git Checking out Revision 21d457224673682f2879170c504750db98638d2e (origin/master) FATAL: Could not checkout null with start point 21d457224673682f2879170c504750db98638d2e hudson.plugins.git.GitException: Could not checkout null with start point 21d457224673682f2879170c504750db98638d2e at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:1222) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:870) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117) at hudson.model.AbstractProject.checkout(AbstractProject.java:1376) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:655) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) 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) Caused by: hudson.plugins.git.GitException: Command "git checkout -f 21d457224673682f2879170c504750db98638d2e" returned status code 1: stdout: stderr: error: unable to create symlink RelNotes (Function not implemented) Note: checking out '21d457224673682f2879170c504750db98638d2e'. The error disappears when I explicitly do "git config --system core.symlinks false" on the build server (see 3). 1 http://stackoverflow.com/a/11664406/1127485 2 http://mingwgitdevenv.cloudapp.net/job/mingwGitDevEnv-test-git/32/console 3 http://mingwgitdevenv.cloudapp.net/job/mingwGitDevEnv-test-git/33/consoleFull Environment: Jenkins 1.509.4 running on Windows Server 2008 R2 64-bit, Git Client Plugin 1.6.0, Git Plugin 2.0 Project: Jenkins Priority: Major Reporter: Sebastian Schuberth 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.
