Daniel:
I guess you are my first customer, congratulations :-)
I have no immediate answer, but I will look into this.
What is your os, java/jenkins version?
Thank you,
Andrei
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/V9W3sagC5Zg/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Andrei,
Hi Andrei,
Ok, it must just be my version then. I'm running Jenkins 1.480.2, and the JVM is "JRE 1.6.0 IBM J9 2.4 Linux amd64-64". For some reason, it doesn't want to get the latest from the update server.
I looked at the code, and unfortunately won't be able to write the SVN section. I have no idea what's going on in there.
Would you say that to get SVN working, one would have to make a superclass for PluginScmGit and PluginScmSvn, replicate the functionality of the Git version in the Svn version (using SVNKit, for example), and rewrite PluginScm to use the superclass?
Just want to get an idea of what would be required, in case someone with more skill is interested in writing it...
is the SCM code separated enough that one would only need to work on that section?
Andrei.
Regards,
Daniel
Ok, it must just be my version then. I'm running Jenkins 1.480.2, and the JVM is "JRE 1.6.0 IBM J9 2.4 Linux amd64-64". For some reason, it doesn't want to get the latest from the update server.
Ok, it must just be my version then. I'm running Jenkins 1.480.2, and the JVM is "JRE 1.6.0 IBM J9 2.4 Linux amd64-64". For some reason, it doesn't want to get the latest from the update server.