[JIRA] [git-client-plugin] (JENKINS-29321) Setting custom refspec with wildcards throws an exception

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title

Mark Waite commented on JENKINS-29321   Re: Setting custom refspec with wildcards throws an exception I think the code would be much improved if it presented a message in the UI when an invalid refspec is entered, rather than refusing to save the job definition and showing a stack trace. The git online manual on RefSpec says that the format +refs/heads/dev*:refs/remotes/origin/dev* is invalid. I believe the code is correct to declare that is an illegal argument (though it really should inform the user of that problem with a much more friendly message than a stack trace and refusal to save the form). The manual says: You can’t use partial globs in the pattern, so this would be invalid: fetch = +refs/heads/qa*:refs/remotes/origin/qa* Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.