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 <[email protected]> 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 <
> [email protected]> wrote:
>
>> 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.
>>
>>
>> [email protected] 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 <[email protected]> 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 <[email protected]> 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 [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAPp28epn9bDrJW6deQCtVNh2M8GYr1vvPM9vjevwDGKym%2Bhaug%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> --
>>>> 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 [email protected].
>>>>
>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS70dOJALP9zbO-ph5RpFm8Ua-17zaKvnRkjS0UyQ58k-A%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS70dOJALP9zbO-ph5RpFm8Ua-17zaKvnRkjS0UyQ58k-A%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> --
>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/2f7cd4aa-6526-40de-910c-1e9672364cfcn%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/2f7cd4aa-6526-40de-910c-1e9672364cfcn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eqe8MmjGnQugn9hXk9zKhvxpQ4__--6oOFHP1v1p-WV2g%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eqe8MmjGnQugn9hXk9zKhvxpQ4__--6oOFHP1v1p-WV2g%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS7OhP85_iZAj6OyuWD3bGC5rXvQvoJSRJDrD5btxu2Q%3DQ%40mail.gmail.com.

Reply via email to