Re: [ee4j-build] TCK run/GlassFish merge process

[Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>]

Stuart,

We are working now on creating a document describing GlassFish integration process. What you’ve done is right. The second step would be submitting a PR to GlassFish. The first step is to make sure that GlassFish is buildable with your changes locally and quick look tests are passing. Instructions how to run quick look tests are here https://github.com/eclipse-ee4j/glassfish/blob/master/README.md.  

The GF build job and dev tests run job should be run for each PR submitted. I don’t think it’s been setup because we had some problems with Eclipse infra. We are in process of solving it now.

After that CTS must be run and pass on that version of GlassFish. The CTS job itself is there, but we don’t have it automated. If you wish to help, there are some documents and guides about running CTS here: https://github.com/eclipse-ee4j/jakartaee-tck/wiki.

I don’t know why IP check fails, you should contact Eclipse Webmasters, possibly something is wrong with the repository GitHub hooks setup. 

Thanks,

Dmitry

On 19 Nov 2018, at 13:07, Stuart Douglas <sdouglas@xxxxxxxxxx> wrote:

Hi everyone,

I was just wondering what the process is for getting a TCK run/merge to get our staged artifacts into GlassFish? I don't seem to be able to find any docs on this (apologies if they exist and I am just looking in the wrong place).

I have opened https://github.com/eclipse-ee4j/glassfish/pull/22615 which I think is the last think stopping us from releasing as we have a successful release review. Do I just need to be patient or is there something more I need to do to enable this to be merged?

Stuart

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build