[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Thomas we ended up excluding the build folders from our backups. Would like to see this resolved and be able to do a complete Jenkins backup. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen updated JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Change By: Joe Knudsen (17/Sep/14 1:25 PM) Description: After upgrading to 1.509.4 our Maven builds create files that Windows cannot backup. The UI seems to working. The invalid files are SYMLINKD one for each module.The none maven builds build and UI seem to work fine. The files are under the jobs/project name/builds/buildnumber or builddate directory.11/19/2013 04:47 PM us.mn.state.education.sfin.automation$sfin-post-processor [../../modules/us.mn.state.education.sfin.automation$sfin-post-processor/builds/2013-11-19_16-40-46] 4 File(s) 3,881,255 bytes 34 Dir(s) 20,236,365,824 bytes freeE:\jenkins\.jenkins\jobs\SFIN-OB\builds\56>type us.mn.state.education.sfin$configsAccess is denied.E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56>cd us.mn.state.education.sfin$configsThe filename, directory name, or volume label syntax is incorrect.E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56> This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen edited a comment on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Jesse it is not the build number links that are problematic. The Maven build includes a section called Module Builds. The plugin seems to create a link for each Module. These module links are the problem. The Windows OS does not see the links as valid. I believe the links contain a path and the path uses the wrong path separator for Windows. I do not see any impacts in the Jenkins UI. I Jenkins is not impacted because Jenkins uses Java and Java can handle either Windows or Unix file separators. The problem is the Windows OS and backup software see these as corrupted files. Hope this helps. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Jesse it is not the build number links. The Maven build includes a section called Module Builds. The plugin seems to create a link for each Module. These module links are 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen edited a comment on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Tim, Looks like you have the latest plugin. After grading from 1.509 I needed to add to a maven property. Global MAVEN_OPTS I made mine have the value -XX:MaxPermSize=256m and that resolved by problem. Worth giving a try at least. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Were still seeing the problem so I edited my comments above to remove the references about not seeing the problem any longer. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen edited a comment on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Tim what version of the Maven plugin are you using? I am using 2.0.1 now with Jenkins 1.532.2 and the problem still exists. Now in the 1.532.2 (latest stable) version the maven plugin is separate from the Jenkins system so you need to update the maven plugin after you update 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Tim, After grading from 1.509 I needed to add to a maven property. Global MAVEN_OPTS I made mine have the value -XX:MaxPermSize=256m and that resolved by problem. The error message looks familiar so you might be having the same problem. Worth giving a try at least. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen edited a comment on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Tim what version of the Maven plugin are you using? I am using 2.0.1 now with Jenkins 1.532.2 and the problem seems to have resolved. Now in the 1.532.2 (latest stable) version the maven plugin is separate from the Jenkins system so you need to update the maven plugin after you update 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Tim what version of the Maven plugin are you using? I am using 2.0.1 now and the problem seems to have resolved. Now the maven plugin is separate from the Jenkins system. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen edited a comment on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Tim what version of the Maven plugin are you using? I am using 2.0.1 now with Jenkins 1.532.2 and the problem seems to have resolved. Now in the 1.532.2 version the maven plugin is separate from the Jenkins system. This message is automatically generated by JIRA. 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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Tried upgrading to the latest stable build 1.532.1 and the problem still exsists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Joe Knudsen commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows Josh, Are you seeing this for a Maven build or in other areas. Take a look at the issue JENKINS-20725 and vote that up if that is what your also experiencing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Joe Knudsen commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows See issue JENKINS-20725 for an issue with the Maven Plugin that still exists in 1.509.4 This message is automatically generated by JIRA. 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] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen updated JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Change By: Joe Knudsen (18/Dec/13 3:58 PM) Affects Version/s: current This message is automatically generated by JIRA. 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] [maven2] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen updated JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Change By: Joe Knudsen (26/Nov/13 8:24 PM) Summary: maven build creates symlinkd files that Windows cannot backup OS does not understand This message is automatically generated by JIRA. 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] [maven2] (JENKINS-20725) maven build creates files that Windows cannot backup
Joe Knudsen commented on JENKINS-20725 maven build creates files that Windows cannot backup After looking closer I see that the slashes are Unix forward slashes in for the path to the symbolic link. Two directories above is a SYMLINK for lastStable and that uses the back slashes. I am guessing the Maven plugin needs to start using the forward slashes on Windows. I did check and the files exist if I use the back slashes. This message is automatically generated by JIRA. 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] [maven2] (JENKINS-20725) maven build creates files that Windows cannot backup
Joe Knudsen created JENKINS-20725 maven build creates files that Windows cannot backup Issue Type: Bug Assignee: Unassigned Components: maven2 Created: 22/Nov/13 2:46 PM Description: After upgrading to 1.509.4 our Maven builds create files that Windows cannot backup. The UI seems to working. The files are SYMLINKD one for each module. The none maven builds seem fine. The files are under the jobs/project name/builds/buildnumber or builddate directory. 11/19/2013 04:47 PM us.mn.state.education.sfin.automation$sfi n-post-processor [../../modules/us.mn.state.education.sfin.automation$sfin-post- processor/builds/2013-11-19_16-40-46] 4 File(s) 3,881,255 bytes 34 Dir(s) 20,236,365,824 bytes free E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56>type us.mn.state.education.sfin$confi gs Access is denied. E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56>cd us.mn.state.education.sfin$configs The filename, directory name, or volume label syntax is incorrect. E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56> Environment: Windows 2008 R2 Jenkins 1.509.4 Project: Jenkins Priority: Major Reporter: Joe Knudsen This message is automatically generated by JIRA. 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] [maven] (JENKINS-18072) Mavem module symlinks in builds history are invalid under Windows 7
Joe Knudsen edited a comment on JENKINS-18072 Mavem module symlinks in builds history are invalid under Windows 7 Still having this problem with Maven on 1.509.4 I am using Window Server 2008 R2. Seems like a new feature in Maven to add Module Builds time is causing this. The files include a $ symbol which in Windows has a special meaning. This message is automatically generated by JIRA. 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] [maven] (JENKINS-18072) Mavem module symlinks in builds history are invalid under Windows 7
Joe Knudsen reopened JENKINS-18072 Mavem module symlinks in builds history are invalid under Windows 7 Still having this problem with Maven on 1.509.4 Change By: Joe Knudsen (21/Nov/13 9:11 PM) Resolution: Duplicate 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] [maven] (JENKINS-19398) Maven jobs not loaded on 1.529 - Could not initialize class hudson.maven.MavenModuleSet
Joe Knudsen commented on JENKINS-19398 Maven jobs not loaded on 1.529 - Could not initialize class hudson.maven.MavenModuleSet Me too needed to enable JavaDoc plugin after upgrading from 1.480.3 to 1.509.4 This message is automatically generated by JIRA. 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] [active-directory] (JENKINS-13058) E-mail to individuals who broke the build is sent to wrong address
Joe Knudsen commented on JENKINS-13058 E-mail to individuals who broke the build is sent to wrong address This is happening at our Jenkins version 1.480.3 with the Active Directory plugin 1.30 and the Subversion Plugin 1.45. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Joe Knudsen commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 Thanks. I copied the default.json from one of my other jenkins servers and now I am getting a lists of plugins again. Thanks for the workaround. Hoping for a better long term resolution to follow. This message is automatically generated by JIRA. 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] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Joe Knudsen commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 Well having the problem on Linux and Windows at least rules out the OS patches. I also see the error on an existing machine if you look in the jenkins.err file. The DB must retain the updates from past successes and since no error is shown on the UI this could be having a larger impact then just new installs. This message is automatically generated by JIRA. 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] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Joe Knudsen commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 Mark, I tried these 3 sites directly and still no updates and the same error message in jenkins.err file. Thanks, Joe This message is automatically generated by JIRA. 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] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Joe Knudsen edited a comment on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 I am seeing the same on a Windows Server 2008 R2 x64. I installed this same war on a Windows Server 2008 R2 x64 a couple of weeks ago without an issue. Now I am getting this error on that system also. I have tried using the mirror sites directly with no success either. This message is automatically generated by JIRA. 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] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Joe Knudsen commented on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 I am seeing the same on a Windows Server 2008 R2 x64. I installed this same war on a Windows Server 2008 R2 x64 a couple of ago without an 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] [plugin] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3
Joe Knudsen edited a comment on JENKINS-17677 Digest mismatch in update center for LTS 1.480.3 I am seeing the same on a Windows Server 2008 R2 x64. I installed this same war on a Windows Server 2008 R2 x64 a couple of weeks ago without an 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.
