Adopting build-history-metrics-plugin

[Nick Charsley]

I've been looking at build-history-metrics-plugin which needs some updates to get it working with WorkflowJobs. The last update from the Maintainer was June 2015. 

 * Plugin: https://github.com/jenkinsci/build-history-metrics-plugin 

 * Pull requests 

   o https://github.com/jenkinsci/build-history-metrics-plugin/pull/3 

   o Working on others (Updating to later version of core) 

 * Github ID: NickCharsley 

 * Jenkins ID: NickCharsley 

Also the build-history-metrics-plugin appears to be missing from Jira so currently no issues can be logged. I have attempted to contact the current maintainer but both his email address (ai...@aidanmcginley.com) and his website listed on Git Hub (www.aidanmcginley.com) are dead. 

 Nick(c) 

[Nick Charsley]

Not sure if anything was missing from this request, 

I’m still quite keen to adopt this plug-in as it really needs up dating to add pipeline jobs.

Nick(c)

On 27 Jul 2021, at 08:44, Nick Charsley <nickch...@gmail.com> wrote:

I've been looking at build-history-metrics-plugin which needs some updates to get it working with WorkflowJobs. The last update from the Maintainer was June 2015. 

--
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/8834f2c9-e140-4a63-90e0-ffba27e86d5cn%40googlegroups.com.

[Gavin Mogan]

Honestly things just get lost all the time, too many things to do not enough people to do them.

Normally you are supposed to cc the current owner when you post to the mailing list for something that isn't marked as abandoned, but since the plugin hasn't been touched in 6 years and the existing contact info is gone, I'm comfortable skipping that part.

We need you to create a PR for https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-build-history-metrics-plugin.yml (and tag the current owner, even if they are not responding) with your artifactory/jenkins.io account, and part of that process you'll be given github access.

On a side note, we should look into a system that formalize this, maybe with hosting tickets or something, so things are in a queue and not lost.

Gavin

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/AFD48962-E60D-4BBE-AA82-711A44D1B134%40gmail.com.

[Nick Charsley]

No problem Gavin,

I always knew this one may be a bit problematic as it appeared to have been left so long ago.

I 'think' I've done the pull request correctly so that at least will be 'queued' and so hopefully will not get lost.

Yes I can see a ticketing system could be good, but as always it's the value stream, how many adoption requests come through and how many people give up  rather than prod again, if you are not losing potential maintainers then spending time improving this system vs spending that time enhancing Jenkins, I know where I'd like you to be spending time :)

Nick(c)

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutXPkeJhbgftVtL_E6GNvAzFoL8QCiaAUdGMXuY%3Dj%2Beig%40mail.gmail.com.