In Travis-CI, you can say "java-ea", what is the equivalent in GitHub?

Gary

On Wed, Jul 1, 2020 at 9:33 AM Matt Sicker <[email protected]> wrote:

> I’ll take a look this week sometime. I’m in support of everything said
> here, too. This should help the PR testing feature actually work again!
>
> On Wed, Jul 1, 2020 at 06:49 Volkan Yazıcı <[email protected]>
> wrote:
>
> > Hello,
> >
> > I have pulled this off in my local repo and created a PR[1]. If there
> > are no objections, I really would like to get this merged. Once this
> > lifts off, I am inclined to drop the Travis CI. Would anybody mind
> > reviewing the PR, please? (Note that the change set updates the Maven
> > Wrapper scripts too.)
> >
> > Cheers!
> >
> > [1] https://github.com/apache/logging-log4j2/pull/379
> >
> > On Mon, Jan 20, 2020 at 9:40 PM Volkan Yazıcı <[email protected]>
> > wrote:
> > >
> > > Given GitHub has introduced its own CI, i.e., GitHub Actions, would
> > > you consider migrating from Travis CI to that? In its current form,
> > > setup-java[1] doesn't support multiple JDKs, but I think it can be
> > > worked around. If the rest of the people would agree, I will create a
> > > ticket for that and work on it after "replacing JsonLayout with
> > > LogstashLayout" task, which I am currently busy right now.
> > >
> > > Advantages? Technically none, socially a more GitHub-friendly project
> > setup.
> > >
> > > [1] https://github.com/actions/setup-java/
> >
> --
> Matt Sicker <[email protected]>
>

Reply via email to