You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@yetus.apache.org by Allen Wittenauer <aw...@effectivemachines.com.INVALID> on 2020/08/15 15:48:52 UTC

Move our stuff or just use GitHub actions?

	
With the primary Jenkins shutting down, I guess we should make a decision.  FWIW, I'm perfectly happy to drop Jenkins and use GitHub actions given how many of us run test-patch on Jenkins for our $DAYJOBS.

Thoughts?

Re: Move our stuff or just use GitHub actions?

Posted by Sean Busbey <bu...@apache.org>.

I'm skeptical on capacity, but we don't need much for our own tests iirc.

Let's try it out.

On Wed, Aug 19, 2020, 15:06 Nick Dimiduk <nd...@apache.org> wrote:

> I'm fine with moving to GitHub actions. The experiment you posted up looked
> pretty nice. I'm not clear on how resources are allocated from GitHub, but
> as long as there's capacity, let's try it.
>
> Thanks,
> Nick
>
> On Sat, Aug 15, 2020 at 8:49 AM Allen Wittenauer
> <aw...@effectivemachines.com.invalid> wrote:
>
> >
> > With the primary Jenkins shutting down, I guess we should make a
> > decision.  FWIW, I'm perfectly happy to drop Jenkins and use GitHub
> actions
> > given how many of us run test-patch on Jenkins for our $DAYJOBS.
> >
> > Thoughts?
> >
> >
>

Re: Move our stuff or just use GitHub actions?

Posted by Nick Dimiduk <nd...@apache.org>.

I'm fine with moving to GitHub actions. The experiment you posted up looked
pretty nice. I'm not clear on how resources are allocated from GitHub, but
as long as there's capacity, let's try it.

Thanks,
Nick

On Sat, Aug 15, 2020 at 8:49 AM Allen Wittenauer
<aw...@effectivemachines.com.invalid> wrote:

>
> With the primary Jenkins shutting down, I guess we should make a
> decision.  FWIW, I'm perfectly happy to drop Jenkins and use GitHub actions
> given how many of us run test-patch on Jenkins for our $DAYJOBS.
>
> Thoughts?
>
>