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

["Markus KARG" <markus@xxxxxxxxxxxxxxx>]

I do not see a special case or particular complexity here compared to other tasks like implementing a feature or fixing a complex bug, so for me there is no need for exceptions. The only need I see is that the committers of all those projects have to be more active. For example, in JAX-RS the majority of pre-selected committers did neither commit nor even participate in discussions or PR reviews within the past eight months! So in other words, if the pre-selected committers do not have the time, knowledge or will to set up the pipeline, we should seek for new contributors, not for other rules, and ask them for PRs. This will take a while, certainly, but it will teach us to really accept and live the EF way, not to try to change the EF while we all are in incubation state still.
-Markus


-----Original Message-----
From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Dmitry Kornilov
Sent: Donnerstag, 6. September 2018 20:51
To: EE4J PMC Discussions
Subject: [ee4j-pmc] Access to Jenkins instances for non committers

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


_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc