.svn folder getting checked out

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

.svn folder getting checked out

Ven H
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: "<SVN_credentials>", depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "<Source_URL>"]], quietOperation: true, workspaceUpdater: [$class: 'UpdateUpdater']])

This is working fine in a Jenkins environment (master & slaves)  on Windows. Now we are moving to a Jenkins master on a Docker container hosted in a Linux environment. The slaves are still Windows servers since the Application code is in .Net. 

The Source code is in SVN. After moving to the new Jenkins instance, we are facing a weird issue. The checkout step is somehow getting .svn folders also downloaded into the workspace, which was not happening in the earlier Jenkins environment. Not sure what is wrong. Can anyone please help?

Regards,
Venkatesh

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: .svn folder getting checked out

Baptiste MATHUS
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 is having a pre-1.7 svn binaries?

PS : we don't use the term 'slave' anymore for agents since 2016. And master got replaced by controller earlier this year.
Thanks.


Le jeu. 24 déc. 2020 à 19:27, Ven H <[hidden email]> a écrit :
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: "<SVN_credentials>", depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "<Source_URL>"]], quietOperation: true, workspaceUpdater: [$class: 'UpdateUpdater']])

This is working fine in a Jenkins environment (master & slaves)  on Windows. Now we are moving to a Jenkins master on a Docker container hosted in a Linux environment. The slaves are still Windows servers since the Application code is in .Net. 

The Source code is in SVN. After moving to the new Jenkins instance, we are facing a weird issue. The checkout step is somehow getting .svn folders also downloaded into the workspace, which was not happening in the earlier Jenkins environment. Not sure what is wrong. Can anyone please help?

Regards,
Venkatesh

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS70dOJALP9zbO-ph5RpFm8Ua-17zaKvnRkjS0UyQ58k-A%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: .svn folder getting checked out

Ven H
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 the .svn folders in the earlier (or older) Jenkins instance, whereas it is doing it in the newer Jenkins instance. SVN has not changed at all. Hope I have explained the problem statement correctly.

Regards,
Venkatesh


On Fri, Dec 25, 2020 at 6:23 PM Baptiste Mathus <[hidden email]> wrote:
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 is having a pre-1.7 svn binaries?

PS : we don't use the term 'slave' anymore for agents since 2016. And master got replaced by controller earlier this year.
Thanks.


Le jeu. 24 déc. 2020 à 19:27, Ven H <[hidden email]> a écrit :
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: "<SVN_credentials>", depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "<Source_URL>"]], quietOperation: true, workspaceUpdater: [$class: 'UpdateUpdater']])

This is working fine in a Jenkins environment (master & slaves)  on Windows. Now we are moving to a Jenkins master on a Docker container hosted in a Linux environment. The slaves are still Windows servers since the Application code is in .Net. 

The Source code is in SVN. After moving to the new Jenkins instance, we are facing a weird issue. The checkout step is somehow getting .svn folders also downloaded into the workspace, which was not happening in the earlier Jenkins environment. Not sure what is wrong. Can anyone please help?

Regards,
Venkatesh

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS70dOJALP9zbO-ph5RpFm8Ua-17zaKvnRkjS0UyQ58k-A%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eomhVDM_m6Gw81mQ1F2F_abxueAn1evMNn%2BLa-royP2uQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: .svn folder getting checked out

Martin Schmude
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 didn't take note of them before the switch to your newer Jenkins instance, for whatever reason.


[hidden email] schrieb am Freitag, 25. Dezember 2020 um 18:57:24 UTC+1:
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 the .svn folders in the earlier (or older) Jenkins instance, whereas it is doing it in the newer Jenkins instance. SVN has not changed at all. Hope I have explained the problem statement correctly.

Regards,
Venkatesh


On Fri, Dec 25, 2020 at 6:23 PM Baptiste Mathus <[hidden email]> wrote:
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 is having a pre-1.7 svn binaries?

PS : we don't use the term 'slave' anymore for agents since 2016. And master got replaced by controller earlier this year.
Thanks.


