Skip to content

Plugin adoption: I'd like to co-maintain http-request #342

Closed

Description

@h3nr1-d14z

Hi! 👋

The adopt-this-plugin topic brought me here. I'd like to adopt and co-maintain this plugin.

Who I am: I recently became the maintainer of discord-notifier-plugin through the Adopt-a-Plugin program (RPU #5271, with @MarkEWaite's approval). Since taking it over I've merged a long-standing truncation bug fix (#159), shipped release 281.v41a_01a_c2e7dc, and have a dependency-modernization PR up (#165 — unirest-java → Apache HttpComponents swap).

Why http-request: it's a widely-used plugin (30k+ installations) sitting on a backlog with no active day-to-day maintainer — recent history is almost entirely dependabot bumps. My recent work maps directly onto it: the discord-notifier swap was a from-scratch migration to CloseableHttpClient with proxy/timeout/multipart parity, which is exactly this plugin's territory. Old PRs like #137 (proxy auth), #124 (redirect handling), and #53 (Authorization masking) are in the same problem space.

What I'd do first: triage the open PR queue (some date back years), work through the high-signal issues (#319 error masking, #320 secret-text credentials, #323 proxy env vars), and keep releases flowing.

@janario @MarkEWaite @oleg_nenashev @sandi2382 @Ralnoc — would any of you object, or better yet, like to hand over with your blessing? Happy to take pointers on anything load-bearing I should know about.

— h3nr1-d14z

Activity

  1. h3nr1-d14z commented on Sep 7, 2026

    @h3nr1-d14z
    ContributorAuthor

    While waiting on maintainer feedback: @Ralnoc, I'd be glad to give #338 a detailed technical review as a first contribution — it's the most recent substantive change in the queue and pairs with #337. Happy to do that before any of the paperwork resolves.

    — h3nr1-d14z

  2. MarkEWaite commented on Sep 7, 2026

    @MarkEWaite
    Contributor

    +1 from me.

  3. Ralnoc commented on Sep 7, 2026

    @Ralnoc
  4. h3nr1-d14z commented on Sep 7, 2026

    @h3nr1-d14z
    ContributorAuthor

    @MarkEWaite @Ralnoc — thank you both, appreciated!

    Two notes:

    Handle correction: my original post mentioned @oleg_nenashev, but that handle doesn't resolve — the account is @oleg-nenashev (hyphen), so the ping never landed. Fixing here so it does: @oleg-nenashev — I'd like to co-maintain this plugin; details in the top post, and there are already two +1s above. No rush, chime in as you see fit.

    On #338: understood, @Ralnoc — I'll hold off until your cleanup pass lands. Ping me here whenever you'd like the second pair of eyes.

    — h3nr1-d14z

  5. oleg-nenashev commented on Sep 13, 2026

    @oleg-nenashev
    Member

    @h3nr1-d14z I put this plugin for adoption ages ago, and I have no objections
    Please follow https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/

  6. h3nr1-d14z commented on Sep 19, 2026

    @h3nr1-d14z
    ContributorAuthor

    thanks Oleg! the adoption went through on the 8th (RPU #5273, with Mark and timja's help) — bit of a head start, but glad to have the original owner's blessing too. we're keeping busy: backlogged PRs are moving again and the plugin is on continuous delivery now.

    — h3nr1-d14z

  7. h3nr1-d14z commented on Sep 19, 2026

    @h3nr1-d14z
    ContributorAuthor

    closing — the adoption is complete: RPU #5273 merged 2026-09-08 with Mark and timja's help, Oleg (original owner) has no objections, CD is enabled and shipping (1.26, 1.657, 1.658, 1.659), and the PR backlog is moving again. thanks everyone.

    — h3nr1-d14z

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions