Coverity scans on Jenkins

Ulrich Spörlein uqs at
Thu Apr 17 09:35:14 UTC 2014

No BSDCan for me this year, I'll be on the road:

So do I need a special account to get the scripts and coverity binaries

I know we use LDAP now at the cluster, but I've never set up a password,
how would I do that?

A new VM might be easier, as it requires special setup with the coverity
binaries and curl, etc.


On Tue, 2014-04-15 at 11:10:56 -0700, Craig Rodrigues wrote:
> Hi,
> Yes, what you want is totally doable.
> If you look at , you will see that
> we have several bhyve VM's that build several src branches,
> and we also have several builds that use poudriere to build ports.
> We can set up another build configuration, either in an existing VM, or a new
> VM, to run your scripts once a week.
> Will you be at BSDCan?  There is a working group on May 15 where it would
> be a good place to coordinate on this:
> --
> Craig
> On Tue, Apr 15, 2014 at 10:43 AM, Ulrich Spörlein <uspoerlein at> wrote:
> > Hey all
> >
> > so how do I get on this CI bandwagon? I have some scripts that set up
> > the coverity environment (a one-time thing) then those should run at
> > most once per week (preferably when -CURRENT is actually building) and
> > then tar up the results and upload them to
> >
> > As there are some passwords/tokens that are required for the upload,
> > I'd like it if not all of the scripts are visible to everyone that has
> > a Jenkins account.
> >
> > Is that possible?
> >
> > Cheers,
> > Uli
> > _______________________________________________
> > freebsd-testing at mailing list
> >
> > To unsubscribe, send any mail to "freebsd-testing-unsubscribe at"

More information about the freebsd-testing mailing list