Page MenuHomePhorge

Maintenance of / Involvement in the Phabricator Plug-in for Jenkins
Closed, ResolvedPublic

Asked by kwisatz on Dec 11 2022, 17:00.


I have recently been reading up on the ticket that discusses the lack of adoption of arcanist as an obstacle for larger adoption of Phorge.
I think that the Phabricator Plug-in for Jenkins authored by Uber may play a similar role. Without the plug-in, there is no longer any reason for our company to be using Phorge.

And just a few days ago, the plug-in stopped working reliably because one of its dependencies has been deprecated. See my ticket over at github.

What do you think about this? Should there perhaps be a phorge fork of the plug-in in order to ensure Phorge stays attractive for users of Jenkins?
There doesn't seem to be a lot of interest by the original author anymore to assure maintenance:


Updated 443 Days Ago

Under T15030, we're basically open to any plugin/extension that involves Phorge, so we'd like that - if you (or someone) is willing to take ownership.

It can be hosted here, or wherever the Jenkins community likes.

Updated 384 Days Ago

It seems the fix was already merged upstream

I think you can just compile the plugin again and use that version, if you don't want to wait for the upstream release:

We can probably mirror that plugin here on Phorge, once a new maintainer will be alive, but I don't know if it's a good idea to move the whole plugin contribution workflow on Phorge. It should be the new Jenkins plugin maintainer to decide.

Updated 384 Days Ago

Just wondering: people or organisations who are no longer using Jenkins with Phorge, what are you using nowadays? And do these set-ups allow for the same level of integration with Herald/Differential?

New Answer


This question has been marked as closed, but you can still leave a new answer.