[JIRA] (JENKINS-17310) URL in the project description without https:// don't work
Andrey Sorokovikov started work on JENKINS-17310 URL in the project description without https:// don't work Change By: Andrey Sorokovikov (22/Mar/13 7:29 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17248) java.lang.NullPointerException by start
Mikko Peltonen commented on JENKINS-17248 java.lang.NullPointerException by start We experienced this too, and I can confirm that removing "global-build-stats" plugin helped to get Jenkins back up. Not a real solution, though. We just updated to 1.506 from a pretty old version (1.47x something), and suddenly after one restart, this error came up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17288) Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly
rzanner updated JENKINS-17288 Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly Change By: rzanner (22/Mar/13 8:51 AM) Description: As described here: http://jenkins.361315.n4.nabble.com/Getting-NoSuchClassDefFoundError-for-ehcache-td391329.html, the spring-context-support JAR that is now (from version 1.502 on) packaged into the jenkins.war is loaded instead of the one from crowd/WEB-INF/lib. So it does not find classes from the ehcache JAR packaged only in the crowd/WEB-INF/lib.(see attached jenkins.log for complete stack trace)Two possible solutions:# remove the spring-context-support JAR from jenkins.war/WEB-INF/lib# switch class loader lookup order to search "plugin/WEB-INF/ -ib lib " first (this way it would be possible for plugin developers to override JARs delivered with the jenkins core)This issue prevents me from using the newest jenkins versions (starting from 1.502). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17318) Fitnesse pluging throws NullPointerException
Fried Hoeben
created JENKINS-17318
Fitnesse pluging throws NullPointerException
Issue Type:
Bug
Assignee:
Unassigned
Components:
fitnesse
Created:
22/Mar/13 8:56 AM
Description:
When I add the Fitnesse plugin to my build I get a NullPointerException. I'm probably doing somethings wrong, but what?
hudson.plugins.fitnesse.FitnesseBuilder: {fitnessePortLocal=8282, fitnesseJdk=Java6, fitnesseTargetPage=LegalAndGeneralIntegrationTests, fitnesseTargetIsSuite=true, fitnessePathToJar=fitnesse-standalone.jar, additionalFitnesseOptions=, fitnesseJavaOpts=, fitnesseHttpTimeout=6, fitnesseJavaWorkingDirectory=wiki, fitnessePathToRoot=FitNesseRoot, fitnesseStart=True, fitnessePathToXmlResultsOut=fitnesse-results.xml}
java.lang.NullPointerException
at hudson.plugins.fitnesse.FitnesseBuilder.getFitnesseHost(FitnesseBuilder.java:94)
at hudson.plugins.fitnesse.FitnesseExecutor.getFitnesseBuildAction(FitnesseExecutor.java:70)
at hudson.plugins.fitnesse.FitnesseExecutor.execute(FitnesseExecutor.java:46)
at hudson.plugins.fitnesse.FitnesseBuilder.perform(FitnesseBuilder.java:210)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814)
at hudson.model.Build$BuildExecution.build(Build.java:199)
at hudson.model.Build$BuildExecution.doRun(Build.java:160)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593)
at hudson.model.Run.execute(Run.java:1567)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
Build step 'Execute fitnesse tests' marked build as failure
Finished: FAILURE
Project:
Jenkins
Priority:
Major
Reporter:
Fried Hoeben
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17319) SSH sites disappear
François Dumont created JENKINS-17319 SSH sites disappear Issue Type: Bug Affects Versions: current Assignee: bap Components: publish-over-ssh Created: 22/Mar/13 9:23 AM Description: My SSH sites keep disappearing...All jobs using them get a blank site, then fail. Environment: Windows 2008 Server 64 bits Project: Jenkins Priority: Critical Reporter: François Dumont This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
SCM/JIRA link daemon resolved JENKINS-13412 as Fixed Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings Change By: SCM/JIRA link daemon (22/Mar/13 9:35 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
SCM/JIRA link daemon commented on JENKINS-13412 Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/gradle/Gradle.java http://jenkins-ci.org/commit/gradle-plugin/3ce68c23921a59b02d0159d9f7038941b88afada Log: [FIXED JENKINS-13412] use hudson.util.ArgumentListBuilder#toWindowsCommand – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17320) Warnings Plugin for GHS doesnt' get the filename correct
Thorsten Scheepers created JENKINS-17320 Warnings Plugin for GHS doesnt' get the filename correct Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 22/Mar/13 10:01 AM Description: The GHS Plugin doesn't get the file name correct. Example from Output: "../../../40_cmn/include/Source/IoHwAb.h", line 219: warning #301-D: typedef name has already been declared (with same type) typedef uint16 IoHwAb_AnalogValueType; Warning plugin recognizes the following: IoHwAb.h":189, GHS Multi Compiler, Priorität: Normal typedef name has already been declared (with same type) typedef uint8 IoHwAb_AnalogInputStatusType; => Take a look on the double quotes This is stored in the tmp-File in the build-workspace: 1 Copying the source file './../../40_cmn/include/Source/IoHwAb.h"' from the workspace to the build folder 'C:...\builds\2013-03-22_10-24-31\workspace-files\709f15f2.tmp' on the Hudson master failed. 2 Seems that the path is relative, however an absolute path is required when copying the sources. 3 Is the file 'IoHwAb.h"' contained more than once in your workspace? 4 Is the file './../../40_cmn/include/Source/IoHwAb.h"' a valid filename? 5 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]/./../../40_cmn/include/Source/IoHwAb.h"' 6 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace/./../../40_cmn/include/Source/IoHwAb.h"' Environment: Windows XP-32, Jenkins 1.506, Warnings Plugin 4.23 MULTI Compiler 2012.5 Project: Jenkins Priority: Minor Reporter: Thorsten Scheepers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7813) Archiving artifacts very slow
Tom Fanning commented on JENKINS-7813 Archiving artifacts very slow Thank you very much! Look forward to seeing this in a release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16868) Icons are not displayed with a reverse proxy
Sylvain C. commented on JENKINS-16868 Icons are not displayed with a reverse proxy This update fix my issue. thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17320) Warnings Plugin for GHS doesnt' get the filename correct
Ulli Hafner commented on JENKINS-17320 Warnings Plugin for GHS doesnt' get the filename correct This shouldn't be hard to fix: interested in providing a 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] (JENKINS-7813) Archiving artifacts very slow
David Karlsen commented on JENKINS-7813 Archiving artifacts very slow Yes - hope it will be backported into the LTS real soon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17321) Nothing to do, not fail
Christian Wolfgang created JENKINS-17321 Nothing to do, not fail Issue Type: Improvement Assignee: Praqma Support Components: config-rotator Created: 22/Mar/13 11:06 AM Project: Jenkins Priority: Major Reporter: Christian Wolfgang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17321) Nothing to do, not fail
Christian Wolfgang resolved JENKINS-17321 as Duplicate Nothing to do, not fail 14746 case 6843 Change By: Christian Wolfgang (22/Mar/13 11:07 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17128) Quoted label expression can result into throwing exception
SCM/JIRA link daemon commented on JENKINS-17128 Quoted label _expression_ can result into throwing exception Code changed in jenkins User: Vojtech Juranek Path: core/src/main/java/jenkins/model/Jenkins.java test/src/test/java/hudson/model/labels/LabelExpressionTest.java http://jenkins-ci.org/commit/jenkins/42734675f4825e4856f67945981ce44d2190dbd6 Log: [FIXED JENKINS-17128] Unquote labels before processing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17128) Quoted label expression can result into throwing exception
SCM/JIRA link daemon resolved JENKINS-17128 as Fixed Quoted label _expression_ can result into throwing exception Change By: SCM/JIRA link daemon (22/Mar/13 11:15 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17084) ChangeLog should produce output even if some annotator fails
SCM/JIRA link daemon commented on JENKINS-17084 ChangeLog should produce output even if some annotator fails Code changed in jenkins User: Vojtech Juranek Path: core/src/main/java/hudson/scm/ChangeLogSet.java test/src/test/java/hudson/scm/ChangeLogSetTest.java http://jenkins-ci.org/commit/jenkins/0c46701287ebfa1719c66dcdbcbba57f36c2ac59 Log: [FIXED JENKINS-17084] Changelog should produce output even if some changelog annotator fails This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17128) Quoted label expression can result into throwing exception
SCM/JIRA link daemon commented on JENKINS-17128 Quoted label _expression_ can result into throwing exception Code changed in jenkins User: vjuranek Path: core/src/main/java/jenkins/model/Jenkins.java test/src/test/java/hudson/model/labels/LabelExpressionTest.java http://jenkins-ci.org/commit/jenkins/8ef261ef8d233a0a30384249f12945808c7f628b Log: Merge pull request #730 from vjuranek/label_cast_exception [FIXED JENKINS-17128] Unquote labels before processing Compare: https://github.com/jenkinsci/jenkins/compare/a689c472ab2b...8ef261ef8d23 – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17084) ChangeLog should produce output even if some annotator fails
SCM/JIRA link daemon commented on JENKINS-17084 ChangeLog should produce output even if some annotator fails Code changed in jenkins User: vjuranek Path: core/src/main/java/hudson/scm/ChangeLogSet.java test/src/test/java/hudson/scm/ChangeLogSetTest.java http://jenkins-ci.org/commit/jenkins/4a39c5ab0425e504783e955a79ba676b92798c80 Log: Merge pull request #729 from vjuranek/fix_pull646 [FIXED JENKINS-17084] Changelog should produce output even if some chang... Compare: https://github.com/jenkinsci/jenkins/compare/8ef261ef8d23...4a39c5ab0425 – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17084) ChangeLog should produce output even if some annotator fails
SCM/JIRA link daemon resolved JENKINS-17084 as Fixed ChangeLog should produce output even if some annotator fails Change By: SCM/JIRA link daemon (22/Mar/13 11:16 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17320) Warnings Plugin for GHS doesnt' get the filename correct
Thorsten Scheepers commented on JENKINS-17320 Warnings Plugin for GHS doesnt' get the filename correct Because I'm not familiar with the changing java sources I would try to create a specific warnings parser in the system configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17128) Quoted label expression can result into throwing exception
dogfood commented on JENKINS-17128 Quoted label _expression_ can result into throwing exception Integrated in jenkins_main_trunk #2397 [FIXED JENKINS-17128] Unquote labels before processing (Revision 42734675f4825e4856f67945981ce44d2190dbd6) Result = SUCCESS Vojtech Juranek : 42734675f4825e4856f67945981ce44d2190dbd6 Files : core/src/main/java/jenkins/model/Jenkins.java test/src/test/java/hudson/model/labels/LabelExpressionTest.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17084) ChangeLog should produce output even if some annotator fails
dogfood commented on JENKINS-17084 ChangeLog should produce output even if some annotator fails Integrated in jenkins_main_trunk #2397 [FIXED JENKINS-17084] Changelog should produce output even if some changelog annotator fails (Revision 0c46701287ebfa1719c66dcdbcbba57f36c2ac59) Result = SUCCESS Vojtech Juranek : 0c46701287ebfa1719c66dcdbcbba57f36c2ac59 Files : test/src/test/java/hudson/scm/ChangeLogSetTest.java core/src/main/java/hudson/scm/ChangeLogSet.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13206) Is it a short hop to upgrade to SVNKit 1.3.7
evernat resolved JENKINS-13206 as Fixed Is it a short hop to upgrade to SVNKit 1.3.7 As said in [1], SVNKit is currently 1.7.6 in the subversion plugin, so resolving as fixed. [1] https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin Change By: evernat (22/Mar/13 12:31 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] (JENKINS-17322) Svn-tagging failed on newly created branch
Fredrik Svärd created JENKINS-17322 Svn-tagging failed on newly created branch Issue Type: Bug Affects Versions: current Assignee: k2nakamura Components: svn-tag Created: 22/Mar/13 12:53 PM Description: Jenkins Subversion Tagging Plugin, version 1.16 fails to tag on a newly created branch. Subversion tag checks out: Checking out https://subversion03/svn/uniregrepos/branches/rel_20130413/src at revision '2013-03-20T14:50:45.673 +0100' . .. ... At revision 1061 Remote Module Location: https://subversion03/svn/uniregrepos/branches/rel_20130413/src@1060. Tag Base URL: https://subversion03/svn/uniregrepos/tags/D20130320_SVN001060_B0001_REL_20130413_PATCH. There was no old tag at https://subversion03/svn/uniregrepos/tags/D20130320_SVN001060_B0001_REL_20130413_PATCH. Subversion copy failed. svn: E160013: Path 'https://subversion03/svn/uniregrepos/branches/rel_20130413/src' does not exist in revision 1,060 Build step 'Perform Subversion tagging on successful build' marked build as failure It fails because the SVN Global Number for the newly created branch starts at #1061. The 'subversion tag' plugin picks SVN Global Number #1060. When I tried to commit to the newly created branch, the SVN Global Number is incremented and the subversion tag plugin works. Due Date: 22/Mar/13 12:00 AM Environment: Linux, x86-hardware Project: Jenkins Labels: plugin Priority: Major Reporter: Fredrik Svärd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17323) Log lines print without newlines
Chris Tooley created JENKINS-17323 Log lines print without newlines Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: vsphere-cloud Created: 22/Mar/13 1:03 PM Description: The log entries when connecting a vSphere Cloud API Slave do not end with newlines. This causes the log to be a little less useful as it's not viewable in the web ui until the slave starts connecting instead of while it's being reset. Not a terribly big deal, but would make the logs much more useful. Project: Jenkins Priority: Minor Reporter: Chris Tooley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-4949) Deploy to more than one container
Hans-Joachim Kliemeck commented on JENKINS-4949 Deploy to more than one container https://github.com/jenkinsci/deploy-plugin/pull/8 is there any progress on this issue? i would like to deploy my war files instead of using ssh for my deploy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17242) pushes no longer being recorded in destination repository
Kevin Bond commented on JENKINS-17242 pushes no longer being recorded in destination repository I had this problem as well. Upgrading the Git Client plugin to 1.0.5 solved the issue. See: https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin#GitClientPlugin-1.0.5%28march21%2C2013%29 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17324) Update Center reboot flag problems
Bruno Cunha created JENKINS-17324 Update Center reboot flag problems Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: update-center Created: 22/Mar/13 1:47 PM Description: Hello. I observed that the "Restart Jenkins when installation is complete and no jobs are running" checkbox on the Update Center does not reflect the real state of the environment. If my server is going to shut down previously marked by "/quietDown", the flag will be marked, but it doesn't guarantee that the server will really restart after the updates. I had an experience that server only shutdown after I cancel that previously mark (/cancelQuietDown), and re-select the checkbox on Update Manager. Thank you! Regards, Bruno Candido Volpato da Cunha Environment: Jenkins ver. 1.506 Project: Jenkins Priority: Major Reporter: Bruno Cunha This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17324) Update Center reboot flag problem
Bruno Cunha updated JENKINS-17324 Update Center reboot flag problem Change By: Bruno Cunha (22/Mar/13 1:47 PM) Summary: Update Center reboot flag problems 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16608) View name allows '..'
Jacob Robertson updated JENKINS-16608 View name allows '..' Change By: Jacob Robertson (22/Mar/13 2:18 PM) Assignee: Jacob Robertson 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15624) Rest API for view manipulation
Jacob Robertson updated JENKINS-15624 Rest API for view manipulation Change By: Jacob Robertson (22/Mar/13 2:18 PM) 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Matt Williamson commented on JENKINS-17265 Builds disappearing from history Same issue on 1.506, job history for some jobs disappears. Selecting "Reload Configuration from Disk" brings the history back. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15239) Tags feature is broken
Adam PAPAI commented on JENKINS-15239 Tags feature is broken What's up with this issue? Can we release a newer version? As far as I can see the development is happening in the background. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17277) Jenkins iOS job broken because “FATAL: Log statements out of sync: current test case was null”
Christopher Disdero closed JENKINS-17277 as Not A Defect Jenkins iOS job broken because “FATAL: Log statements out of sync: current test case was null” Discovered that it's really a bug in the iOS-sim code. If you download the project from https://github.com/phonegap/ios-sim and search the source code for "[DEBUG]", you'll find it in one place. If you remove that from the printf statement and rebuild the project, this issue appears to vanish. Change By: Christopher Disdero (22/Mar/13 2:54 PM) Status: Open Closed Fix Version/s: current Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17325) SVN Plugin does a full checkout when variables used in the SVN Repo URL even if 'svn update' checked
Rick L created JENKINS-17325 SVN Plugin does a full checkout when variables used in the SVN Repo URL even if 'svn update' checked Issue Type: Bug Assignee: Unassigned Components: subversion Created: 22/Mar/13 3:45 PM Description: When using the SVN Plugin to perform a repository extract during a build, the build pulls all files each time even though the 'svn update' option is selected. When the variables are removed from the repository url line, the svn update works as expected. Our SVN Repo URL = ""> Environment: Jenkins master on Linux. Project: Jenkins Priority: Major Reporter: Rick L This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16940) Git publisher fails with "Invalid id: origin/master" when trying to publish changes
Mark Waite commented on JENKINS-16940 Git publisher fails with "Invalid id: origin/master" when trying to publish changes The git client plugin 1.4.0 reported the push but did not actually push enough information to the remote server so that others could use it. I have confirmed that the git client plugin 1.5.0 does push enough information for others to use the resulting push. The full fix of this bug requires git client plugin 1.5.0 and glit plugin 1.3.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17242) pushes no longer being recorded in destination repository
Mark Waite resolved JENKINS-17242 as Fixed pushes no longer being recorded in destination repository git client plugin 1.0.5 resolved this issue for me and one other person. Change By: Mark Waite (22/Mar/13 4:21 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] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Mark Waite commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Since git-client-plugin 1.0.5 reverted to using the git CLI instead of using JGit as its default, I think this bug is fixed by git-client-plugin 1.0.5. Can you check that the issue is resolved by installing git-client-plugin 1.0.5? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Mark Waite commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ The git-client-plugin 1.0.5 has switched back to using the CLI version as its default implementation. It is available for download now. Does that resolve this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Matt Williamson commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client I'm running "Jenkins GIT client plugin" 1.0.4, but it doesn't show any updates available. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Steve Haworth commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ git-client-plugin 1.0.5, has fully resolved my issues associated with Git cloning to conduct slave jenkins builds (Linux) from the Master (Windows) 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] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Mark Waite commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files @Dallas, I believe git-client-plugin 1.0.5 acknowledges that the JGit implementation is not yet mature enough for general purpose use as a replacement for the git command line implementation. When the JGit implementation has the necessary features, the plugin maintainer will consider changing the default to use JGit instead of using the command line. For at least some bug reports, there is a robot that resolves the issue when a submission is made that declares the issue is resolved. I interpreted that to mean that anyone can resolve an issue, including the submitter of the change which fixes the issue. The project does not seem to require or mandate that the issue can only be resolved by the person who reported the issue. In this case, I think it would be great if the original submitter would install git-client-plugin 1.0.5 and confirm the issue is resolved, but in the general case, if the issue is resolved, anyone can mark it as resolved. The plugin maintainer can still refer to this bug report (and others) before the next time when it is chosen to make JGit the default implementation instead of using the CLI implementation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17252) JGit checkout poor performaces
Mark Waite commented on JENKINS-17252 JGit checkout poor performaces git-client-plugin 1.0.5 reverts to using command line git for its implementation. Can you confirm that installing the git-client-plugin 1.0.5 resolves this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Mark Waite commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Go to the "Advanced" tab in the "Manage Plugins" section and you'll see an "Update Now" button in the bottom right corner. Above that "Update Now" button it will show the last time it polled for updates. If you press the "Update Now", it will poll immediately, and should then show the 1.0.5 plugin is available. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17326) Git Wipe Out stopped working
omissis created JENKINS-17326 Git Wipe Out stopped working Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 22/Mar/13 4:54 PM Description: Hi, I've just reinstalled jenkins on my new server and ported all the old tasks to the new instance. It all works fine, but if I enable the "Wipe out workspace before build" in git plugin(it was previously enabled and working fine), the clone fails leaving the job's workspace with 0666 permissions (so it "chmods a-x" the workspace directory); I checked the umask and it looks correct, it's 0002. If I remove the flag, clearly the workspace doesn't get wiped out but everything works again pretty well. This is the output from the console(I replaced some names): Building in workspace /var/lib/jenkins/jobs/MyProject/workspace Checkout:workspace / /var/lib/jenkins/jobs/MyProject/workspace - hudson.remoting.LocalChannel@20a26542 Using strategy: Default Last Built Revision: Revision ad1e4166745f9e33c9851bdefb7494de9651df23 (origin/master) Using shallow clone Wiping out workspace first. Cloning the remote Git repository Cloning repository g...@git.mycompany.com:myproject/myproject-001/myrepository.git Error trying to determine the git version: Error performing command: git --version Assuming 1.6 ERROR: Error cloning remote repo 'origin' : Could not clone g...@git.mycompany.com:myproject/myproject-001/myrepository.git hudson.plugins.git.GitException: Could not clone g...@git.mycompany.com:myproject/myproject-001/myrepository.git at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clone(CliGitAPIImpl.java:219) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1002) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1113) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:689) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:594) at hudson.model.Run.execute(Run.java:1567) 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 clone -o origin --depth 1 g...@git.mycompany.com:myproject/myproject-001/myrepository.git /var/lib/jenkins/jobs/MyProject/workspace" returned status code 128: stdout: stderr: fatal: destination path '/var/lib/jenkins/jobs/MyProject/workspace' already exists and is not an empty directory. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:773) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clone(CliGitAPIImpl.java:217) ... 14 more Trying next repository ERROR: Could not clone repository FATAL: Could not clone hudson.plugins.git.GitException: Could not clone at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1014) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:941) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:941) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1113) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:689) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:594) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceCo
[JIRA] (JENKINS-17242) pushes no longer being recorded in destination repository
A K commented on JENKINS-17242 pushes no longer being recorded in destination repository Excellent. I am glad to hear that. (I saw the new 1.0.5 come out but didn't have a chance to test it). The solution is also comforting/as-expected given the previous release notes, so I am optimistic it is fixed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Matt Williamson commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client Great, looks like that fixed all our issues! For others... Manage Jenkins -> Manage Plugins -> Advanced Tab -> Check now button (bottom right corner) Manage Jenkins -> Manage Plugins -> Updates Tab -> Install all (specifically Jenkins GIT Client Plugin 1.0.5) Thank you!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17315) Nested view no longer shows unless logged in
pmv commented on JENKINS-17315 Nested view no longer shows unless logged in I'm starting to think this may be related to JENKINS-3681. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17327) Subprojects of the Parameterized trigger plugin are not shown in jsplumb view
domi created JENKINS-17327 Subprojects of the Parameterized trigger plugin are not shown in jsplumb view Issue Type: Bug Assignee: wolfs Components: depgraph-view Created: 22/Mar/13 5:24 PM Description: The dependency typ subproject introduced by the parameterized trigger plugin are not shown in the jsplumb view. A job triggered by the parameterized trigger plugin does not have any edge to its trigger job. sorry I mark this one a critical, but as we use this plugin without the graphviz integration this a very essential missing piece. Project: Jenkins Priority: Critical Reporter: domi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17315) Nested view no longer shows unless logged in
pmv resolved JENKINS-17315 as Fixed Nested view no longer shows unless logged in Found (and linked) duplicate issue. Fix is to give the new View 'Read' permission to Anonymous - no changes needed here. Thanks. Change By: pmv (22/Mar/13 5: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] (JENKINS-17325) SVN Plugin does a full checkout when variables used in the SVN Repo URL even if 'svn update' checked
Rick L resolved JENKINS-17325 as Not A Defect SVN Plugin does a full checkout when variables used in the SVN Repo URL even if 'svn update' checked After conducting more tests, it is working the right way. I must have missed something in my original test scenario. Thank you. Change By: Rick L (22/Mar/13 5:31 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17328) output.xml kept open after build if parsing error occurs causing subsequent runs to fail
Kevin Ormbrek
created JENKINS-17328
output.xml kept open after build if parsing error occurs causing subsequent runs to fail
Issue Type:
Bug
Assignee:
jpiironen
Components:
robot-plugin
Created:
22/Mar/13 5:54 PM
Description:
Steps to reproduce:
Have an output.xml file with broken XML when the plugin processes the results.
After the job fails, try to delete the output.xml file.
Expected:
Can delete the file.
Actual:
File in use, cannot be deleted. The JVM's process keeps the file open. This causes subsequent job runs to fail until the slave agent is restarted to release the file.
Stack trace from when the file is opened and not closed:
hudson.util.IOException2: remote file operation failed: C:\Jenkins\workspace\Apollo_SKU_IT\test-output at hudson.remoting.Channel@c591b4:Robot-2
at hudson.FilePath.act(FilePath.java:861)
at hudson.FilePath.act(FilePath.java:838)
at hudson.plugins.robot.RobotParser.parse(RobotParser.java:45)
at hudson.plugins.robot.RobotPublisher.parse(RobotPublisher.java:239)
at hudson.plugins.robot.RobotPublisher.perform(RobotPublisher.java:261)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733)
at hudson.model.Run.execute(Run.java:1592)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
Caused by: hudson.remoting.ProxyException: java.io.IOException: Parsing of output xml failed!
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:90)
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:50)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:58)
at java.lang.Thread.run(Unknown Source)
Caused by: hudson.remoting.ProxyException: com.ctc.wstx.exc.WstxEOFException: Unexpected end of input block in end tag
at [row,col {unknown-source}]: [1649,61]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOB(StreamScanner.java:700)
at com.ctc.wstx.sr.StreamScanner.loadMoreFromCurrent(StreamScanner.java:1054)
at com.ctc.wstx.sr.StreamScanner.getNextCharFromCurrent(StreamScanner.java:811)
at com.ctc.wstx.sr.BasicStreamReader.readEndElem(BasicStreamReader.java:3206)
at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2832)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
at hudson.plugins.robot.RobotParser$RobotParserCallable.processTest(RobotParser.java:190)
at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:158)
at hudson.plugins.robot.RobotParser$RobotParserCallable.parseResult(RobotParser.java:114)
at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:88)
... 12 more
Environment:
Jenkins 1.505 (job running on a slave that has Java 1.6.0_30-b12 on Windows Server 2003 32-bit), Robot Framework Plugin 1.2.3
Project:
Jenkins
Priority:
[JIRA] (JENKINS-17195) InvalidTagNameException with version 1.0.4 of git client
Mark Waite resolved JENKINS-17195 as Fixed InvalidTagNameException with version 1.0.4 of git client git-client-plugin 1.0.5 resolved this by switching back to the CLI as the default git implementation. Change By: Mark Waite (22/Mar/13 6:10 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Mark Waite resolved JENKINS-17204 as Fixed GIT plugin fetch failing since update Git Plugin to 1.2.0+ Resolved in git-client-plugin 1.0.5 Change By: Mark Waite (22/Mar/13 6:16 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] (JENKINS-16680) Downstream project being triggered twice since installing v0.11 version of plugin
Thomas Fields commented on JENKINS-16680 Downstream project being triggered twice since installing v0.11 version of plugin Any chance for a fix for this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10147) Add 'poll SCM' option to build step
Thomas Fields commented on JENKINS-10147 Add 'poll SCM' option to build step Are we any closer to getting this released? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12983) Redundat syncs when using matrix jobs
Thomas Fields commented on JENKINS-12983 Redundat syncs when using matrix jobs How many votes are required for this to be fixed? It'd be nice if this was fixed soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Jared Griffith commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Works perfectly with the 1.0.5 version. Thank you! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16608) View name allows '..'
sogabe assigned JENKINS-16608 to sogabe View name allows '..' Change By: sogabe (22/Mar/13 6:36 PM) Assignee: sogabe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16608) View name allows '..'
SCM/JIRA link daemon resolved JENKINS-16608 as Fixed View name allows '..' Change By: SCM/JIRA link daemon (22/Mar/13 6:41 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] (JENKINS-16608) View name allows '..'
SCM/JIRA link daemon commented on JENKINS-16608 View name allows '..' Code changed in jenkins User: Seiji Sogabe Path: changelog.html core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/hudson/model/Messages_ja.properties test/src/test/java/hudson/model/ViewTest.java http://jenkins-ci.org/commit/jenkins/d8b29df3558724090efaf18326937075c25ba7f3 Log: [FIXED JENKINS-16608] View name should not allow "..". – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17311) Expand and encourage use of hash syntax in crontabs
Jesse Glick updated JENKINS-17311 Expand and encourage use of hash syntax in crontabs Change By: Jesse Glick (22/Mar/13 7:20 PM) URL: https://github.com/jenkinsci/jenkins/pull/743 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17329) JSON exception in jenkins v 1.506
Ravinder Batra
created JENKINS-17329
JSON exception in jenkins v 1.506
Issue Type:
Bug
Assignee:
wolfs
Components:
all-changes
Created:
22/Mar/13 7:19 PM
Description:
Failed to parse form data. Please report this problem as a bug
JSON={"name":"BuybackInterface-01-Build","description":"","":["","0"],"logrotate":false,"buildDiscarder":{"stapler-class":"hudson.tasks.LogRotator","daysToKeepStr":"","numToKeepStr":"","artifactDaysToKeepStr":"","artifactNumToKeepStr":""},"properties":{"stapler-class-bag":"true","hudson-security-AuthorizationMatrixProperty":{"useProjectSecurity":{"data":{"DEV":{"hudson.model.Item.Delete":false,"hudson.model.Item.Configure":false,"hudson.model.Item.Read":true,"hudson.model.Item.Discover":false,"hudson.model.Item.ExtendedRead":true,"hudson.model.Item.Build":true,"hudson.model.Item.Workspace":true,"hudson.model.Item.Cancel":false,"hudson.model.Run.Delete":false,"hudson.model.Run.Update":false,"hudson.scm.SCM.Tag":false},"anonymous":{"hudson.model.Item.Delete":false,"hudson.model.Item.Configure":false,"hudson.model.Item.Read":false,"hudson.model.Item.Discover":false,"hudson.model.Item.ExtendedRead":false,"hudson.model.Item.Build":false,"hudson.model.Item.Workspace":false,"hudson.model.Item.Cancel":false,"hudson.model.Run.Delete":false,"hudson.model.Run.Update":false,"hudson.scm.SCM.Tag":false}},"":""}},"com-coravy-hudson-plugins-github-GithubProjectProperty":{"projectUrl":""},"hudson-model-ParametersDefinitionProperty":{},"hudson-plugins-svn_release_mgr-JobPropertyImpl":{},"org-jenkinsci-plugins-envinject-EnvInjectJobProperty":{}},"jdk":"(Default)","hasSlaveAffinity":{"assignedLabelString":"NIX"},"displayNameOrNull":"","scm":{"value":"6","locations":{"remote":"https://svn.cheggnet.com/svn/Corp/backoffice/interface/buyback/trunk","local":".","depthOption":"infinity","ignoreExternalsOption":false},"":["2","7"],"workspaceUpdater":{"stapler-class":"hudson.scm.subversion.UpdateWithCleanUpdater"},"browser":{"stapler-class":"hudson.plugins.viewVC.ViewVCRepositoryBrowser","url":"https://svn.cheggnet.com/","location":"Corp"},"ignoreDirPropChanges":false,"excludedRegions":"","includedRegions":"","excludedUsers":"","excludedCommitMessages":"","excludedRevprop":"","filterChangelog":false},"hudson-triggers-SCMTrigger":{"scmpoll_spec":"* * * * *","ignorePostCommitHooks":false},"hudson-plugins-timestamper-TimestamperBuildWrapper":{},"builder":[{"description":"","switches":"-i -g .gradle","tasks":"clearCaches clean","rootBuildScriptDir":"","buildFile":"","stapler-class":"hudson.plugins.gradle.Gradle","kind":"hudson.plugins.gradle.Gradle"},{"description":"","switches":"-i -g .gradle","tasks":"assemble","rootBuildScriptDir":"","buildFile":"","stapler-class":"hudson.plugins.gradle.Gradle","kind":"hudson.plugins.gradle.Gradle"},{"useWrapper":{"value":"false","gradleName":"1.2"},"description":"","switches":"-i -g .gradle","tasks":"uploadA","rootBuildScriptDir":"","buildFile":"","stapler-class":"hudson.plugins.gradle.Gradle","kind":"hudson.plugins.gradle.Gradle"}],"publisher":[{"childProjects":"BuybackService-01-Build, ","threshold":"SUCCESS","stapler-class":"hudson.tasks.BuildTrigger","kind":"hudson.tasks.BuildTrigger"},{"reportTargets":{"reportDir":"build/docs/javadoc","reportFiles":"index.html","reportName":"Catalog Javadocs","keepAll":false},"stapler-class":"htmlpublisher.HtmlPublisher","kind":"htmlpublisher.HtmlPublisher"},{"recipientlist_recipients":"c...@chegg.com","project_replyto":"","project_content_type":"default","project_default_subject":"$DEFAULT_SUBJECT","project_default_content":"$DEFAULT_CONTENT","project_attachments":"","project_presend_script":"","mailer_Failure_configured":"true","mailer_Failure_sendToRecipientList":true,"mailer_Failure_sendToDevelopers":true,"mailer_Failure_sendToRequester":false,"mailer_Failure_includeCulprits":false,"mailer_Failure_recipientList":"","mailer_Failure_replyTo":"","mailer_Failure_subject":"$PROJECT_DEFAULT_SUBJECT","mailer_Failure_body":"$PROJECT_DEFAULT_CONTENT","mailer_Failure_attachmentsPattern":"","mailer_Failure_attachBuildLog":false,"mailer_Failure_compressBu
[JIRA] (JENKINS-16608) View name allows '..'
dogfood commented on JENKINS-16608 View name allows '..' Integrated in jenkins_main_trunk #2398 [FIXED JENKINS-16608] View name should not allow "..". (Revision d8b29df3558724090efaf18326937075c25ba7f3) Result = SUCCESS Seiji Sogabe : d8b29df3558724090efaf18326937075c25ba7f3 Files : test/src/test/java/hudson/model/ViewTest.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/hudson/model/Messages_ja.properties core/src/main/resources/hudson/model/Messages.properties changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17330) FilePath.installIfNecessaryFrom routes download over remoting channel
Jesse Glick created JENKINS-17330 FilePath.installIfNecessaryFrom routes download over remoting channel Issue Type: Bug Assignee: Jesse Glick Components: core Created: 22/Mar/13 8:18 PM Description: Installing a large downloaded tool on a network slave can be quite slow: "Executor #... for ... : executing ... #... / waiting for hudson.remoting.Channel@...:HTTP full-duplex channel ..." Id=... Group=main TIMED_WAITING on hudson.remoting.UserRequest@... at java.lang.Object.wait(Native Method) - waiting on hudson.remoting.UserRequest@... at hudson.remoting.Request.call(Request.java:146) at hudson.remoting.Channel.call(Channel.java:672) at hudson.FilePath.act(FilePath.java:831) at hudson.FilePath.act(FilePath.java:824) at hudson.FilePath.unzipFrom(FilePath.java:485) at hudson.FilePath.installIfNecessaryFrom(FilePath.java:718) at hudson.tools.DownloadFromUrlInstaller.performInstallation(DownloadFromUrlInstaller.java:72) at com.soasta.jenkins.MakeAppTouchTestableInstaller.performInstallation(MakeAppTouchTestableInstaller.java:49) at com.soasta.jenkins.MakeAppTouchTestable.perform(MakeAppTouchTestable.java:94) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:728) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:510) at hudson.model.Run.execute(Run.java:1505) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) JENKINS-7813 is partly to blame, but the main issue here is that the URL is being opened on master, a RemoteInputStream constructed, and the archive unpacked on the slave. It would be much faster to open the URL directly from the slave and use the remoting channel only for control. In typical cases the slave can access a tool URL. There are some rarer cases where it is really intentional that the URL is resolved from the master; it might be a file-protocol URL, the slave might have no public internet access, the download location might be limited to particular IPs, etc. So installIfNecessaryFrom should first try to open from the slave, then fall back to the current implementation. Project: Jenkins Labels: performance lts-candidate Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12007) copying artifact to windows node very slow
Jesse Glick resolved JENKINS-12007 as Duplicate copying artifact to windows node very slow Probably improved by JENKINS-7813 fixes. Change By: Jesse Glick (22/Mar/13 8:22 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-4995) Support windows AMI's in EC2 plugin
Matthew Batema commented on JENKINS-4995 Support windows AMI's in EC2 plugin Having the EC2 plugin support Windows would be great; it would keep me from writing custom scripts. However, has there been much progress of late? I do see that the issue has been "In Progress" for the last year and change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3922) Slave is slow copying maven artifacts to master
Jesse Glick resolved JENKINS-3922 as Duplicate Slave is slow copying maven artifacts to master Probably improved by JENKINS-7813 fixes. Change By: Jesse Glick (22/Mar/13 8:24 PM) Status: Reopened Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3799) Slave-to-master copies can be extremely slow
Jesse Glick resolved JENKINS-3799 as Duplicate Slave-to-master copies can be extremely slow Probably improved by JENKINS-7813 fixes. Change By: Jesse Glick (22/Mar/13 8:26 PM) Status: Reopened Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14117) The plugin hasn't been performed correctly: remote file operation failed
Corey O'Connor commented on JENKINS-14117 The plugin hasn't been performed correctly: remote file operation failed I am able to reproduce this randomly. This appears to depend on the speed at which a slave fsync's the directory containing the XML data. The only entry from the log is: [xUnit] [ERROR] - The plugin hasn't been performed correctly: remote file operation failed: /var/lib/role-jenkins-alfred/jenkins_slave_data_root/workspace/qa-tools-ui-test-support-functional-tests at hudson.remoting.Channel@a907d8a:alfred_5 No additional information is output to either the slave log or master log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize The git-client-plugin 1.0.5 and git-plugin 1.3.0 still show the same problem when attempting a build from a slave agent. The same build works fine if it is restricted to the master node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8616) cannot use spot instances
Eric Caron commented on JENKINS-8616 cannot use spot instances My team and I at the Rochester Institute of Technology have been working with Amazon to add this feature and earlier today we submitted a 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] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize
Mark Waite edited a comment on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize The git-client-plugin 1.0.5 and git-plugin 1.3.0 still show the same problem when attempting a build from a slave agent. The same build works fine if it is restricted to the master node. That seems to indicate that this issue is not directly related to whether the git implementation is JGit or command line Git. The git-client-plugin 1.0.4 implementation default was JGit (which showed the problem). The git-client-plugin 1.0.5 implementation default is command line Git (which also shows 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17331) "Local to the workspace" repository locator does not work when building one module in isolation
Jesse Glick created JENKINS-17331 "Local to the workspace" repository locator does not work when building one module in isolation Issue Type: Bug Assignee: Jesse Glick Components: maven Created: 22/Mar/13 9:19 PM Description: MavenProjectTest.testDeleteSetBuildDeletesModuleBuilds used to fail in some environments because it was using the default local repository, and a build of one submodule in isolation failed to find the installed snapshot artifact of its reactor dependency. Using PerExecutorLocalRepositoryLocator sometimes works, but only if the same executor runs both builds. PerJobLocalRepositoryLocator looks like it should work, but does not because when running the individual module build it uses a different repository from the module set build. You would expect that in an aggregator project where modules have snapshot interdependencies, if you have built the whole module set then you should also be able to rerun a single module build and that it should find the dependency artifacts in the workspace, using a repository at top level. Project: Jenkins Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14608) Crash on firefox 14.0.1
celltestr commented on JENKINS-14608 Crash on firefox 14.0.1 So I am able the reproduce this crash reliably. Looks like firefox is crashing only when one of the pipeline jobs is running. If nothing is running in the pipeline firefox wouldn't crash. When triggering one of the pipeline jobs (doesn't remember if it's triggered using the pipeline of from a different view) and keeping the firefox tab on the pipeline view, the second the job is finished firefox will stop responding. I am still able to see the job flashes green after a successful run and then a few seconds after it crashes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17331) "Local to the workspace" repository locator does not work when building one module in isolation
SCM/JIRA link daemon resolved JENKINS-17331 as Fixed "Local to the workspace" repository locator does not work when building one module in isolation Change By: SCM/JIRA link daemon (22/Mar/13 9:28 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] (JENKINS-17331) "Local to the workspace" repository locator does not work when building one module in isolation
SCM/JIRA link daemon commented on JENKINS-17331 "Local to the workspace" repository locator does not work when building one module in isolation Code changed in jenkins User: Jesse Glick Path: changelog.html maven-plugin/src/main/java/hudson/maven/MavenBuild.java maven-plugin/src/main/java/hudson/maven/local_repo/PerJobLocalRepositoryLocator.java test/src/test/java/hudson/maven/MavenProjectTest.java http://jenkins-ci.org/commit/jenkins/56c6aa32273df43ba1d5cec375e256cc40c07f6e Log: [FIXED JENKINS-17331] PerJobLocalRepositoryLocator should prefer the MavenModuleSetBuild.workspace for single-module builds. – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10274) Can this plugin support CLOC for even more languages and better Windows support
Adam Westhusing reopened JENKINS-10274 Can this plugin support CLOC for even more languages and better Windows support It doesn't appear this works for the current version. I'm using Cloc 1.58 with plugin version 1.8. I used the same method as the individuals above, and the output is not properly parsed by the sloccount plugin. Change By: Adam Westhusing (22/Mar/13 9:44 PM) Resolution: Won't Fix 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8616) cannot use spot instances
Jai Ram Rideout commented on JENKINS-8616 cannot use spot instances Awesome! I'm very excited to try it out! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-4995) Support windows AMI's in EC2 plugin
Frank Bille stopped work on JENKINS-4995 Support windows AMI's in EC2 plugin Change By: Frank Bille (22/Mar/13 10:11 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-4995) Support windows AMI's in EC2 plugin
Frank Bille assigned JENKINS-4995 to Unassigned Support windows AMI's in EC2 plugin I didn't made any progress on this issue, as I stopped using Jenkins together with EC2. I still believe that it would be fairly easy to integrate using the built-in WMI support in Jenkins. Change By: Frank Bille (22/Mar/13 10:13 PM) Assignee: Frank Bille This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17331) "Local to the workspace" repository locator does not work when building one module in isolation
dogfood commented on JENKINS-17331 "Local to the workspace" repository locator does not work when building one module in isolation Integrated in jenkins_main_trunk #2401 [FIXED JENKINS-17331] PerJobLocalRepositoryLocator should prefer the MavenModuleSetBuild.workspace for single-module builds. (Revision 56c6aa32273df43ba1d5cec375e256cc40c07f6e) Result = SUCCESS Jesse Glick : 56c6aa32273df43ba1d5cec375e256cc40c07f6e Files : changelog.html maven-plugin/src/main/java/hudson/maven/MavenBuild.java maven-plugin/src/main/java/hudson/maven/local_repo/PerJobLocalRepositoryLocator.java test/src/test/java/hudson/maven/MavenProjectTest.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Richard Buckle commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ git-client-plugin 1.0.5 has fully resolved my issues. Thank you very much for the quick response! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Richard Buckle edited a comment on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ What is the proper channel to request that the main Jenkins repo be rolled back to Git plugin v1.2.0 and client v1.0.3? Edit: I withdraw this question now that git-client-plugin 1.0.5 solves 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16181) Jenkins does not try to resend a failed e-mail
Mark Trinh commented on JENKINS-16181 Jenkins does not try to resend a failed e-mail I'm using 2.27.1 and i'm not seeing any retry messages. Email was triggered for: Success Sending email for trigger: Success Sending email to: x...@xx.com ERROR: Could not send email as a part of the post-build publishers. javax.mail.MessagingException: Could not connect to SMTP host: smtp.xx.com, port: 25; nested exception is: java.net.ConnectException: Connection refused at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1282) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:370) at javax.mail.Service.connect(Service.java:275) at javax.mail.Service.connect(Service.java:156) at javax.mail.Service.connect(Service.java:105) at javax.mail.Transport.send0(Transport.java:168) at javax.mail.Transport.send(Transport.java:98) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:317) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:296) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:256) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656) at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171) at hudson.model.Run.run(Run.java:1452) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:337) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:198) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) at java.net.Socket.connect(Socket.java:579) at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:230) at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:189) at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1250) ... 18 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Mark Waite closed JENKINS-17204 as Fixed GIT plugin fetch failing since update Git Plugin to 1.2.0+ Several different users have reported the issue is resolved. Thanks! Change By: Mark Waite (23/Mar/13 4:03 AM) 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17273) Polling fails attempting to set an invalid tag before build
Mark Waite commented on JENKINS-17273 Polling fails attempting to set an invalid tag before build The git-client-plugin 1.0.5 switches the default git implementation from JGit back to the command line git client. That change resolves this issue. I confirmed I could see the issue in git-client-plugin 1.0.4 and after upgrading to git-client-plugin 1.0.5 the issue is resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17273) Polling fails attempting to set an invalid tag before build
Mark Waite resolved JENKINS-17273 as Fixed Polling fails attempting to set an invalid tag before build Fixed in git-client-plugin 1.0.5 Change By: Mark Waite (23/Mar/13 4:14 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16181) Jenkins does not try to resend a failed e-mail
Alex Earl commented on JENKINS-16181 Jenkins does not try to resend a failed e-mail Retry will currently only occur on SocketExceptions, would need to add something for ConnectException This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16181) Jenkins does not try to resend a failed e-mail
Mark Trinh commented on JENKINS-16181 Jenkins does not try to resend a failed e-mail Adding ConnectException would be very helpful. Do you think it is possible? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Richard Buckle commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Thank you very much for your work, Mark Waite! Of course the issues in the JGit implementation remain, but that is a matter for another ticket. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Mark Waite commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ The real work is done by Nicolas Deloof, the maintainer of the git plugin. He's handled the challenges of a complex refactoring and recovering from the unexpected gaps in JGit functionality very well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17212) Git clean broken on Windows
Mark Waite commented on JENKINS-17212 Git clean broken on Windows I am unable to duplicate this problem with git-client-plugin 1.0.5. I confirmed that the workspace is cleaned on each build by having the job create an internal tag for the build, and confirming by browsing the workspace after the build to confirm that only the most recent tag is in the repository, not the tag from other builds. I was using a very small repository for my tests, and was cloning to a Windows Home Server 2011 machine. Your results may be different than mine, depending on repository size, virus scanning engine, etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Richard Buckle commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ In that case huge thanks to Nicolas Deloof also! I am in general very impressed with how swiftly this issue has been dealt with. I fully understand how much more complex these things can be than appears to a mere user. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17212) Git clean broken on Windows
Mark Waite edited a comment on JENKINS-17212 Git clean broken on Windows I am unable to duplicate this problem with git-client-plugin 1.0.5. I verified that the workspace is cleaned on each build by having the job create an internal tag for the build, then browsing the workspace after the build to see that only the most recent tag is in the repository, not the tag from previous builds. I was using a very small repository for my tests, and was cloning to a Windows Home Server 2011 machine. Your results may be different than mine, depending on repository size, virus scanning engine, etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17318) Fitnesse pluging throws NullPointerException
Ricardo Torres commented on JENKINS-17318 Fitnesse pluging throws NullPointerException I have sent a pull request I believe addresses this issue after having encountered the same exception on Windows Server 2012 and CentOS 6.3: https://github.com/jenkinsci/fitnesse-plugin/pull/5 This message is automatically generated by JIRA. 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.
