From owner-freebsd-testing@FreeBSD.ORG Thu Apr 17 09:35:14 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2C314698; Thu, 17 Apr 2014 09:35:14 +0000 (UTC) Received: from acme.spoerlein.net (unknown [IPv6:2a02:2528:fa:1000::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.spoerlein.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AE5512D8; Thu, 17 Apr 2014 09:35:13 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a02:2528:fa:1000::1]) by acme.spoerlein.net (8.14.8/8.14.7) with ESMTP id s3H9Z9Ac090804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 17 Apr 2014 11:35:10 +0200 (CEST) (envelope-from uqs@FreeBSD.org) Date: Thu, 17 Apr 2014 11:35:09 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Craig Rodrigues Subject: Re: Coverity scans on Jenkins Message-ID: <20140417093509.GA3620@acme.spoerlein.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "freebsd-testing@freebsd.org" X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2014 09:35:14 -0000 No BSDCan for me this year, I'll be on the road: http://igg.me/at/aor2014/x/5664674 So do I need a special account to get the scripts and coverity binaries uploaded? 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. Cheers, Uli 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 https://jenkins.freebsd.org , 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: > https://wiki.freebsd.org/Jenkins#Presentations_and_Working_Groups > > -- > Craig > > On Tue, Apr 15, 2014 at 10:43 AM, Ulrich Spörlein 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 scan.coverity.com. > > > > 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@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-testing > > To unsubscribe, send any mail to "freebsd-testing-unsubscribe@freebsd.org"