-
Bug
-
Resolution: Unresolved
-
Major
-
git plugin 2.2.1
I create a free-style software project, and config branch specifier to "*/feature/**" in order to build automatically when Stash receives a push to those branches. Git Plugin receives the NotifyCommit:
Triggering the polling of xxx
But nothing happens as expected, except the first initialise fetch.
When changing branch specifier to 'origin/feature/category' or '*/master', everything goes well. 'SCM changes detected' appears on System log.
The screenshot attachments are configs of my project.
I can't figure out what's going wrong, please help me.
[JENKINS-22861] build is not triggered automatically if branch specifier contains wildcards
Description |
Original:
I create a free-style software project, and config branch specifier to "*/feature/**" in order to build automatically when Stash receives a push to those branches. Git Plugin receives the NotifyCommit: {code} Triggering the polling of xxx {code} But nothing happens as expected, except the first initialise fetch. When changing branch specifier to 'origin/feature/category' or '*/master', everything goes well. 'SCM changes detected' appears on System log. The screenshot attachments are configs of my project. I can't figure out what's going wrong, please help me. |
New:
I create a free-style software project, and config branch specifier to *"\*/feature/\*\*"* in order to build automatically when Stash receives a push to those branches. Git Plugin receives the NotifyCommit: {code} Triggering the polling of xxx {code} But nothing happens as expected, except the first initialise fetch. When changing branch specifier to 'origin/feature/category' or '\*/master', everything goes well. 'SCM changes detected' appears on System log. The screenshot attachments are configs of my project. I can't figure out what's going wrong, please help me. |
Workflow | Original: JNJira [ 155006 ] | New: JNJira + In-Review [ 178975 ] |
Assignee | Original: Nicolas De Loof [ ndeloof ] |