The GitHub Pull Request Builder is a nice plugin

Hi,

I have enjoyed working with the GitHub Pull Request Builder and it’s a critical component of many jobs.

It seems the plugin is deprecated since the code hasn’t been maintained and it says “You should probably migrate to GitHub Branch Source Plugin

The GitHub Branch Source Plugin requires a Jenkinsfile.

Isn’t there a value in both GUI and CLI? In both Windows and Linux?

I’m using Freestyle projects which are the equivalent of Windows. They are easy to use. If I’m compelled to switch to Jenkinsfile, then I may also consider alternative CI systems that offer native YAML formats, at least.

Why not continue to support GitHub Pull Request Builder? Are Freestyle projects discouraged? They are a big selling point of Jenkins.

Welcome to the Jenkins community!

The GitHub pull request builder has two known security vulnerabilities that have been open for almost two years. As an open source project, the Jenkins project relies on maintainers to choose to fix issues. The maintainers of the GitHub pull request builder have chosen to not fix those issues. I suspect that they’ve chosen not to fix those vulnerabilities because they’ve switched to use GitHub branch source and Jenkins Pipeline.

Pipeline jobs have been more and more preferred by Jenkins users. Likewise, more and more features are added that support Pipelines.

Switching from the GitHub Pull Request Builder Plugin to the Multibranch Pipeline, which is not a drop-in replacement, and requires quite a bit of redesign… it turns out the features of Multibranch Pipeline are actually pretty neat! It is an improvement.

Maybe as you say, the authors have switched to Jenkins Pipeline, and so the deprecation acts as an encouragement for users to do the same.