For me I think we could first enable the github issues, for users to ask questions and discuss things. And if there are actual bugs or something which require code changes, we could file an jira, and also let the contributor to register a jira account. I think this is also easier for our PMCs to decide whether a jira account is necessary for a given user comparing to the current workflow. The private mailing list is full of jira registrations notifications and hard to find other useful information...
And on moving to github actions, in general I'm +1 on this. We should try to follow modern ways. And on the funding side, we still have 10 machines, we could contact INFRA to see how to make use of these machines if we switch to github actions. Thanks. Istvan Toth <st...@cloudera.com.invalid> 于2024年10月2日周三 17:31写道： > > I've been working on modifying the existing Jenkinsfile, and it has been a > horrible experience, especially as I'm trying to mix declarative and > scripted syntax. > I think from a usability standpoint GH actions would be a win. > > On the other hand, our Jenkinsfiles don't do that much, as most of the > actual CI process is performed via Yetus, so migration shouldn't be a huge > amount of work. > > I seem to recall seeing similar discussions on ASF mailing lists, but I > haven't followed them closely. > > Istvan > > Istvan > > On Wed, Oct 2, 2024 at 11:23 AM Nick Dimiduk <ndimi...@apache.org> wrote: > > > Heya, > > > > I'd like to take the community temperature on migrating our build infra > > from the ci-hbase.a.o Jenkins instance to something built on GitHub > > Actions. I have several reasons that justify this proposal. > > > > As some of you may know, our community funding has reduced and we will no > > longer be able to sustain the current fleet of build infrastructure. So, > > one motivation for this proposal is cost-cutting: I think that we'll be > > able to operate at lower costs if we can migrate to a provisioned-as-needed > > model of consumption. > > > > My second reason is an optimistic appeal to a larger contributor base. I > > suspect that if we can modernize our infrastructure then we will increase > > the pool of contributors who might be able to participate in this area. I > > believe that GH Actions (and systems like it) is more prevalent in the > > industry than Jenkins, which means that more people already have experience > > with the platform and more people will feel compelled to offer support to > > an OSS project that uses the platform as a means of growing their own > > skillset and as a means of bolstering their CVs. > > > > Dove-tailed into reason two is reason three: I believe that there is a > > large community of folks who are developing GitHub Actions on its > > marketplace. We would effectively open ourselves up to more off-the-shelf > > offerings and those offerings would be in our hands directly. By contrast, > > I don't think there's as much development in Jenkins plugins, and the > > process of adding a new plugin to our Jenkins instance requires filing an > > INFRA ticket. > > > > These are my motivations. I'm still not clear on what's possible yet for > > ASF projects. I have filed an INFRA ticket, requesting whatever is > > necessary for us to start an experiment. Indeed, I believe that there are > > some major limitations on the current implementation provided by the ASF, > > and as far as I can tell, only one project with a build footprint that > > resembles HBase has pursued this effort. I've catalogued the applicable > > information that I've found so far on that issue. > > > > https://issues.apache.org/jira/browse/INFRA-26170 > > > > Thanks, > > Nick > > > > > -- > *István Tóth* | Sr. Staff Software Engineer > *Email*: st...@cloudera.com > cloudera.com <https://www.cloudera.com> > [image: Cloudera] <https://www.cloudera.com/> > [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image: > Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera > on LinkedIn] <https://www.linkedin.com/company/cloudera> > ------------------------------ > ------------------------------