Le jeu. 24 déc. 2020 à 19:27, Ven H <[hidden email]> a écrit :
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: "<SVN_credentials>", depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "<Source_URL>"]], quietOperation: true, workspaceUpdater: [$class: 'UpdateUpdater']])

This is working fine in a Jenkins environment (master & slaves)  on Windows. Now we are moving to a Jenkins master on a Docker container hosted in a Linux environment. The slaves are still Windows servers since the Application code is in .Net. 

The Source code is in SVN. After moving to the new Jenkins instance, we are facing a weird issue. The checkout step is somehow getting .svn folders also downloaded into the workspace, which was not happening in the earlier Jenkins environment. Not sure what is wrong. Can anyone please help?

Regards,
Venkatesh

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2f7cd4aa-6526-40de-910c-1e9672364cfcn%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: .svn folder getting checked out

Ven H
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 Jenkins Users <[hidden email]> wrote:
SVN does not download .svn folders, it creates them while performing a checkout.
With the older Jenkins instance every SVN checkout must have created a .svn folder too. Maybe you just didn't take note of them before the switch to your newer Jenkins instance, for whatever reason.


[hidden email] schrieb am Freitag, 25. Dezember 2020 um 18:57:24 UTC+1:
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 the .svn folders in the earlier (or older) Jenkins instance, whereas it is doing it in the newer Jenkins instance. SVN has not changed at all. Hope I have explained the problem statement correctly.

Regards,
Venkatesh


On Fri, Dec 25, 2020 at 6:23 PM Baptiste Mathus <[hidden email]> wrote:
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 is having a pre-1.7 svn binaries?

PS : we don't use the term 'slave' anymore for agents since 2016. And master got replaced by controller earlier this year.
Thanks.


Le jeu. 24 déc. 2020 à 19:27, Ven H <[hidden email]> a écrit :
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: "<SVN_credentials>", depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "<Source_URL>"]], quietOperation: true, workspaceUpdater: [$class: 'UpdateUpdater']])

This is working fine in a Jenkins environment (master & slaves)  on Windows. Now we are moving to a Jenkins master on a Docker container hosted in a Linux environment. The slaves are still Windows servers since the Application code is in .Net. 

The Source code is in SVN. After moving to the new Jenkins instance, we are facing a weird issue. The checkout step is somehow getting .svn folders also downloaded into the workspace, which was not happening in the earlier Jenkins environment. Not sure what is wrong. Can anyone please help?

Regards,
Venkatesh

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2f7cd4aa-6526-40de-910c-1e9672364cfcn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eqe8MmjGnQugn9hXk9zKhvxpQ4__--6oOFHP1v1p-WV2g%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: .svn folder getting checked out

Baptiste MATHUS
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 <[hidden email]> a écrit :
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 Jenkins Users <[hidden email]> wrote:
SVN does not download .svn folders, it creates them while performing a checkout.
With the older Jenkins instance every SVN checkout must have created a .svn folder too. Maybe you just didn't take note of them before the switch to your newer Jenkins instance, for whatever reason.


[hidden email] schrieb am Freitag, 25. Dezember 2020 um 18:57:24 UTC+1:
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 the .svn folders in the earlier (or older) Jenkins instance, whereas it is doing it in the newer Jenkins instance. SVN has not changed at all. Hope I have explained the problem statement correctly.

Regards,
Venkatesh


On Fri, Dec 25, 2020 at 6:23 PM Baptiste Mathus <[hidden email]> wrote:
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 is having a pre-1.7 svn binaries?

PS : we don't use the term 'slave' anymore for agents since 2016. And master got replaced by controller earlier this year.
Thanks.


Le jeu. 24 déc. 2020 à 19:27, Ven H <[hidden email]> a écrit :
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: "<SVN_credentials>", depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "<Source_URL>"]], quietOperation: true, workspaceUpdater: [$class: 'UpdateUpdater']])

This is working fine in a Jenkins environment (master & slaves)  on Windows. Now we are moving to a Jenkins master on a Docker container hosted in a Linux environment. The slaves are still Windows servers since the Application code is in .Net. 

