> - remove Jenkins DSL files (Yong maybe you can do it in another PR please) > - stop all of the Jobs on Jenkins
Okay, I will do that with separate PR. > On Jan 16, 2020, at 10:47 PM, Enrico Olivelli - Diennea > <enrico.olive...@diennea.com> wrote: > > I totally agree. > And I would like to make this change soon as Apache CI is so in bad state. > > I am not sure we need a VOTE or a BP, the road is simple: > - add new GitHub Actions > - remove Jenkins DSL files (Yong maybe you can do it in another PR please) > - stop all of the Jobs on Jenkins > - Celebrate > > > > Enrico > > Il giorno 16/01/20, 15:44 "Yong Zhang" <zhangyong1025...@gmail.com> ha > scritto: > > Hi BookKeepers, > Because of the Jenkins CI is not anymore working when a new pull request > created. I have been created a pull request to migrate the CI to the Github > Actions. But it seems I have no permission to run Github Actions in the > Apache BookKeeper repository, so I run it in my fork and all checks had > been passed. > > Any thoughts? > > FYI, the pull request about the migration: > https://github.com/apache/bookkeeper/pull/2246, > the passed Github Actions status in my repo: > https://github.com/zymap/bookkeeper/pull/2 > > Thanks, > Yong > > > > ________________________________ > > CONFIDENTIALITY & PRIVACY NOTICE > This e-mail (including any attachments) is strictly confidential and may also > contain privileged information. If you are not the intended recipient you are > not authorised to read, print, save, process or disclose this message. If you > have received this message by mistake, please inform the sender immediately > and destroy this e-mail, its attachments and any copies. Any use, > distribution, reproduction or disclosure by any person other than the > intended recipient is strictly prohibited and the person responsible may > incur in penalties. > The use of this e-mail is only for professional purposes; there is no > guarantee that the correspondence towards this e-mail will be read only by > the recipient, because, under certain circumstances, there may be a need to > access this email by third subjects belonging to the Company.
