I think you need not worry about the .svn folders that you observe in your
current setup. You should worry why you did not note them in the former
setup.
When investigating before/after issues like this, comparison of Jenkins job
logs before and after a modification had been helpful to me in the
You should double check your svn plugin config and the platform you're
checking on as I said.
Also, wondering whether your config is actually using the svn binaries or
javasvn (disclaimer: not sure it's still a thing, I've totally moved away
from even seeing an svn use from inside Jenkins 4+ years
Thanks a lot for your response. PFB the details below.
Server / Software Old New
Jenkins 2.163 2.257
Jenkins Controller Windows Server 2012 R2 Ubuntu 18.04.3
Jenkins Agent Windows Server 2019 Standard Windows Server 2019 Standard
SVN Version 1.6.2 1.6.2
Regards,
Venkatesh
On Sat, Dec 26, 2020 a
On Windows or Linux?
On Linux it will require ls -a to show them.
Please check and provide svn versions and OS on various cases.
Or possibly, you've been using 'svn export' in some cases. I don't know.
You're the one best positioned to check 😉
Le sam. 26 déc. 2020 à 17:07, Ven H a écrit :
> I
I am pretty sure, it didn't create those folders in the old instance. We
still have the old instance running since we are in the process of
transitioning. I don't see those folders there. That's why I raised this
query.
Regards,
Venkatesh
On Sat, Dec 26, 2020 at 12:48 AM 'Martin Schmude' via Jen
SVN does not download .svn folders, it creates them while performing a
checkout.
The .svn folders are documented in:
http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.basic.in-action.wc.
With the older Jenkins instance every SVN checkout must have created a .svn
folder too. Maybe you just did
Thank you for your response. SVN version has not changed in our case. Our
controller has changed. It's a newer version of Jenkins. The older version
was hosted on Windows and the newer version is hosted in a Docker container
in a Linux environment.
The checkout step in the pipeline didn't download
Not sure what exactly you're concerned about:
Subversion always had this .svn folder. Since 1.7 it's only at the root of
the checked out repo.
Before svn 1.7 it was literally in all directories.
This is expected.
If you're surprised more by the latter behavior described above, maybe your
agent i
I have a pipeline script in Jenkinsfile which is in SVN. It has the
following checkout step.
*checkout([$class: 'SubversionSCM', filterChangelog: false,
ignoreDirPropChanges: false, locations: [[cancelProcessOnExternalsFail:
true, credentialsId: "", depthOption: 'infinity',
ignoreExternalsOption:
