Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
For the git branch parameter, set Branch Filter to: origin/(.*) I found the parentheses to be counter-intuitive, because if you don't specify a filter you get: .* (No parens.) If you are filteri...
Answer
#2: Post edited
- For the git branch parameter, set Branch Filter to:
- origin/(.*)
- I found the parentheses to be counter-intuitive, because if you don't specify a filter you get:
- .*
- (No parens.) If you are filtering stuff out, you use parens to indicate the part to keep.
- For the git branch parameter, set Branch Filter to:
- origin/(.*)
- I found the parentheses to be counter-intuitive, because if you don't specify a filter you get:
- .*
- (No parens.) If you are filtering stuff out, you use parens to indicate the part to keep.
- The parens indicate a *capture group*, which is general to regular expressions and not specific to this case. Specific to this case is that the branch filter of the git-parameter plug-in takes the matched capture group as value if and only if the regex pattern contains a *single* capture group. If the regex pattern has more than one capture group, the branch name is taken as value -- as if the pattern were defined without capture groups at all. It's not well-documented, but see the [code](https://github.com/jenkinsci/git-parameter-plugin/blob/c40ec6db14f5a5e0abaab143037d3292bbe3fcbb/src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java#L370-L377). (Thanks to hkotsubo and elgonzo for the information in this paragraph.)