| Re: [glassfish-dev] Question about nightly builds and running TCKs |
|
Hi, 3). Yes, the https://ci.eclipse.org/glassfish/job/cditck-porting is the pipeline job (corresponding to the Jenkinsfile) that needs to be triggered to run the cdi TCK using the porting kit. Currently we can select the "CDI_PORTING_TCK" option in the job
https://ci.eclipse.org/jakartaee-tck/job/standalonetck-nightly-build-run-master
to trigger the above pipeline job that will build
the portingkit and run
the cdi tck. By default, it picks the CDI TCK from
http://download.eclipse.org/ee4j/cdi/cdi-tck-2.0.6-dist.zip. Regards, On 20/04/20 5:25 PM, Steve Millidge
(Payara) wrote:
Hi Martin, Some answers; 1) Currently you will have to checkout and build master for current builds or take it from Jenkins which is building master https://ci.eclipse.org/glassfish/job/glassfish/job/master/lastSuccessfulBuild/artifact/bundles/glassfish.zip. Currently I would call this unstable as we are in the middle of moving to the Jakarta namespace and a number of tests fail. Our current test of quality for merging PRs is that the code compiles! 2) For upgrading Weld you can just copy the latest Weld jar into the glassfish modules directory and restart glassfish as you describe. However if you want to test Jakarta namespace change then there is a bunch of code within GlassFish that will need to be changed. I have an in progress branch to do these changes but is expanding day by day and hitting blockers on other upstream projects day by day. Currently it is blocked on Weld (chicken and egg). 3) Jenkins has jobs to run the TCK https://ci.eclipse.org/glassfish/job/cditck-porting/ I think this is the correct one but I'm not sure. I wasn't involved in the GlassFish 5.1 release so didn't set these jobs up. Perhaps someone form Oracle on the GF team is more familiar with (3). Steve -----Original Message----- From: glassfish-dev-bounces@xxxxxxxxxxx <glassfish-dev-bounces@xxxxxxxxxxx> On Behalf Of Matej Novotny Sent: 17 April 2020 09:33 To: glassfish-dev@xxxxxxxxxxx Cc: Martin Kouba <mkouba@xxxxxxxxxx> Subject: [glassfish-dev] Fwd: Question about nightly builds and running TCKs Hello, I am from Weld team and I recently started looking into adapting Weld for Jakarta 9. Since GF is the only server that will early on adapt this, I will want to swap our testing (Jenkins) towards GF so that we have some incontainer test coverage. And I am missing some bits that I hope you can point me towards: 1) Where can I get some latest GF build and how "new" and stable is that build - basically looking for a place where jenkins can grab some nightly/weekly snapshot of GF to work with 2) How do you swap a component version inside; e.g. how do I upgrade Weld inside GF? - I know this used to be just about copying the osgi bundle into "glassfish/modules", is that still the case? 3) How do you run CDI TCK with GF? - we used to have a setup which leveraged weld-glassfish-runner[1] but that wasn't used for some time and I recall some errors last time I tried - how do you run TCKs? Is there some public jenkins job where this can be seen? Best regards Matej ___________________________________________________________________________________________________________ [1] https://github.com/weld/weld-glassfish-tck-runner _______________________________________________ glassfish-dev mailing list glassfish-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev _______________________________________________ glassfish-dev mailing list glassfish-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev |