AUTO: Martin Schoepf is out of the office (returning 03.19.2013)
I am out of the office until 03.19.2013. Note: This is an automated response to your message Fwd: Delivery Status Notification (Failure) sent on 3/14/2013 12:15:47. This is the only notification you will receive while this person is away. -- 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.
AUTO: Martin Schoepf is out of the office (returning 10.08.2012)
I am out of the office until 10.08.2012. Note: This is an automated response to your message [JIRA] (JENKINS-11285) Ability to run postbuild script on a given node sent on 9/24/2012 1:26:49. This is the only notification you will receive while this person is away.
REMOVE ME
Martin Schoepf - Software Testing
TTTech Computertechnik AG - Ensuring Reliable Networks
Commercial Reg. No.: 165 664z, Commercial Court Vienna
Schoenbrunner Strasse 7, A-1040 Vienna, Austria
Phone: +43 1 585 34 34-46, Fax: +43 1 585 34 34-90
martin.scho...@tttech.com, http://www.tttech.com
___
From:
l...@yomolo.com (JIRA) nore...@jenkins-ci.org
To:
jenkinsci-issues@googlegroups.com
Date:
08.03.2012 15:34
Subject:
[JIRA] (JENKINS-10628) SCM build trigger not working correctly with
variables in SVN URL
Sent by:
jenkinsci-issues@googlegroups.com
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
CONFIDENTIALITY: The contents of this e-mail are confidential and
intended only for the above addressee(s). If you are not the intended
recipient, or the person responsible for delivering it to the intended
recipient, copying or delivering it to anyone else or using it in any
unauthorized manner is prohibited and may be unlawful. If you
receive this e-mail by mistake, please notify the sender and the
systems administrator at straym...@tttech.com immediately.
UNSUBSCRIBE
Martin Schoepf - Software Testing TTTech Computertechnik AG - Ensuring Reliable Networks Commercial Reg. No.: 165 664z, Commercial Court Vienna Schoenbrunner Strasse 7, A-1040 Vienna, Austria Phone: +43 1 585 34 34-46, Fax: +43 1 585 34 34-90 martin.scho...@tttech.com, http://www.tttech.com ___ CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straym...@tttech.com immediately.
REMOVE ME
Martin Schoepf - Software Testing TTTech Computertechnik AG - Ensuring Reliable Networks Commercial Reg. No.: 165 664z, Commercial Court Vienna Schoenbrunner Strasse 7, A-1040 Vienna, Austria Phone: +43 1 585 34 34-46, Fax: +43 1 585 34 34-90 martin.scho...@tttech.com, http://www.tttech.com ___ From: hits...@gmail.com (JIRA) nore...@jenkins-ci.org To: jenkinsci-issues@googlegroups.com Date: 05.30.2012 09:22 Subject: [JIRA] (JENKINS-13836) Stable release issues|Loading All Build History Fails in stable release 1.447.1 Sent by: jenkinsci-issues@googlegroups.com [ https://issues.jenkins-ci.org/browse/JENKINS-13836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163311#comment-163311 ] hiteswar kumar commented on JENKINS-13836: -- this issue fixed in Jenkins 1.459 (2012/04/09) and will be fixed at Jenkins coming LTS 1.447.2 Reference: http://jenkins-ci.org/changelog Loading All Build History Fails. (issue 13238) https://issues.jenkins-ci.org/browse/JENKINS-13238 Stable release issues|Loading All Build History Fails in stable release 1.447.1 --- Key: JENKINS-13836 URL: https://issues.jenkins-ci.org/browse/JENKINS-13836 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Prodution Reporter: Arvind Ramalingam Priority: Blocker Hi I have upgraded my Production Jenkins to 1.447.1 and I am not able to see my build history.When I try to view more of my build history I get the below error.Please let me know which stable release should i revert back to and I was at 1.409 and everything was fine. HTTP Status 404 - type Status report message description The requested resource () is not available. Apache Tomcat/6.0.26 -- 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 CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straym...@tttech.com immediately.
REMOVE ME
Martin Schoepf - Software Testing TTTech Computertechnik AG - Ensuring Reliable Networks Commercial Reg. No.: 165 664z, Commercial Court Vienna Schoenbrunner Strasse 7, A-1040 Vienna, Austria Phone: +43 1 585 34 34-46, Fax: +43 1 585 34 34-90 martin.scho...@tttech.com, http://www.tttech.com ___ From: lst...@gmail.com (JIRA) nore...@jenkins-ci.org To: jenkinsci-issues@googlegroups.com Date: 05.09.2012 05:08 Subject: [JIRA] (JENKINS-9679) NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option Sent by: jenkinsci-issues@googlegroups.com [ https://issues.jenkins-ci.org/browse/JENKINS-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162591#comment-162591 ] Liam Staskawicz commented on JENKINS-9679: -- Would love to see this addressed or elevated in priority - this is a critical component of putting together a master/slave cluster, and has been known for just about a year now. I say this without being able to fix it myself of course :) but this would be a great help to people setting up multi configuration systems. NoClassDefFoundError on Base64 when launching an headless slave with -jnlpCredential option --- Key: JENKINS-9679 URL: https://issues.jenkins-ci.org/browse/JENKINS-9679 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Jenkins 1.411 / MacOS X / JDK 1.6.0_24 Jenkins 1.412 / Master: Ubuntu 10.04, / Slave: Windows Server 2008 x64, JDK 1.6.0_20 Jenkins 1.424.2 / Master: CentOS 5.5, / Slave: Windows Server 2008 R2 x64, JDK 1.6.0_21 Reporter: Olivier Mansion When launching a headless slave, a NoClassDefFoundError on org/apache/commons/codec/binary/Base64 is raised when specifying the -jnlpCredential option: $ java -jar slave.jar -jnlpUrl url -jnlpCredentials user:password Exception in thread main java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64 at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:221) at hudson.remoting.Launcher.run(Launcher.java:192) at hudson.remoting.Launcher.main(Launcher.java:168) Caused by: java.lang.ClassNotFoundException: org.apache.commons.codec.binary.Base64 at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 3 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 CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straym...@tttech.com immediately.
