No response to any of the posts in particular, just a general thought/proposal.
I can appreciate that the ComplexScripts branch requires a clean FB report so
that Glenn is not continuously sent on a wild goose chase.
However, personally (and Vincent seems to agree), I do not favor 'blind'
I think the existing exclusions should be left in trunk, and that no new
ones should be permitted in (or should be fixed immediately). If you do as
you suggest below, then the list of findbugs errors will just continue to
grow because nobody will pay attention to them.
We are at a known, stable
in a
headless configuration, hence I had to disable many junit tests. At
nightly builds there is no one to check checkstyle and findbugs errors
and warnings; therefore there is no point in running them.
Simon
in a
headless configuration, hence I had to disable many junit tests. At
nightly builds there is no one to check checkstyle and findbugs errors
and warnings; therefore there is no point in running them.
Simon
.
Many junit tests require a display. Nightly builds are run in a
headless configuration, hence I had to disable many junit tests. At
nightly builds there is no one to check checkstyle and findbugs errors
and warnings; therefore there is no point in running them.
Simon
.
Many junit tests require a display. Nightly builds are run in a
headless configuration, hence I had to disable many junit tests. At
nightly builds there is no one to check checkstyle and findbugs errors
and warnings; therefore there is no point in running them.
Simon
:
I notice also that the nightly build target does not run all the
junit
tests. It would be better if it run all of them plus checkstyle and
findbugs.
Many junit tests require a display. Nightly builds are run in a
headless configuration, hence I had to disable many junit tests. At
nightly
tests require a display. Nightly builds are run in a
headless configuration, hence I had to disable many junit tests. At
nightly builds there is no one to check checkstyle and findbugs errors
and warnings; therefore there is no point in running them.
Simon
to disable many junit tests. At
nightly builds there is no one to check checkstyle and findbugs errors
and warnings; therefore there is no point in running them.
Simon
Jeremias Maerki
On Wed, Feb 23, 2011 at 01:10:10PM -0700, Glenn Adams wrote:
Right now the nightly build is our CI process.
That is a development-centric point of view. The nightly build is
definitely not a CI process. It is a service to the users, which must
not be interrupted by development concerns. If a
configuration, hence I had to disable many junit tests. At
nightly builds there is no one to check checkstyle and findbugs errors
and warnings; therefore there is no point in running them.
Simon
11 matches
Mail list logo
