Adoption of JenkinsPipelineUnit library

[Nik Reiman]

Hello!

As @stchar noted in a comment on the repository (see https://github.com/jenkinsci/JenkinsPipelineUnit/issues/156#issuecomment-561608219), this library can now be adopted in the same manner as Jenkins plugins.

I'd like to adopt this plugin on behalf of my company (Ableton AG). We have contributed to this plugin in the past and also written an extension library on top of it (see https://github.com/AbletonDevTools/jenkins-pipeline-mocks), since we noticed a long waiting time for merging PRs.

My GitHub username is nre-ableton, and my Jenkins infrastructure account name is nre_ableton. Thanks!

I tried reaching out to the maintainer (ozangunalp) in https://github.com/jenkinsci/JenkinsPipelineUnit/issues/156, though we were unable to agree on a time to discuss the matter further. In https://github.com/jenkinsci/JenkinsPipelineUnit/issues/156#issuecomment-535598801, he indicated that he would be open to me being added as a committer. I don't want to go behind his back, though, so I'll make a post in that GitHub issue that I've made this request.

Best,

Nik Reiman

DevTools team, Ableton AG

[Oleg Nenashev]

Hi Nik,

I see a response from Ozan ib the referenced issue. Also Stas is now formally a maintainer, so his approval also counts.

I have granted you permissions in GitHub, welcome aboard!

For the release permissions you will need to update https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/component-jenkins-pipeline-unit.yml

I'd like to adopt this plugin on behalf of my company (Ableton AG)

Note that we do not have a notion of "company ownership" in the Jenkins project at the moment, it is one of the items in my backlog.

Right now there is individual ownership, and the maintainers are expected to approve/transfer ownership to their teammates, e.g. if they decide to change the company

Best regards,

Oleg Nenashev