[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Ruben Perez commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Then your architecture is wrong. It cannot support something fundamentally needed. The sooner you change it, the better. This project goes nowhere without this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-15681) Support for Cloudbees Folders
Ruben Perez commented on JENKINS-15681 Support for Cloudbees Folders Yes, sure. It looks something like: C:\Program Files\Jenkins\jobs\folder1\ ... config.xml ... jobs\folder2\ . config.xml . jobs\Normal Jenkins Task1\ . jobs\Normal Jenkins Task2\ (Sorry for the formatting, I don't have time to waste it with this wiki) If you have anything and you want to test it you can send it to me. 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-15681) Support for Cloudbees Folders
Ruben Perez created JENKINS-15681 Support for Cloudbees Folders Issue Type: Improvement Assignee: Thomas Fürer Components: thinBackup Created: 31/Oct/12 11:43 AM Description: The plugin is not doing the backup of jobs contained in Cloudbees folders, but it seems to be detecting them on the logs: Oct 31, 2012 12:23:21 PM org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobs INFO: Found 5 jobs to back up. Project: Jenkins Priority: Major Reporter: Ruben Perez 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-10628) SCM build trigger not working correctly with variables in SVN URL
Ruben Perez commented on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Ok, I'm completely updated and I'm still having problems with variables in the SVN url... The interface is not recognizing that I entered a variable and is always showing problem and I can't enter my username and password (I have to specify it on the URL). Also, I'm having an exception like: INFO: Failed to access subversion repository ${SVNPATH} org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '${SVNPATH}' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.SVNURL.init(SVNURL.java:221) at org.tmatesoft.svn.core.SVNURL.parseURIDecoded(SVNURL.java:113) at hudson.scm.SubversionSCM$DescriptorImpl.doCheckRevisionPropertiesSupported(SubversionSCM.java:2201) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) This is basic stuff for managing different branches and so on Please fix 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
[JIRA] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Ruben Perez edited a comment on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Ok, I'm completely updated and I'm still having problems with variables in the SVN url... The interface is not recognizing that I entered a variable and is always showing problem and I can't enter my username and password (I have to specify it on the URL). Also, I'm having an exception like: INFO: Failed to access subversion repository ${SVNPATH} org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '${SVNPATH}' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.SVNURL.init(SVNURL.java:221) at org.tmatesoft.svn.core.SVNURL.parseURIDecoded(SVNURL.java:113) at hudson.scm.SubversionSCM$DescriptorImpl.doCheckRevisionPropertiesSupported(SubversionSCM.java:2201) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) This is basic stuff for managing different branches and so on Please fix 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