The Source code is in SVN. After moving to the new Jenkins instance, we are facing a weird issue. The checkout step is somehow getting .svn folders also downloaded into the workspace, which was not happening in the earlier Jenkins environment. Not sure what is wrong. Can anyone please help?

Regards,
Venkatesh

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2f7cd4aa-6526-40de-910c-1e9672364cfcn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eqe8MmjGnQugn9hXk9zKhvxpQ4__--6oOFHP1v1p-WV2g%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7OhP85_iZAj6OyuWD3bGC5rXvQvoJSRJDrD5btxu2Q%3DQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: .svn folder getting checked out

Ven H
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 at 11:40 PM Baptiste Mathus <[hidden email]> wrote:
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 <[hidden email]> a écrit :
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 Jenkins Users <[hidden email]> wrote:
SVN does not download .svn folders, it creates them while performing a checkout.
With the older Jenkins instance every SVN checkout must have created a .svn folder too. Maybe you just didn't take note of them before the switch to your newer Jenkins instance, for whatever reason.


[hidden email] schrieb am Freitag, 25. Dezember 2020 um 18:57:24 UTC+1:
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 the .svn folders in the earlier (or older) Jenkins instance, whereas it is doing it in the newer Jenkins instance. SVN has not changed at all. Hope I have explained the problem statement correctly.

Regards,
Venkatesh


On Fri, Dec 25, 2020 at 6:23 PM Baptiste Mathus <[hidden email]> wrote:
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 is having a pre-1.7 svn binaries?

PS : we don't use the term 'slave' anymore for agents since 2016. And master got replaced by controller earlier this year.
Thanks.


Le jeu. 24 déc. 2020 à 19:27, Ven H <[hidden email]> a écrit :
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: "<SVN_credentials>", depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "<Source_URL>"]], quietOperation: true, workspaceUpdater: [$class: 'UpdateUpdater']])

This is working fine in a Jenkins environment (master & slaves)  on Windows. Now we are moving to a Jenkins master on a Docker container hosted in a Linux environment. The slaves are still Windows servers since the Application code is in .Net. 

The Source code is in SVN. After moving to the new Jenkins instance, we are facing a weird issue. The checkout step is somehow getting .svn folders also downloaded into the workspace, which was not happening in the earlier Jenkins environment. Not sure what is wrong. Can anyone please help?

Regards,
Venkatesh

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2f7cd4aa-6526-40de-910c-1e9672364cfcn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eqe8MmjGnQugn9hXk9zKhvxpQ4__--6oOFHP1v1p-WV2g%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7OhP85_iZAj6OyuWD3bGC5rXvQvoJSRJDrD5btxu2Q%3DQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28ep_m1uRwusmWNPZiMmzErXWOL0-jtOHBtyVpPX%2B-rRvdg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: .svn folder getting checked out

Baptiste MATHUS
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 ago)

On Linux, ls will *not* show the .svn folders but they're still present.

Given you're using svn pre-1.7 there'll be such a folder in all folders in the local repository.

Cheers

Le lun. 28 déc. 2020 à 08:55, Ven H <[hidden email]> a écrit :
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 at 11:40 PM Baptiste Mathus <[hidden email]> wrote:
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 <[hidden email]> a écrit :
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 Jenkins Users <[hidden email]> wrote:
SVN does not download .svn folders, it creates them while performing a checkout.
With the older Jenkins instance every SVN checkout must have created a .svn folder too. Maybe you just didn't take note of them before the switch to your newer Jenkins instance, for whatever reason.


[hidden email] schrieb am Freitag, 25. Dezember 2020 um 18:57:24 UTC+1:
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 the .svn folders in the earlier (or older) Jenkins instance, whereas it is doing it in the newer Jenkins instance. SVN has not changed at all. Hope I have explained the problem statement correctly.

Regards,
Venkatesh


On Fri, Dec 25, 2020 at 6:23 PM Baptiste Mathus <[hidden email]> wrote:
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 is having a pre-1.7 svn binaries?

PS : we don't use the term 'slave' anymore for agents since 2016. And master got replaced by controller earlier this year.
Thanks.


