You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Ali Ahmed <al...@gmail.com> on 2019/08/26 20:36:56 UTC
Jenkins migration proposal
I have finished by poc with Github actions. I propose we disable the
jenkins pr check in jobs with this. The benefits are more stable test runs
and more available resources to instantly start running checkin jobs.
The experimental PR is here.
https://github.com/apache/pulsar/pull/5035
We should be able to do the migration very quickly.
-Ali
Re: Jenkins migration proposal
Posted by Ali Ahmed <ah...@gmail.com>.
Let's request apache to disable apache for ci cd on a fixed date , we can
enable github ci cd in parallel.
-Ali
On Wed, Nov 6, 2019 at 4:48 AM Sijie Guo <gu...@gmail.com> wrote:
> Ali,
>
> I checkout your branch to my fork and submit a new pull request -
> https://github.com/apache/pulsar/pull/5574
>
> Github Action now can run on the forked repo. So that we can proceed the
> github action approach now.
>
> - Sijie
>
> On Sat, Oct 26, 2019 at 2:51 AM Ali Ahmed <al...@gmail.com> wrote:
>
> > Thanks for verifying this yong.
> >
> > -Ali
> >
> > On Fri, Oct 25, 2019 at 2:04 AM Yong Zhang <zh...@gmail.com>
> > wrote:
> >
> > > Hi all,
> > >
> > > The GitHub Actions works well on the public repo. Also can verify the
> > pull
> > > request from the fork.
> > >
> > > To test the Github Actions, I create a public repo and use an account
> > > without the GitHub Actions
> > > service to create a pull request. The GitHub Actions working well.
> > > I think we can consider moving a part of the CI from Jenkins to the
> > GitHub
> > > Actions.
> > >
> > >
> >
>
--
-Ali
Re: Jenkins migration proposal
Posted by Sijie Guo <gu...@gmail.com>.
Ali,
I checkout your branch to my fork and submit a new pull request -
https://github.com/apache/pulsar/pull/5574
Github Action now can run on the forked repo. So that we can proceed the
github action approach now.
- Sijie
On Sat, Oct 26, 2019 at 2:51 AM Ali Ahmed <al...@gmail.com> wrote:
> Thanks for verifying this yong.
>
> -Ali
>
> On Fri, Oct 25, 2019 at 2:04 AM Yong Zhang <zh...@gmail.com>
> wrote:
>
> > Hi all,
> >
> > The GitHub Actions works well on the public repo. Also can verify the
> pull
> > request from the fork.
> >
> > To test the Github Actions, I create a public repo and use an account
> > without the GitHub Actions
> > service to create a pull request. The GitHub Actions working well.
> > I think we can consider moving a part of the CI from Jenkins to the
> GitHub
> > Actions.
> >
> >
>
Re: Jenkins migration proposal
Posted by Ali Ahmed <al...@gmail.com>.
Thanks for verifying this yong.
-Ali
On Fri, Oct 25, 2019 at 2:04 AM Yong Zhang <zh...@gmail.com>
wrote:
> Hi all,
>
> The GitHub Actions works well on the public repo. Also can verify the pull
> request from the fork.
>
> To test the Github Actions, I create a public repo and use an account
> without the GitHub Actions
> service to create a pull request. The GitHub Actions working well.
> I think we can consider moving a part of the CI from Jenkins to the GitHub
> Actions.
>
>
Re: Jenkins migration proposal
Posted by Yong Zhang <zh...@gmail.com>.
Hi all,
The GitHub Actions works well on the public repo. Also can verify the pull request from the fork.
To test the Github Actions, I create a public repo and use an account without the GitHub Actions
service to create a pull request. The GitHub Actions working well.
I think we can consider moving a part of the CI from Jenkins to the GitHub Actions.
Re: Jenkins migration proposal
Posted by Matteo Merli <ma...@gmail.com>.
That would be an issue since all the PRs should be created from a user
fork.
On Wed, Aug 28, 2019 at 7:57 PM Yong Zhang <zh...@gmail.com>
wrote:
> Hi all,
>
> I found the Github Actions only can running on the base repository. If I
> create a pull request from fork repo, it will not be running.
>
> FYI:
>
> https://github.community/t5/GitHub-API-Development-and/Run-a-GitHub-action-on-pull-request-for-PR-opened-from-a-forked/m-p/15426#M363
>
>
> On Tue, 27 Aug 2019 at 04:37, Ali Ahmed <al...@gmail.com> wrote:
>
> > I have finished by poc with Github actions. I propose we disable the
> > jenkins pr check in jobs with this. The benefits are more stable test
> runs
> > and more available resources to instantly start running checkin jobs.
> >
> > The experimental PR is here.
> > https://github.com/apache/pulsar/pull/5035
> >
> > We should be able to do the migration very quickly.
> >
> > -Ali
> >
>
--
--
Matteo Merli
<ma...@gmail.com>
Re: Jenkins migration proposal
Posted by Yong Zhang <zh...@gmail.com>.
Hi all,
I found the Github Actions only can running on the base repository. If I
create a pull request from fork repo, it will not be running.
FYI:
https://github.community/t5/GitHub-API-Development-and/Run-a-GitHub-action-on-pull-request-for-PR-opened-from-a-forked/m-p/15426#M363
On Tue, 27 Aug 2019 at 04:37, Ali Ahmed <al...@gmail.com> wrote:
> I have finished by poc with Github actions. I propose we disable the
> jenkins pr check in jobs with this. The benefits are more stable test runs
> and more available resources to instantly start running checkin jobs.
>
> The experimental PR is here.
> https://github.com/apache/pulsar/pull/5035
>
> We should be able to do the migration very quickly.
>
> -Ali
>
Re: Jenkins migration proposal
Posted by Jia Zhai <zh...@gmail.com>.
+1
Best Regards.
Jia Zhai
Beijing, China
Mobile: +86 15810491983
On Tue, Aug 27, 2019 at 10:07 PM Enrico Olivelli <eo...@gmail.com>
wrote:
> Cc dev@bookkeeper
> If it works well for Pulsar we could try for BK, we have a quite complex
> precommit job set
>
>
> Enrico
>
> ---------- Forwarded message ---------
> Da: Ivan Kelly <iv...@apache.org>
> Date: mar 27 ago 2019, 14:26
> Subject: Re: Jenkins migration proposal
> To: <de...@pulsar.apache.org>
>
>
> +1 for moving to actions. It looks to be azure pipelines in
> background. It should be able to give us more hermetic testing.
> Jenkins has always had issues of old builds hanging around the cluster
> and causing unreproducible flakes.
>
> FYI, infra are giving their blessing to people trying it out.
>
> http://mail-archives.apache.org/mod_mbox/www-builds/201908.mbox/%3cd425ae5c-7977-7aed-7fd8-ef63a6c0a850@apache.org%3e
>
> -Ivan
>
> On Mon, Aug 26, 2019 at 9:50 PM Sijie Guo <gu...@gmail.com> wrote:
> >
> > The results look promising.
> >
> > +1
> >
> > - Sijie
> >
> > On Mon, Aug 26, 2019 at 1:37 PM Ali Ahmed <al...@gmail.com> wrote:
> >
> > > I have finished by poc with Github actions. I propose we disable the
> > > jenkins pr check in jobs with this. The benefits are more stable test
> runs
> > > and more available resources to instantly start running checkin jobs.
> > >
> > > The experimental PR is here.
> > > https://github.com/apache/pulsar/pull/5035
> > >
> > > We should be able to do the migration very quickly.
> > >
> > > -Ali
> > >
>
Fwd: Jenkins migration proposal
Posted by Enrico Olivelli <eo...@gmail.com>.
Cc dev@bookkeeper
If it works well for Pulsar we could try for BK, we have a quite complex
precommit job set
Enrico
---------- Forwarded message ---------
Da: Ivan Kelly <iv...@apache.org>
Date: mar 27 ago 2019, 14:26
Subject: Re: Jenkins migration proposal
To: <de...@pulsar.apache.org>
+1 for moving to actions. It looks to be azure pipelines in
background. It should be able to give us more hermetic testing.
Jenkins has always had issues of old builds hanging around the cluster
and causing unreproducible flakes.
FYI, infra are giving their blessing to people trying it out.
http://mail-archives.apache.org/mod_mbox/www-builds/201908.mbox/%3cd425ae5c-7977-7aed-7fd8-ef63a6c0a850@apache.org%3e
-Ivan
On Mon, Aug 26, 2019 at 9:50 PM Sijie Guo <gu...@gmail.com> wrote:
>
> The results look promising.
>
> +1
>
> - Sijie
>
> On Mon, Aug 26, 2019 at 1:37 PM Ali Ahmed <al...@gmail.com> wrote:
>
> > I have finished by poc with Github actions. I propose we disable the
> > jenkins pr check in jobs with this. The benefits are more stable test
runs
> > and more available resources to instantly start running checkin jobs.
> >
> > The experimental PR is here.
> > https://github.com/apache/pulsar/pull/5035
> >
> > We should be able to do the migration very quickly.
> >
> > -Ali
> >
Re: Jenkins migration proposal
Posted by Ivan Kelly <iv...@apache.org>.
+1 for moving to actions. It looks to be azure pipelines in
background. It should be able to give us more hermetic testing.
Jenkins has always had issues of old builds hanging around the cluster
and causing unreproducible flakes.
FYI, infra are giving their blessing to people trying it out.
http://mail-archives.apache.org/mod_mbox/www-builds/201908.mbox/%3cd425ae5c-7977-7aed-7fd8-ef63a6c0a850@apache.org%3e
-Ivan
On Mon, Aug 26, 2019 at 9:50 PM Sijie Guo <gu...@gmail.com> wrote:
>
> The results look promising.
>
> +1
>
> - Sijie
>
> On Mon, Aug 26, 2019 at 1:37 PM Ali Ahmed <al...@gmail.com> wrote:
>
> > I have finished by poc with Github actions. I propose we disable the
> > jenkins pr check in jobs with this. The benefits are more stable test runs
> > and more available resources to instantly start running checkin jobs.
> >
> > The experimental PR is here.
> > https://github.com/apache/pulsar/pull/5035
> >
> > We should be able to do the migration very quickly.
> >
> > -Ali
> >
Re: Jenkins migration proposal
Posted by Sijie Guo <gu...@gmail.com>.
The results look promising.
+1
- Sijie
On Mon, Aug 26, 2019 at 1:37 PM Ali Ahmed <al...@gmail.com> wrote:
> I have finished by poc with Github actions. I propose we disable the
> jenkins pr check in jobs with this. The benefits are more stable test runs
> and more available resources to instantly start running checkin jobs.
>
> The experimental PR is here.
> https://github.com/apache/pulsar/pull/5035
>
> We should be able to do the migration very quickly.
>
> -Ali
>