[ee4j-pmc] Access to Jenkins instances for non committers

[Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>]

Hi,

We have a lot of tasks related to building CI/CD pipelines for EE4J projects. Currently there are unassigned tasks for more than 50 repositories. So, you understand, the amount of work needed. Recently I asked the community for help and there were some volunteers to take these tasks. The problem is that if a volunteer is not a committer on the project, he doesn’t have access to project's Jenkins instance. Also, we may consider utilising employees who are not project committers to work on these tasks. These developers need temporary access to Jenkins instances. They are not going to contribute more and don’t want to be project committers. 

I already raised this topic to EMO and webmasters. 

The proposed solution is complicated:

- tell contributors to create PR with pipeline in Jenkinsfile
- committers create pipeline jobs on JIPPs (Eclipse Foundation releng team can assist here).
- committers review and merge PR if they are satisfied.

I would like to discuss it on this mailing list. We are trying hard to attract the community to EE4J projects and at the same time making it impossible or really hard to contribute. Is there any easy solution?

Thanks,
Dmitry