@Richard Zowalla, In terms of Jenkis job configuration, what is your Job configuration set up in the University?
Current Apache TomEE master job has the following configurations: -Java: latest Java 8 -Maven: 3.3.9 version with MAVEN_OPTS -Xmx1536m -Maven command: -U --show-version --fail-at-end clean install -Pall-adapters -Junit patter for post-build actions: **/target/surefire-reports/TEST-*.xml Buildbot had 3 steps (temp folder creation, checkstyle, pmd, install without test) before executing the full project tests. https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/1426 I wonder if you included the same steps build bot has or if you went straight to `clean install` like the Job we currently have in Apache CI Job. El mié., 18 nov. 2020 a las 5:12, Jonathan Gallimore (< [email protected]>) escribió: > I'll dig into the log... thanks for the pointers. Its too bad that Jenkins > shows the modules in a weird order though. Things like that add to my > frustration with it. > > Jon > > On Wed, Nov 18, 2020 at 9:06 AM Zowalla, Richard < > [email protected]> wrote: > >> Hi Jon, >> >> the module order shown on the start page does not necessarily reflect the >> build order. >> >> We are building TomEE Master from GitHub on our university Jenkins CI >> infrastructure as well. >> >> Afaik, the module order is hidden in the CI log files: >> >> CI University: >> https://gist.github.com/rzo1/aded63855dbabda57ab11a89188ada68 >> CI Apache: https://gist.github.com/rzo1/0fe6cb8c67fab5ded2ab566e30b7a4e3 >> >> Looking at both CI logs, the build order is: >> >> Core >> Assembly >> Zips >> Integration >> >> as one would expect or did I miss something, Jon? >> >> Best >> Richard >> >> FYI: The latest CI Job on our infrastructure failed with 10 tests (tck >> beanvalidation): >> https://gist.github.com/rzo1/05ff7f30c034c66355cb95363b35686f >> >> Am Dienstag, den 17.11.2020, 22:42 +0000 schrieb Jonathan Gallimore: >> >> I'll keep working on this. I got a clean build on my machine here (which >> >> takes just under 2 hours), and have gotten a release up for vote. We're >> >> definitely seeing 'odd' things on this instance. >> >> >> Jon >> >> >> On Tue, Nov 17, 2020 at 9:32 PM David Blevins < >> >> [email protected] >> >> > >> >> wrote: >> >> >> On Nov 17, 2020, at 1:50 AM, Jonathan Gallimore < >> >> [email protected] >> >> > wrote: >> >> >> I kicked off a run of this last night: >> >> https://ci-builds.apache.org/job/Tomee/job/master/10/ >> >> - which completed >> >> (it >> >> was hanging before), with 38 test failures, looking to be OWB related. >> >> The >> >> tests I've looked at so far locally pass ok - I'm wondering if this is >> >> specific to Jenkins, or timing related (as the build went past midnight, >> >> and so old snapshots may be picked up. >> >> >> Kicked off another full build on Jenkins, and also a full build locally >> >> (which take about half the time of the CI). I'll report back. >> >> >> I tried some time ago to set us up in the Apache setup for Jenkins and got >> >> failures along with a very not intuitive reactor order. >> >> >> For example, in module order from this build: >> >> >> - >> >> https://ci-builds.apache.org/job/Tomee/job/master/10/ >> >> >> >> This is not a complete summary, but a highlight the most odd ordering I >> >> see: >> >> >> Unstable TomEE :: Arquillian Adaptors Parent :: Tests :: Web Profile >> >> 29 min >> >> ... >> >> Success TomEE :: TomEE :: Apache TomEE 1 min 53 sec >> >> ... >> >> Success TomEE :: Assembly 3.6 sec >> >> ... >> >> Success TomEE :: Container :: Core >> >> >> The above is the opposite of what I'd expect, which is: >> >> >> - Build the core code (TomEE :: Container :: Core) >> >> - Assemble the webapps (TomEE :: Assembly) >> >> - Create the Apache TomEE distribution zips (TomEE :: TomEE :: Apache >> >> TomEE) >> >> - Integration test the zips (TomEE :: Arquillian Adaptors Parent :: Tests >> >> :: Web Profile) >> >> >> Instead we have: >> >> >> - Test the zips we haven't built yet >> >> - Build the zips from webapps we haven't created yet >> >> - Build the webapps from code we haven't compiled yet >> >> - Now compile the code >> >> >> It's completely baffling. We get the correct order on our machines and in >> >> buildbot. It's just this Jenkins that seems to create such a completely >> >> unintelligible result. >> >> >> It's like there is some invisible setting or "optimization" enabled. >> >> >> >> -David >> >> >> >> -- >> >> Richard Zowalla, M.Sc. >> Research Associate, PhD Student | Medical Informatics >> >> >> >> Hochschule Heilbronn – University of Applied Sciences >> Max-Planck-Str. 39 >> D-74081 Heilbronn >> phone: +49 7131 504 6791 >> mail: [email protected] >> web: http://www.mi.hs-heilbronn.de/ >> > -- Atentamente: César Hernández.
