Details
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: https://issues.jenkins.io/browse/JENKINS-70253?focusedCommentId=433214&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-433214
Answers
It seems the fix was already merged upstream
https://github.com/uber-archive/phabricator-jenkins-plugin/pull/357
I think you can just compile the plugin again and use that version, if you don't want to wait for the upstream release:
https://github.com/uber-archive/phabricator-jenkins-plugin/issues/358
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.