Jenkins pipelines works great on one branch (either master, or a specific other branch defined in Branch Specifier). I

It's a multi branch pipeline, but for some reason, it won't build any feature branch when I commit something and await the SCM trigger period.

When I push a commit to master, the SCM trigger will poll and detect a change. The pipeline will build the master branch.

When I push a commit to e.g. feature/test, the trigger will poll but for some reason will only check master. The pipeline will never build the new commits in that feature branch.

This is what I can see in the git poll logs (my last push was at 12:22 AM)

```

Started on Jul 19, 2022, 12:28:00 AM Using strategy: Default [poll] Last Built Revision: Revision a9d99b7c25a9c3fc21d7e1be61a0ace32c624dc8 (origin/master) The recommended git tool is: git using credential bitbucket_creds > git rev-parse --resolve-git-dir /var/jenkins_home/workspace/unode-bitbucket@script/dfff7abd70e2267e5b482084285ba36f0148a29633c50781644e44bfe3292b66/.git # timeout=10 Fetching changes from the remote Git repositories > git config remote.origin.url

https://bp1979@bitbucket.org/valinso/iobox.git

1. timeout=10 Fetching upstream changes from

https://bp1979@bitbucket.org/valinso/iobox.git

> git --version # timeout=10 > git --version # 'git version 2.30.2' using GIT_ASKPASS to set credentials bitbucket_creds > git fetch --tags --force --progress –

https://bp1979@bitbucket.org/valinso/iobox.git

+refs/heads/:refs/remotes/origin/ # timeout=10 Polling for changes in Seen branch in repository origin/bugfix/fix-copy-app Seen branch in repository origin/feature/A1.1 Seen branch in repository origin/feature/bootloader-burn-fuse-select Seen branch in repository origin/feature/fpic-cmake Seen branch in repository origin/feature/mqtt-online Seen branch in repository origin/feature/mqtt-tester Seen branch in repository origin/feature/pic Seen branch in repository origin/feature/test Seen branch in repository origin/master Seen branch in repository origin/test/flash Seen 10 remote branches > git show-ref --tags -d # timeout=10 Using strategy: Default [poll] Last Built Revision: Revision a9d99b7c25a9c3fc21d7e1be61a0ace32c624dc8 (origin/master) The recommended git tool is: git using credential bitbucket_creds > git rev-parse --resolve-git-dir /var/jenkins_home/workspace/unode-bitbucket/.git # timeout=10 Fetching changes from the remote Git repositories > git config remote.origin.url

https://bp1979@bitbucket.org/valinso/iobox.git

1. timeout=10 Fetching upstream changes from

https://bp1979@bitbucket.org/valinso/iobox.git

> git --version # timeout=10 > git --version # 'git version 2.30.2' using GIT_ASKPASS to set credentials bitbucket_creds > git fetch --tags --force --progress –

https://bp1979@bitbucket.org/valinso/iobox.git

+refs/heads/:refs/remotes/origin/ # timeout=10 Polling for changes in Seen branch in repository origin/bugfix/fix-copy-app Seen branch in repository origin/feature/A1.1 Seen branch in repository origin/feature/bootloader-burn-fuse-select Seen branch in repository origin/feature/fpic-cmake Seen branch in repository origin/feature/mqtt-online Seen branch in repository origin/feature/mqtt-tester Seen branch in repository origin/feature/pic Seen branch in repository origin/feature/test Seen branch in repository origin/master Seen branch in repository origin/test/flash Seen 10 remote branches > git show-ref --tags -d # timeout=10 Done. Took 3.5 sec No changes

```