Can anyone suggest how to fix the two issues?
- Can't upgrade Jenkins and SVN plugin
- Can't connect to svn
I am setting up Jenkins on a Windows 64 bit machine. It's configured to run as a windows service.
We are running this on Windows 7 64 bit OS
Jenkins 1.482
I am able to do an SVN update/checkout from my user account on the machine.
When I attempt to set up a job on jenkins I get the following when trying to add svn credentials
FAILED: org.tmatesoft.svn.core.SVNErrorMessage: svn: OPTIONS /svn/client/trunk failed
More details are:
FAILED: org.tmatesoft.svn.core.SVNErrorMessage: svn: OPTIONS /svn/client/trunk failed
org.tmatesoft.svn.core.SVNException: svn: OPTIONS /svn/client/trunk failed
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271)
at ...
I stopped the service and ran Jenkins from command line and tried the same thing - with the same result.
I am able to connect to the svn server with a tortoise client and via firefox with the same credentials.
In researching the issue I saw a few posts about similar problems and the only one that seems to claim to fix it is rolling back to Jenkins svn plugin version.
I then tried to install the latest jenkins and Plugin for svn. The downloads failed. Aha, I thought - obviously a firewall issue. So I disable the firewall.
Still no good. I can't automatically download or get the new Jenkins or SVN plugin.
Try starting jenkins with this option:
-Dsvnkit.http.sslProtocols="SSLv3"
Or, if Jenkins is starting svn plugin in a separate JVM, try adding the line to wherever the svn plugin run configuration is.
It's a known problem with svnkit, which is used by Jenkins' svn plugin:
http://issues.tmatesoft.com/issue/SVNKIT-176
Also, this answer can be helpful with regards to upgrading your svn plugin.
To change your Windows service commandline:
open a command line window cmd.exe
sc qc "JenkinsSlave" (if that's what your service name is)
select and copy the BINARY_PATH_NAME value
change it, adding -Dsvnkit.http.sslProtocols=""SSLv3"" after the jar path - mind the double quote
sc config "JenkinsSlave" binPath= <paste the changed value copied earlier>
Replace JenkinsSlave with your service name.
Windows 7 x64 has some automatic firewall settings. You may need to open a firewall port to allow the connection.
You should be able to verify or eliminate this as a cause by trying to run your svn client outside Jenkins.
bit late topic, but did you try the following solution?
http://www.daangemist.nl/2014/03/03/jenkins-reports-sslv3-error-on-svn-update
that one worked out for me, in my case I wanted to use -Dsvnkit.http.sslProtocols="TLSv1"
What about running Jenkins service with your account?
Related
I have jenkins job which is checking out the code from SVN repository and run the build but I am getting the multiple or different errors before its checking out the complete code.Please help me.
Error:
ERROR 1: svn: E155021: The path 'D:\Jenkins\workspace\Project1\branch-1.1' appears to be part of a Subversion 1.7 or greater
working copy. Please upgrade your Subversion client to use this
working copy.
org.tmatesoft.svn.core.SVNException: svn: E155021: The path 'D:\Jenkins\workspace\Project\branch-1.1' appears to be part of a Subversion 1.7 or greater
working copy. Please upgrade your Subversion client to use this
working copy.
Error 2:
D:\jenkins\workspace\project\branch.svn\wc.db: The process cannot access the file because it is being used by another process.
Please install Tortoise SVN (It has the cli interface) and add to Windows %PATH%.
Recently i have upgraded Jenkins from v1.596.2 to 2.32.3(LTS). But after upgradation i am getting following error but no clear how to rectify it.
=========================================================================
Tomcat Deploy v1.0.16
You must update Jenkins from v2.32.3 to v3.0.0 or later to run this plugin.
Ok so I had the same problem (but with others plugins).
To fix that:
Put Jenkins in "Prepare for Shutdown" mode and shutdown it
On the server HDD go to JENKINS_HOME/plugins and delete (or move elsewhere) the folder and hpi file corresponding to plugin which produce warnings. (The name of file/folder can be a little bit different than the plugin name displayed in Jenkins)
Restart Jenkins. Warning should be deleted
I am using svn Export command as a pre-build step (Execute windows batch command) in jenkins job.
The link I am exporting has a several external links from same SVN repo.
During execution I have observed that from command line some external links are not accessible but it accessible through internet explorer or through SVN browser. (I am using tortoise as a client)
Is there any provision in the SVN command line so that I can add retry count in case of connection failure.
Note: I am not using Jenkins subversion plugin as I want to export the SVN link and do not want checkout.
Please help.
Thank you in advance.
Neither the svn command line client nor the TortoiseSVN equivalent have this functionality. Instead, write your own wrapper to check the client's output for errors and retry on failure (and have an upper bound on the number of retries so you don't get stuck in a loop forever).
If you're automating with no user interaction, you should be using svn.exe, not tortoiseproc.exe. Or better yet, a client library for the scripting/programming environment of your choice (SharpSVN, SVNKit SVN::Client, pysvn, etc.).
I've upgraded the OS and the Jenkins that was running on it from Windows XP and an ancient version of Jenkins (installed in 2012). So now I'm on Windows 7 and Jenkins 2.19.1 (the latest at time of writing). Other than that, the only different is that I do not have a jenkins user, and it's running as a service instead of locally on the desktop.
I need to update a repository that is outside my Jenkins workspace. Let's call is C:\Repos\Operations. Doing an hg pull -u in a windows batch command and I get this:
C:\Repos\Operations>hg pull --debug -u
using https://xxx.kilnhg.com/Code/Repositories/Operations
sending capabilities command
xxx.kilnhg.com certificate successfully verified
abort: http authorization required for https://xxx.kilnhg.com/Code/Repositories/Operations
It works fine if I do it in the cmd.exe. I've been searching for hours for an answer. Using hg showconfig --debug the only difference between doing it in the cmd and having hg showconfig --debug in the jenkins windows batch command is the following 2 lines:
read config from: C:\Windows\system32\config\systemprofile\mercurial.ini
read config from: C:\Windows\system32\config\systemprofile\.hgrc
But those files do not exist on my system. So, in theory, it should be reading everything from the same settings location, but it's not.
Does someone have any idea?
Thanks!
Can't comment yet, so this goes under 'Answer': per your comment it does not find the correct '.hgrc' file. Have you tried providing the username/password in the batch command, like here Mercurial (HG) pull parameters: username and password ?
I have been assigned a task to do build automation using jenkins which should perform checkout, compile & build automatically.
Existing set up - Currently we have PVCS installed in one of our AIX server where build process(checkout,compile,build) is automated using ant script.
I have installed jenkins in my windows server.
How do i get the code into my windows server from PVCS which resides in AIX server to perform build through jenkins.
Thanks in advance.
As I posted on CodeRanch where you posted the same question, you need to install the PVCS plugin for Jenkins.