Many of those types of tools also have the ability to only report a subset of
their problems. Since most teams won't attempt to fix thousands of warnings,
you might be better only having the tool report the set of warnings you think
are most valuable to fix.
As an example, I've used a findbugs
Hi,
the static analysis plugins hold their state in Maps. At least this has
been the state of affairs last tie i looked. Kohsuke supplied patches
that reduce this amount but when you have the count of warnings you
mentioned it is simply a problem of allocating memory to your
application server ins
Forgot to mention that JENKINS_HOME was pointing to an EXT4 filesystem
created with:
mke2fs -t ext4 -F /dev/vg0/jenkins
Hi,
I'm running Jenkins as a daemon on Amazon Linux (standalone on winstone).
I changed JENKINS_HOME (/etc/sysconfig/jenkins) to point to "*/jenkins"*instead
of "
*/var/lib/jenkins".*
The "*/jenkins*" directory is a new mount based on an EBS volume attached
(/dev/sda1) to the EC2 instance.
Ever
Have you enabled the "block when upstream/downstream is running" options in
the advanced section of the job config.
As this will normally keep multiple jobs in a chain, only allowing a single
job to be running at a time.
I have used these options to run a chain of 5-6 jobs run on multiple
sla
parallel expect a set of closures, each closure being ran in a separate
thread :
parallel( { build(A) },
{ build(B) }
)
2012/11/9 r2_
> Hey, I got a really cool looking error using Build Flow Plugin. The flow
> is just 2 parameterized jobs which should run in parallel on different