Le jeu. 24 déc. 2020 à 19:27, Ven H <[hidden email]> a écrit :
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: "<SVN_credentials>", depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "<Source_URL>"]], quietOperation: true, workspaceUpdater: [$class: 'UpdateUpdater']])

This is working fine in a Jenkins environment (master & slaves)  on Windows. Now we are moving to a Jenkins master on a Docker container hosted in a Linux environment. The slaves are still Windows servers since the Application code is in .Net. 

The Source code is in SVN. After moving to the new Jenkins instance, we are facing a weird issue. The checkout step is somehow getting .svn folders also downloaded into the workspace, which was not happening in the earlier Jenkins environment. Not sure what is wrong. Can anyone please help?

Regards,
Venkatesh

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2f7cd4aa-6526-40de-910c-1e9672364cfcn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eqe8MmjGnQugn9hXk9zKhvxpQ4__--6oOFHP1v1p-WV2g%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7OhP85_iZAj6OyuWD3bGC5rXvQvoJSRJDrD5btxu2Q%3DQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28ep_m1uRwusmWNPZiMmzErXWOL0-jtOHBtyVpPX%2B-rRvdg%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6VH2Z0iru0fzRFUFeC25kfBANdu_Qsshpj_jXYj8juHA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: .svn folder getting checked out

Martin Schmude
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 past.

So, if possible, execute the same Jenkins job on the former and on the current setup once. Then compare their job logs, located in <jenkins-host>:<jenkins-port>/job/<job-name>/<build-number>/console.
You will find the SVN commands there by searching for "svn".
Do they look similar? Where have they been executed? On the Jenkins master or on a node?


[hidden email] schrieb am Dienstag, 29. Dezember 2020 um 11:01:34 UTC+1:
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 ago)

On Linux, ls will *not* show the .svn folders but they're still present.

Given you're using svn pre-1.7 there'll be such a folder in all folders in the local repository.

Cheers

Le lun. 28 déc. 2020 à 08:55, Ven H <[hidden email]> a écrit :
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 at 11:40 PM Baptiste Mathus <[hidden email]> wrote:
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 <[hidden email]> a écrit :
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 Jenkins Users <[hidden email]> wrote:
SVN does not download .svn folders, it creates them while performing a checkout.
With the older Jenkins instance every SVN checkout must have created a .svn folder too. Maybe you just didn't take note of them before the switch to your newer Jenkins instance, for whatever reason.


[hidden email] schrieb am Freitag, 25. Dezember 2020 um 18:57:24 UTC+1:
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 the .svn folders in the earlier (or older) Jenkins instance, whereas it is doing it in the newer Jenkins instance. SVN has not changed at all. Hope I have explained the problem statement correctly.

Regards,
Venkatesh


On Fri, Dec 25, 2020 at 6:23 PM Baptiste Mathus <[hidden email]> wrote:
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 is having a pre-1.7 svn binaries?

PS : we don't use the term 'slave' anymore for agents since 2016. And master got replaced by controller earlier this year.
Thanks.


Le jeu. 24 déc. 2020 à 19:27, Ven H <[hidden email]> a écrit :
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: "<SVN_credentials>", depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "<Source_URL>"]], quietOperation: true, workspaceUpdater: [$class: 'UpdateUpdater']])

This is working fine in a Jenkins environment (master & slaves)  on Windows. Now we are moving to a Jenkins master on a Docker container hosted in a Linux environment. The slaves are still Windows servers since the Application code is in .Net. 

The Source code is in SVN. After moving to the new Jenkins instance, we are facing a weird issue. The checkout step is somehow getting .svn folders also downloaded into the workspace, which was not happening in the earlier Jenkins environment. Not sure what is wrong. Can anyone please help?

Regards,
Venkatesh

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2f7cd4aa-6526-40de-910c-1e9672364cfcn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eqe8MmjGnQugn9hXk9zKhvxpQ4__--6oOFHP1v1p-WV2g%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7OhP85_iZAj6OyuWD3bGC5rXvQvoJSRJDrD5btxu2Q%3DQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/77be1630-4576-430e-9bbf-275ddfacb060n%40googlegroups.com.