Tully Foote commented on Bug JENKINS-27115

Is this the discussion from Alexander Link you are referring to? https://issues.jenkins-ci.org/browse/JENKINS-20767

When searching for that I also found related tickets: https://issues.jenkins-ci.org/browse/JENKINS-25580 and https://issues.jenkins-ci.org/browse/JENKINS-14026

I've been trying many regex invocations. Using the java regex http://www.tutorialspoint.com/java/java_regular_expressions.htm
But it does not appear that the simple regex :branch/name works. The ls-remote gets passed the entire regex including the : and fails to match anything. And then also passes the full string through to the clone which also fails.

I think I've found that I can make it work with the wildcard evaluation using */full/branch/name, based on the first link above.

I completely understand keeping backwards compatibility so as not to break existing users relying on the behavior. However, I would like to suggest adding an option which defaults to off which can disable the legacy trimming behavior to allow users the option to avoid it if they want.

It's also really frustrating that these things are not documented in the help fields. The trimming is not mentioned in the help fields, and recommending the fully qualified paths to "avoid ambiguity" without mentioning that they are actually going to be trimmed and ambiguous is very frustrating.

From finding the other related issues, it seems that I'm not the only one encountering this problem. It would be really great to get an option to disable the trimming. With or without that updating the documentation to mention the trimming and potential work around solutions would be greatly appreciated.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to