HTTP Request Plugin Adoption

[James Boylan]

Hi,
I would like to adopt a plugin:

    Link: https://github.com/jenkinsci/http-request-plugin
    Status: for adoption
    GitHub Username: Ralnoc
    Jenkins Infrastructure ID: Ralnoc
    Repository Permission Updater PR: https://github.com/jenkins-infra/repository-permissions-updater/pull/5134

My primary focus is to ensure that it is staying up to date with security standards, supporting current HTTP/HTTPS standards, and staying in line with the supported Java versions. I do wish to add support for POST as a Post-build step. This will allow the standardized code to be leveraged for publishing metadata, JSON, XML, or artifacts, to a custom HTTP/HTTPS endpoint.

[Jenkins Developers]

+1 from me.

[Mark Waite]

I replied from the Google groups web page and that hides my identity.

I, Mark Waite, approve of this adoption.

+1

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/08e658ee-a46a-4d9e-9cb8-38aa1a60a1bcn%40googlegroups.com.

[Daniel Krämer]

As someone who has spent some time working on this plugin I'd rather see it being deprecated and removed from pipelines in favor or `curl` or the likes via command line. 

Yet, it is widely used, so +1 from my end.

[Jesse Glick]

On Thu, Jul 2, 2026 at 10:56 AM 'Daniel Krämer' via Jenkins Developers <jenkin...@googlegroups.com> wrote:

I'd rather see it being deprecated and removed from pipelines in favor or `curl` or the likes via command line.

In general, yes. I think it has some legitimate use cases, when a simple HTTP request must be made during a point in pipeline execution when no agent is available. For example, inside `waitUntil` polling for readiness of some external workflow that is expected to take an hour: it would be wasteful to write this as a Bash wait loop even on a relatively cheap agent. We in fact use it on ci.jenkins.io as of https://github.com/jenkins-infra/pipeline-library/pull/210 FYI.

Are we expecting to have a discussion about the long-term viability of plugins when adoption requests are made? Because the Custom Tools and Matrix Sorter plugins recently mentioned would be on my personal list of things that have long since become obsolete and should be deprecated rather than resurrected. If users are aware of the recommended replacements and maintainers wish to devote time to these plugins anyway, there is not much harm, though anything on the update center does add to the body of code for which the Jenkins CERT team must at least triage incoming security vulnerability reports.

CONFIDENTIALITY NOTICE: This email and any attachments contain confidential and proprietary information of CloudBees intended only for the named recipient(s). Unauthorized use or distribution is prohibited. If you received this in error, please notify the sender and delete this email.

[Charles Honton]

I previously used this plugin instead of curl for a no-agent use case. Also, because of the runtime cost of invoking curl (multiple seconds adding up to minutes), custom steps in my jenkins shared library directly invoke java.net.http.HttpClient. If your use case is for pipeline builds, consider something similar.