Re: Github action migration Discussion
+1 Github has more resources to run CI jobs as the contributions keep growing. On Tue, Jan 14, 2020 at 11:06 AM Guangning E wrote: > After a period of testing, Github's action is much more stable than > Jenkins. Jenkins now has a large number of tasks in the queue and > insufficient resources. The committer cannot trigger the test. > > Jenkins: https://builds.apache.org/job/pulsar_precommit_java8/ > > Github action: > > https://github.com/apache/pulsar/pull/6041/checks?check_run_id=388093558 > https://github.com/apache/pulsar/pull/6037/checks?check_run_id=386604833 > https://github.com/apache/pulsar/pull/6034/checks?check_run_id=385585117 > > Now let's consider migration testing from Jenkins to Github action > > Thanks, > Guangning >
Re: Github action migration Discussion
+1 Especially for doc PRs. Passing all Jenkins tests eats up much time. On Tue, Jan 14, 2020 at 4:15 PM Jinfeng Huang wrote: > +1 > Currently, a large number of PRs are blocked by Jenkins. > > Best Regards, > Jennifer > > > On Tue, Jan 14, 2020 at 11:06 AM Guangning E wrote: > > > After a period of testing, Github's action is much more stable than > > Jenkins. Jenkins now has a large number of tasks in the queue and > > insufficient resources. The committer cannot trigger the test. > > > > Jenkins: https://builds.apache.org/job/pulsar_precommit_java8/ > > > > Github action: > > > > https://github.com/apache/pulsar/pull/6041/checks?check_run_id=388093558 > > https://github.com/apache/pulsar/pull/6037/checks?check_run_id=386604833 > > https://github.com/apache/pulsar/pull/6034/checks?check_run_id=385585117 > > > > Now let's consider migration testing from Jenkins to Github action > > > > Thanks, > > Guangning > > >
Re: Github action migration Discussion
+1 Currently, a large number of PRs are blocked by Jenkins. Best Regards, Jennifer On Tue, Jan 14, 2020 at 11:06 AM Guangning E wrote: > After a period of testing, Github's action is much more stable than > Jenkins. Jenkins now has a large number of tasks in the queue and > insufficient resources. The committer cannot trigger the test. > > Jenkins: https://builds.apache.org/job/pulsar_precommit_java8/ > > Github action: > > https://github.com/apache/pulsar/pull/6041/checks?check_run_id=388093558 > https://github.com/apache/pulsar/pull/6037/checks?check_run_id=386604833 > https://github.com/apache/pulsar/pull/6034/checks?check_run_id=385585117 > > Now let's consider migration testing from Jenkins to Github action > > Thanks, > Guangning >
Re: Github action migration Discussion
Thanks @Guangning E contribution, The changes LGTM +1 -- Thanks Xiaolong Ran > 在 2020年1月14日，上午11:05，Guangning E 写道： > > After a period of testing, Github's action is much more stable than > Jenkins. Jenkins now has a large number of tasks in the queue and > insufficient resources. The committer cannot trigger the test. > > Jenkins: https://builds.apache.org/job/pulsar_precommit_java8/ > > Github action: > > https://github.com/apache/pulsar/pull/6041/checks?check_run_id=388093558 > https://github.com/apache/pulsar/pull/6037/checks?check_run_id=386604833 > https://github.com/apache/pulsar/pull/6034/checks?check_run_id=385585117 > > Now let's consider migration testing from Jenkins to Github action > > Thanks, > Guangning
Re: Github action migration Discussion
+1 On Tue, 14 Jan 2020 at 08:36, Guangning E wrote: > > After a period of testing, Github's action is much more stable than > Jenkins. Jenkins now has a large number of tasks in the queue and > insufficient resources. The committer cannot trigger the test. > > Jenkins: https://builds.apache.org/job/pulsar_precommit_java8/ > > Github action: > > https://github.com/apache/pulsar/pull/6041/checks?check_run_id=388093558 > https://github.com/apache/pulsar/pull/6037/checks?check_run_id=386604833 > https://github.com/apache/pulsar/pull/6034/checks?check_run_id=385585117 > > Now let's consider migration testing from Jenkins to Github action > > Thanks, > Guangning -- Thanks Yuvaraj L
