If I understand correctly, there are now two separate build systems being
used--Jenkins, and Travis. The latter is the one that gives a "green light" on
Github's pull request page ("All checks have passed"), but it does not seem to
run any tests. So GitHub pull requests will show a green light even though they
might break the Jenkins build, potentially misleading reviewers and submitters.
Ideally, Github's pull request page would show a failure if a proposed patch
would cause any of the Jenkins builds to fail. That would prevent future pull
requests from breaking the build.
Also note that Jenkins only seems to run tests in modules belonging to the
"platform" cluster. Thus there are many tests that are not run at all by either
Jenkins or Travis, e.g. in the editor and editor.lib/lib2 modules. It would be
great to get the full test suite running on either Jenkins, Travis, or
both--otherwise more and more unexercised tests risk breaking over time without
anyone noticing.
--Eirik
-----Original Message-----
From: Geertjan Wielenga <[email protected]>
Sent: Wednesday, August 22, 2018 3:22 PM
To: dev <[email protected]>
Subject: Failing builds
Hi all,
The builds have been failing for some time:
https://builds.apache.org/job/incubator-netbeans-windows/
https://builds.apache.org/job/incubator-netbeans-linux/
I think before merging more prs, we need to figure out what the reason for
the build failures is.
I'm trying to figure it out, if anyone else can take a look too, that would
help.
Thanks,
Gj
