My suggestion is that we can submit a initial working setup on
single
environment(jdk8, for example), to make it start working, and then
gradually evolving our setup until we can get rid of TravisCI.
@Alessio Soldano @Ronald Sigal wdyt?
On Tue, Apr 21, 2020 at 11:34 PM James Perkins <jperkins(a)redhat.com> wrote:
> Hello All,
> I've submitted a draft for an example of how we could use GitHub Actions to run
CI. The main benefit over TravisCI is we can run Windows jobs as well. I'm curious
what others think of this approach.
>
> One thing to note is I've seen some issues, especially on Java 8 on Windows, with
the resteasy-jdk-http tests. We may need to ignore the test in that environment which I
can make a change to do if we notice it being an issue.
>
> There's also another commit I'd like to get in regardless of using GitHub
Actions which allows various tests to pass on other environments such as Windows.
>
> [1]:
https://github.com/resteasy/Resteasy/pull/2362
>
> --
> James R. Perkins
> JBoss by Red Hat
> _______________________________________________
> resteasy-dev mailing list
> resteasy-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/resteasy-dev