[JIRA] (JENKINS-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
dogfood commented on JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. Integrated in jenkins_main_trunk #2281 [FIXED JENKINS-12251] (Revision 61a83bd657ec93bed6278a3abf3a91c77826ec46) Result = SUCCESS kohsuke : 61a83bd657ec93bed6278a3abf3a91c77826ec46 Files : core/src/main/resources/jenkins/model/Jenkins/help-rawWorkspaceDir.html core/src/main/resources/jenkins/model/Jenkins/help-rawBuildsDir_ja.html core/src/main/resources/jenkins/model/Jenkins/help-rawBuildsDir.html core/src/main/resources/jenkins/model/Jenkins/help-rawWorkspaceDir_ja.html test/src/test/java/jenkins/model/JenkinsTest.java core/src/main/java/jenkins/model/Jenkins.java 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-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
SCM/JIRA link daemon resolved JENKINS-12251 as Fixed Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. Change By: SCM/JIRA link daemon (16/Feb/13 6:06 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-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
SCM/JIRA link daemon
commented on JENKINS-12251
Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/src/main/java/jenkins/model/Jenkins.java
core/src/main/resources/jenkins/model/Jenkins/help-rawBuildsDir.html
core/src/main/resources/jenkins/model/Jenkins/help-rawBuildsDir_ja.html
core/src/main/resources/jenkins/model/Jenkins/help-rawWorkspaceDir.html
core/src/main/resources/jenkins/model/Jenkins/help-rawWorkspaceDir_ja.html
test/src/test/java/jenkins/model/JenkinsTest.java
http://jenkins-ci.org/commit/jenkins/61a83bd657ec93bed6278a3abf3a91c77826ec46
Log:
[FIXED JENKINS-12251]
Introduced ${ITEM_FULL_NAME} to address the ticket without causing the
backward compatibility problem.
–
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-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
Zoltán Buza commented on JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. I have created a pull request which fixes this issue: https://github.com/jenkinsci/jenkins/pull/709 This message is automatically generated by JIRA. 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-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
kutzi updated JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. Change By: kutzi (19/Dec/12 8:38 AM) Component/s: maven2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
sweetfa commented on JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. This issue is still current as of release 1.494. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
Costin Caraivan commented on JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. Hello, This means that Maven 3 is unusable in any kind of Jenkins install on Windows. Without this setting we'd have to hold the builds in the same folder as the configs - this is not feasible for lots of builds So - bump! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
Jamie Cramb commented on JENKINS-12251 Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows. Any work-around for this yet? Are there any variables we can use instead of ITEM_FULLNAME that would still give a unique name per-job? Environment: Windows Server 2008 R2 64bit, Jenkins 1.466.2. Thanks in advance! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12251) Maven3 with 'builds' directory in a separate location tries to create folders with colons in the module name which is not allowed on windows.
[
https://issues.jenkins-ci.org/browse/JENKINS-12251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163510#comment-163510
]
jean-baptiste renaux commented on JENKINS-12251:
Hi,
I also have this problem on Windows 7 with Jenkins 1.466.
Is there a solution or any way to bypass it ?
Thanks
> Maven3 with 'builds' directory in a separate location tries to create folders
> with colons in the module name which is not allowed on windows.
> -
>
> Key: JENKINS-12251
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12251
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Windows Server 2008 R2 64bit
> Java 1.6.0_26
> Winstone (windows install)
> Jenkins 1.444
>Reporter: Samuel Webber
> Labels: build, exception, jenkins, maven, windows
>
> We are using Jenkins on windows and set our workspaces and builds to be a
> separate directory to the standard jenkins install directory on windows.
> This all works fine for our ant builds with our build artefacts stored in
> U:\jenkins\builds
> However we have recently added some maven3 builds.
> These work fine if you have the Build Record Root Directory set to the
> default as: ${ITEM_ROOTDIR}/builds
> And the build folders exists as: C:\Program Files (x86)\Jenkins\jobs\ name>\modules\$
> However changing the Build Record Root Directory to
> u:/jenkins/builds/${ITEM_FULLNAME} it then tries to create the directory with
> a colon rather than a dollar in the directory name, this fails on windows.
> e.g.
> u:\jenkins\builds\\:
> I can confirm running jenkins on linux the same occurs, however the colon is
> not a problem (as its an allowed character).
> Started by user Sam Webber
> Building on master
> Updating
> http://svnserver/svn/ss/platform/branches/wc/wc_maven_migration/core/ss-core
> At revision 181408
> no revision recorded for
> http://svnserver/svn/ss/platform/branches/wc/wc_maven_migration/core/ss-core
> in the previous build
> Parsing POMs
> Modules changed, recalculating dependency graph
> ERROR: Failed to parse POMs
> java.io.FileNotFoundException:
> u:\jenkins\builds\wc.ss-core\com.ss:ss-core\2011-12-23_19-09-32\log (The
> filename, directory name, or volume label syntax is incorrect)
> at java.io.FileOutputStream.open(Native Method)
> at java.io.FileOutputStream.(Unknown Source)
> at java.io.FileOutputStream.(Unknown Source)
> at hudson.maven.MavenBuild$ProxyImpl2.(MavenBuild.java:474)
> at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:686)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:462)
> at hudson.model.Run.run(Run.java:1404)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:238)
> FATAL: Failed to create a temporary file in
> u:\jenkins\builds\wc.ss-core\com.ss:ss-core\2011-12-23_19-09-32
> hudson.util.IOException2: Failed to create a temporary file in
> u:\jenkins\builds\wc.ss-core\com.ss:ss-core\2011-12-23_19-09-32
> at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:67)
> at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:54)
> at hudson.XmlFile.write(XmlFile.java:170)
> at hudson.model.Run.save(Run.java:1540)
> at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.post2(MavenModuleSetBuild.java:1011)
> at
> hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614)
> at hudson.model.Run.run(Run.java:1429)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:238)
> Caused by: java.io.IOException: The filename, directory name, or volume label
> syntax is incorrect
> at java.io.WinNTFileSystem.createFileExclusively(Native Method)
> at java.io.File.checkAndCreate(Unknown Source)
> at java.io.File.createTempFile(Unknown Source)
> at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:65)
> ... 9 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
