Quantcast

SVN Plugin - case sensitivity on tags, branches and trunk

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

SVN Plugin - case sensitivity on tags, branches and trunk

Kenneth Guardanapo
Our projects have been built with the folders under the project named Tags, Trunk and Branches.  When I create a parameterized project and try to build using it, it only shows those names in the dropdown.  I am unable to see anything under the folders.

If I rename them to tags, trunk and branches, the drop-down will show only the folders that have projects commited under them and the plugin works as advertised.

I do not see where there are any requirements for naming conventions to use the plugin.  SVN allows you to name them as you see fit, so the plugin should be able to work with whatever names are in the folder in any case.  Is this a matter of a minor change in the plugin code to remove this restriction?

--
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/4ae3c88a-57c7-48a6-88e7-4c6d066deebb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: SVN Plugin - case sensitivity on tags, branches and trunk

Baptiste MATHUS
Hello,
I think this is a bit more than opinionated than what you say.
I agree SVN does not enforce that, and have been using SVN for years myself (well, I stopped now).
But this convention is present all over the place, like in https://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html

So, I'm not surprised the plugin does not parse this as the same.

Now, having said that. I guess proposing a PR on the plugin to use a system prop, or even a global checkbox to allow case insensitivity could be considered. But in the end, it will also the maintainer's choice to support or not an additional complexity for a possibly pretty rare situation.

You probably want to search or file an issue describing your case first, and propose an associated pull-request to move forward.

Cheers

2017-03-20 15:19 GMT+01:00 Kenneth Guardanapo <[hidden email]>:
Our projects have been built with the folders under the project named Tags, Trunk and Branches.  When I create a parameterized project and try to build using it, it only shows those names in the dropdown.  I am unable to see anything under the folders.

If I rename them to tags, trunk and branches, the drop-down will show only the folders that have projects commited under them and the plugin works as advertised.

I do not see where there are any requirements for naming conventions to use the plugin.  SVN allows you to name them as you see fit, so the plugin should be able to work with whatever names are in the folder in any case.  Is this a matter of a minor change in the plugin code to remove this restriction?

--
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/4ae3c88a-57c7-48a6-88e7-4c6d066deebb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/CANWgJS49EENPqkAu%2BVeyBXj%3D8vUATu_w_n6ZRBm_s2CLqv-5NQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Loading...