Retire some of my old plugins

126 views
Skip to first unread message

Gavin Mogan

unread,
Mar 16, 2024, 9:13:32 PM3/16/24
to Jenkins Developers
https://plugins.jenkins.io/html5-notifier-plugin/ - Code wasn't updated for html to div project, nobody complained. The html5 notifications apis have changed. While I do have a working branch, there's been no complaints, so I think we should just archive the plugin

https://plugins.jenkins.io/graphql-server/ - Failed attempt at trying to create graphql interface for jenkins. Graphql just doesn't handle class inheritance well enough for it to work nicely with all the plugin interfaces. Someone could take it over, but since its an incomplete prototype, I think its worth archiving them.

Is there any objections? Also how would I go about officially marking them depreciated/achieved?

Alexander Brandes

unread,
Mar 17, 2024, 4:01:11 AM3/17/24
to jenkin...@googlegroups.com
No objections from me.

To mark the plugins as EOL, I recommend adding the “deprecated” topic to the GitHub repositories, adding a note to the README that the plugin is EOL, closing open PRs and archiving the GH repository.
Finally, you can remove yourself from the repository-permission-updater file.

--
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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutK1ArKbCo3JbaPOz1V9DYFL_jtzeV4Cv4t5fMAdz%3D0uw%40mail.gmail.com.

Bruno Verachten

unread,
Mar 17, 2024, 9:14:26 AM3/17/24
to jenkin...@googlegroups.com
+1 from me.
Thank you for your work, Gavin.



--

Bruno Verachten
Sr Developer Relations
CloudBees, Inc.

P: +33.632.934.165 | GMT+1
E: bvera...@cloudbees.com

Twitter: https://twitter.com/Poddingue
LinkedIn: https://www.linkedin.com/in/poddingue/

Pronouns: he/his


Kris Stern

unread,
Mar 17, 2024, 9:17:27 AM3/17/24
to jenkin...@googlegroups.com
+1 from me too. 
Thank you Gavin for all your contributions to Jenkins. 

From: 'Bruno Verachten' via Jenkins Developers <jenkin...@googlegroups.com>
Sent: 17 March 2024 21:14
To: jenkin...@googlegroups.com <jenkin...@googlegroups.com>
Subject: Re: Retire some of my old plugins
 

Daniel Beck

unread,
Mar 19, 2024, 8:27:44 AM3/19/24
to jenkin...@googlegroups.com
On Sun, Mar 17, 2024 at 9:01 AM 'Alexander Brandes' via Jenkins Developers <jenkin...@googlegroups.com> wrote:
To mark the plugins as EOL, I recommend adding the “deprecated” topic to the GitHub repositories, adding a note to the README that the plugin is EOL, closing open PRs and archiving the GH repository.

In both cases it looks like continued distribution makes no real sense, so I recommend https://github.com/jenkins-infra/update-center2/?tab=readme-ov-file#removing-plugins-from-distribution in addition to the above.
 
Finally, you can remove yourself from the repository-permission-updater file.

To clarify (as this has been a problem in the past): Keep the file, just remove your 'developers' list entry (likely resulting in `developers: []` for valid YAML).

Gavin Mogan

unread,
May 6, 2024, 9:46:19 PM5/6/24
to jenkin...@googlegroups.com
Okay, only 2 months later...

I also added deprecated label to the two dead ones

Plugin site seems updated

thanks ya'll

--
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.

Adrien Lecharpentier

unread,
May 6, 2024, 10:50:00 PM5/6/24
to Jenkins Developers
Thank you Gavin for your contributions and all the time you spent on the project. 

Reply all
Reply to author
Forward
0 new messages