Pull request refspec

[Jennifer Schuch]

Hi,

I'm working on a poc for building pull requests (refs/pull-requests/*/merge-clean) since we are experiencing a high build failure rate when building developers remote branches. We are expecting the code to be in a buildable state, ready for integration when a Pull Request is submitted.

Currently have this setup working with Jenkins/git plugin/Stash jenkins webhook. My question is, is there a way to limit the amount of pull requests git is going thru? Meaning, pull requests greater than some specified number? I can see this list becoming huge if/when implemented into our live production environment.

Started by an SCM change
Building in workspace C:\Program Files (x86)\Jenkins\workspace\crypto pull request build
Checkout:crypto pull request build / C:\Program Files (x86)\Jenkins\workspace\crypto pull request build - hudson.remoting.LocalChannel@1a2017d
Using strategy: Default
Last Built Revision: Revision 8fc758db16e8df6bb98a5d90e29f85c08f5894c6 (origin/pull-requests/6/merg-clean)
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Pruning obsolete local branches
Seen branch in repository origin/branch_dev
Seen branch in repository origin/branch_jks
Seen branch in repository origin/branch_jks2
Seen branch in repository origin/branch_jks3
Seen branch in repository origin/master
Seen branch in repository origin/pull-requests/1/from
Seen branch in repository origin/pull-requests/1/merge
Seen branch in repository origin/pull-requests/1/merge-clean
Seen branch in repository origin/pull-requests/1/to
Seen branch in repository origin/pull-requests/2/from
Seen branch in repository origin/pull-requests/2/merge
Seen branch in repository origin/pull-requests/2/merge-base
Seen branch in repository origin/pull-requests/2/merge-clean
Seen branch in repository origin/pull-requests/2/to
Seen branch in repository origin/pull-requests/3/from
Seen branch in repository origin/pull-requests/3/merge
Seen branch in repository origin/pull-requests/3/merge-base
Seen branch in repository origin/pull-requests/3/merge-clean
Seen branch in repository origin/pull-requests/3/to
Seen branch in repository origin/pull-requests/4/from
Seen branch in repository origin/pull-requests/4/merge
Seen branch in repository origin/pull-requests/4/merge-clean
Seen branch in repository origin/pull-requests/4/to
Seen branch in repository origin/pull-requests/5/from
Seen branch in repository origin/pull-requests/5/merge
Seen branch in repository origin/pull-requests/5/merge-clean
Seen branch in repository origin/pull-requests/5/to
Seen branch in repository origin/pull-requests/6/from
Seen branch in repository origin/pull-requests/6/merge
Seen branch in repository origin/pull-requests/6/merge-clean
Seen branch in repository origin/pull-requests/6/to
Seen branch in repository origin/pull-requests/7/from
Seen branch in repository origin/pull-requests/7/merge
Seen branch in repository origin/pull-requests/7/merge-clean
Seen branch in repository origin/pull-requests/7/to
Seen 35 remote branches

[Jennifer Schuch]

found that this is resolved in STash2.12