Plugin dev owner

[John Michealson]

Hi all.   We have a plugin in the market.  The staffer who built and managed it has moved on and I need to understand is there anything more required other than doing PR to keep it updated?

TYIA

[Gavin Mogan]

It's a fairly vague, broad and open ended questions but I'll try.

Are you accepting user bug reports? You probably want to get access to jira, or GitHub depending on where you are accepting them. If GitHub you may or may not want to change the default assignee for your component.

Are you planning on making code changes? You'll need to get access to the code repo.

Are you planning on making releases? It's possible continuous releases is setup and you can just commit, but most likely you'll need to have access to artifactory so you can cut releases.

At the very least I recommend reading https://www.jenkins.io/doc/developer/plugin-governance/managing-permissions/ and maybe https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/ and figuring out what you want to do next before asking for how to do it.

Gavin

On Wed., Aug. 25, 2021, 8:45 p.m. John Michealson, <chkp.j...@gmail.com> wrote:

Hi all.   We have a plugin in the market.  The staffer who built and managed it has moved on and I need to understand is there anything more required other than doing PR to keep it updated?

TYIA

--
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/1f372ecb-72aa-44a5-b34c-2aa9b1ced996n%40googlegroups.com.