[JIRA] [subversion] (JENKINS-24377) Create Tag (Tag this build) Not working
Damon Overboe commented on JENKINS-24377 Create Tag (Tag this build) Not working It does exist on both. I was using 1.575 and was following the advice to not upgrade unless you see a bug. Then, I upgraded to 1.576 and it still exists. I've been able to work around it for now by installing the SVN Tag plugin; my best guess is it's an issue with not liking the url that's forced on us by VisualSVN http:/path-to-server/svn/yourreponame because I saw some behavior with it that appeared to think that http:/path-to-server/svn/ was the actual repo, whereas that's actually nothing; a web browser will list all of the available repos under that, but clients (command line, TortoiseSVN, SmartSVN) will throw an error. I'm trying to figure out how to prove that out; I think what I can probably do is test using the tagger against the archives, which are NOT served by VisualSVN, and compare that behavior against the live ones which are served by it. 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] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working
Damon Overboe created JENKINS-24377 CLONE - Create Tag (Tag this build) Not working Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: svn-tag Created: 21/Aug/14 5:11 PM Description: Hudson version 1.227. Stand alone setup running on Winstone. When attempting a tag after selecting 'Tag this build', the tag fails with an error: Tagging http://subversion/svn/X/web/project/trunk (rev.19085) to http://subversion/svn/X/web/project/tags/project-30 Failed to tag org.tmatesoft.svn.core.SVNAuthenticationException: svn: Commit failed (details follow): svn: CHECKOUT of '/svn/X/!svn/ver/19211/web/project/tags': 403 Forbidden (http://subversion) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:84) at org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:354) at hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:167) at hudson.model.TaskThread.run(TaskThread.java:77) Completed The error suggests the user setup within the hudson.scm.SubversionSCM.xml does not have the authority to checkout the subversion tags directory revision. Further investigation found the user being used for the tag is the user that started Hudson in the first instance, and NOT the user declared in the hudson.scm.SubversionSCM.xml file. Thus, if the user account that started Hudson does not have enough permissions for SVN, then the tagging fails with the above error. Regards Matt Gaunt Environment: Platform: All, OS: HP-UX Project: Jenkins Priority: Major Reporter: Damon Overboe 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] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working
Damon Overboe updated JENKINS-24377 CLONE - Create Tag (Tag this build) Not working Change By: Damon Overboe (21/Aug/14 5:21 PM) Fix Version/s: current Environment: Platform:All,OS: HP-UX WIndowsServer2012 Description: Thisisacloneoftheoriginalbug,whenWhenattemptingatagafterselectingTagthisbuild,thetagfails.Generally,itfailssilently,notpumpinganyinformationtotheUIoreventheeventlogs(evenwiththehudsonSubversionSCMlogsettofineorhigher).Iwasabletogetittopumponefailuremessage,butIwasnotabletocaptureit.IamrestartingtheVMtoseeifitwillpumpthemessageagain.IcanrecreateitusingJenkins1.575or1.576onWindowsServer2012,usingthelatestoftheSubversionplugin.Originalmeessage: Hudsonversion1.227.StandalonesetuprunningonWinstone. WhenattemptingatagafterselectingTagthisbuild,thetagfailswithanerror: Tagginghttp://subversion/svn/X/web/project/trunk(rev.19085)to http://subversion/svn/X/web/project/tags/project-30 Failedtotag org.tmatesoft.svn.core.SVNAuthenticationException:svn:Commitfailed(details follow): svn:CHECKOUTof/svn/X/!svn/ver/19211/web/project/tags:403Forbidden (http://subversion) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:84) atorg.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:354) at hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:167) athudson.model.TaskThread.run(TaskThread.java:77) Completed Theerrorsuggeststheusersetupwithinthehudson.scm.SubversionSCM.xmldoes nothavetheauthoritytocheckoutthesubversiontagsdirectoryrevision. Furtherinvestigationfoundtheuserbeingusedforthetagistheuserthat startedHudsoninthefirstinstance,andNOTtheuserdeclaredinthe hudson.scm.SubversionSCM.xmlfile.Thus,iftheuseraccountthatstartedHudson doesnothaveenoughpermissionsforSVN,thenthetaggingfailswiththeabove error. Regards MattGaunt 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] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working
Damon Overboe updated JENKINS-24377 CLONE - Create Tag (Tag this build) Not working Change By: Damon Overboe (21/Aug/14 5:30 PM) Description: Thisisacloneoftheoriginalbug,whenWhenattemptingatagafterselectingTagthisbuild,thetagfails. Generally,itfailssilently,notpumpinganyinformation Thisisalsorelated to theUIoreventheeventlogs(evenwiththehudsonSubversionSCMlogsettofineorhigher) https://issues . jenkins-ci.org/browse/JENKINS-21797,butIhaveeliminatedthat. Iwasabletogetittopumponefailuremessage,butIwasnotabletocaptureit.IamrestartingtheVMtoseeifitwillpumpthemessageagain. Generally,itfailssilently,notpumpinganyinformationtotheUIoreventheeventlogs(evenwiththehudson.scm.SubversionSCMlogsettofineorhigher). IcanrecreateitusingJenkins1.575or1.576onWindowsServer2012,usingthelatestoftheSubversionplugin .Originalmeessage:Hudson ,withaworkingcopyof version1. 227 7 . StandalonesetuprunningonWinstone. Whenattempting TheSVNserverisSmartSVNhostedon a tagafterselectingTagthisbuild, Windows2012server.Ithas the tagfailswithanerror:Tagginghttp: non-configurableconventionofrequiringserverpath / /subversion/ svn/ X/web/project/trunk(rev.19085) beforeyourreponame,andonthelogIfailed to http: capture,Isawitcomplainabout / /subversion/ svn/ X/web/project/tags/project-30 myreponameonthecopy. Failedtotagorg ThereisonlyoneuserspecifiedintheJenkinscredentialsforSVN,andtheyhavetaggingprivileges . tmatesoft.svn.core.SVNAuthenticationException:svn:Commitfailed(details follow): svn AndItriedtheworkaroundfromasimilarbug,whereyou : CHECKOUTof/svn/X/!svn/ver/19211/web/project/tags:403Forbidden (http://subversion) atorg 1 . tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:84) Connecttothetargetmachine atorg 2 . tmatesoft. Run` svn .core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:354) cleanup``svnup`oneachworkspace,specifyingthecredentials athudson Butthathadnoimpactontheresult . scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:167) athudson.model.TaskThread.run(TaskThread.java:77) Completed Theerrorsuggeststheusersetupwithinthe Therearenocredentialsstoredinmy hudson.scm.SubversionSCM.xml does file: nothavetheauthoritytocheckoutthesubversiontagsdirectoryrevision ?xmlversion=1 . 0encoding=UTF-8? FurtherinvestigationfoundtheuserbeingusedforthetagistheuserthatstartedHudsoninthefirstinstance,andNOTtheuserdeclaredinthe hudson.scm. SubversionSCM SubversionSCM_-DescriptorImplplugin=subversion@2 . xmlfile 4 . Thus,iftheuseraccountthatstartedHudson 1 doesnothaveenoughpermissionsforSVN,thenthetaggingfailswiththeabove generation49/generation error. mayHaveLegacyPerJobCredentialsfalse/mayHaveLegacyPerJobCredentials workspaceFormat100/workspaceFormat Regards validateRemoteUpToVarfalse/validateRemoteUpToVar storeAuthToDiskfalse/storeAuthToDisk MattGaunt /hudson.scm.SubversionSCM_-DescriptorImpl 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] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working
Damon Overboe commented on JENKINS-24377 CLONE - Create Tag (Tag this build) Not working I figured cloning the related issue was the right way to go, since that issue was never solved, but was just closed because not enough information was provided to track down the bug? Yeah, I should have started with just a local draft before posting. I'm going to update it with a bit more information if I can get a good log output, but it's failing silently, even with the hudson.scm.SubversionSCM log set to 'All'. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working
Damon Overboe commented on JENKINS-24377 CLONE - Create Tag (Tag this build) Not working It's actually not the SVN Tag plugin, it's just the plain Subversion plugin, using the manual "Tag this build" that you execute on a successful run. It is the same behavior on both version 2.4.1 and and 2.4.3. (The ...scm.xml file from above was before upgrading the plugin) http://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin After restarting the server, I see an error page, but still no log. It simply says: Build #36 Tagging is in progress: Clear Error to Retry I checked the logs before and after clicking the "Clear Error" button and there is nothing for the SCM plugin. 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] [subversion] (JENKINS-24377) Create Tag (Tag this build) Not working
Damon Overboe commented on JENKINS-24377 Create Tag (Tag this build) Not working Steps I took on the logs: 1. In log levels and added hudson.scm.SubversionSCM, setting it to Fine, 2. then tested tagging a successful build. No output. 3. Back in log levels, I bumped it to All, 4. Same result as #2, 5. So I added a new log recorder, set to hudson.scm.SubversionSCM, and level All. 6. Repeated #2, still no output, and the listener in #5 is empty. 7. Rebooted 8. Repeated #2, this time I saw the "Clear Error to Retry" message. 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] [subversion] (JENKINS-24377) Create Tag (Tag this build) Not working
Damon Overboe commented on JENKINS-24377 Create Tag (Tag this build) Not working I'm able to get login failures when adding a new project when I haven't set the credentials yet; those go to both the master log and the SubversionSCM log, but those failures are expected. Also for what it's worth, I have the svnmerge plug-in, version 2.3, to create, update, and integrate feature branches, and that works well. So, I'm going to try disabling as many plugins as I can on a test server to see if one of them is interfering with the Subversion Plugin to rule that 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/d/optout.
[JIRA] [maven2] (JENKINS-6763) Hudson does not set JAVA_HOME for Maven Builds
Damon Overboe edited a comment on JENKINS-6763 Hudson does not set JAVA_HOME for Maven Builds On Jenkins 1.575, working against Windows Server 2012, setting the JDK in Jenkins provides the option to input the JAVA_HOME variable, and that worked around the issue for me. This might be what you were referring to as having it set twice, but given that it seems to completely ignore JAVA_HOME on the clients (even though it reports that correctly with the script console) it doesn't seem to cause any issues. Here were my steps: Manage Jenkins Configure System Scroll to JDK installations Add JDK Installation Provide JAVA_HOME path to the JDK folder on the client/slave such as C:\Progra~2\Java\jdk1.7.0_67 where Proga~2 resolves to Program Files (x86) 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] [maven2] (JENKINS-6763) Hudson does not set JAVA_HOME for Maven Builds
Damon Overboe commented on JENKINS-6763 Hudson does not set JAVA_HOME for Maven Builds On Jenkins 1.575, working against Windows Server 2012, setting the JDK in Jenkins provides the option to input the JAVA_HOME variable, and that worked around the issue for me. This might be what you were referring to as having it set twice, but given that it seems to completely ignore JAVA_HOME on the clients (even though it reports that correctly with the script console) it doesn't seem to cause any issues. Here were my steps: 1. Manage Jenkins 1. Configure System 1. Scroll to JDK installations 1. Add JDK Installation 1. Provide JAVA_HOME path to the JDK folder on the client/slave such as `C:\Progra~2\Java\jdk1.7.0_67` *where Proga~2 is Program Files (x86) 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] [maven2] (JENKINS-6763) Hudson does not set JAVA_HOME for Maven Builds
Damon Overboe edited a comment on JENKINS-6763 Hudson does not set JAVA_HOME for Maven Builds On Jenkins 1.575, working against Windows Server 2012, setting the JDK in Jenkins provides the option to input the JAVA_HOME variable, and that worked around the issue for me. This might be what you were referring to as having it set twice, but given that it seems to completely ignore JAVA_HOME on the clients (even though it reports that correctly with the script console) it doesn't seem to cause any issues. Here were my steps: Manage Jenkins Configure System Scroll to JDK installations Add JDK Installation Provide JAVA_HOME path to the JDK folder on the client/slave such as `C:\Progra~2\Java\jdk1.7.0_67` where Proga~2 is Program Files (x86) 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.
