All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Barth <msbarth@linux.vnet.ibm.com>
To: Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Andrew Geissler <geissonator@gmail.com>
Subject: Re: Jenkins job for per-repository CI
Date: Mon, 21 Nov 2016 09:39:32 -0600	[thread overview]
Message-ID: <5eaf3cc0-2da9-dbeb-b641-92436b647b1d@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACPK8Xd10-XSAsqBGhyaKQYfA0YLNZ00qFuW_ocASkXZA=qd_Q@mail.gmail.com>

Hey Joel,

On 11/20/2016 06:47 PM, Joel Stanley wrote:
> Hi Matt,
>
> You need to set your username in Thunderbird. I also recommend not top
> posting and disabling HTML mail when sending to mailing lists.
>
Thanks for the pointers, think I fixed things on this now.
> On Sat, Nov 19, 2016 at 8:09 AM, Andrew Geissler <geissonator@gmail.com> wrote:
>> Matt Barth is working a story to use his new auto tools capabilities
>> in each of our repo's to do "make check" calls when code is committed.
>
> Cool! I assume make check will be used by developers on the local
> machines too. I think it's important that our development process is
> as frictionaless as possible. To that end, someone should be able to
> git clone && autoreconf && ./configure && make check wherever
> possible.
>
Correct, this should be able to be done by developers on local machines 
within a x86_64(most likely) SDK or without a SDK if all the 
dependencies are met.
> This is harder for projects that have cross-project dependencies. How
> are you handling these cases?
>
At this time, the dependencies will be up to the developer when 
attempting to run locally(SDK or not). There's likely some work still to 
be done here where ./configure should report any missing dependencies 
for the developer to correct.
On the Jenkins automation side, I'm working on a script to parse 
configure.ac in determining what dependencies need to be installed 
within the docker image prior to running the unit tests. This is a work 
in progress at the moment and will possibly cause updates to each repo's 
configure.ac file to better define the dependencies.
> Do you have any code for us to look at?
>
There's a couple commits in gerrit for the Jenkin's scripts to build and 
run the docker image and I'm working on the script that runs within the 
docker image to determine these dependencies now.
https://gerrit.openbmc-project.xyz/#/c/1103/
https://gerrit.openbmc-project.xyz/#/c/1230/
> Cheers,
>
> Joel
>
Matt

      reply	other threads:[~2016-11-21 15:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 21:39 Jenkins job for per-repository CI Andrew Geissler
2016-11-18 22:54 ` Patrick Williams
2016-11-18 23:50   ` msbarth
2016-11-21  0:47 ` Joel Stanley
2016-11-21 15:39   ` Matt Barth [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5eaf3cc0-2da9-dbeb-b641-92436b647b1d@linux.vnet.ibm.com \
    --to=msbarth@linux.vnet.ibm.com \
    --cc=geissonator@gmail.com \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.