All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH v4 11/11] osstest: add FreeBSD build recipe
Date: Thu, 19 Mar 2015 15:31:21 +0000	[thread overview]
Message-ID: <1426779081.21742.43.camel@citrix.com> (raw)
In-Reply-To: <1424276291-6872-12-git-send-email-roger.pau@citrix.com>

On Wed, 2015-02-18 at 17:18 +0100, Roger Pau Monne wrote:
> This patch introduces two new buildjobs:
> 
> build-<arch>-freebsd-xen: sets up a FreeBSD host and builds Xen.
> build-<arch>-freebsd-freebsd: sets up a FreeBSD host and builds FreeBSD sets
> and a mfsBSD installer image.

Not sure why this is dodgy, it doesn't look too bad to me.

One thought I had all the way through this is that its a bit wrong that
ts-xen-{install,build} and ts-kernel-build are actually
ts-xen-{install,build}-linux and ts-linux-build.

Renaming those script would allow some of the iffs you are added to be
replace with do-a-thing-$os.

A little care would be needed so that the testid doesn't change, but
that's might be a good thing, since having the testid be host-install
regardless of the OS being installed would make things a bit more
readable IMHO (e.g. in the summary grid).

Perhaps the way to achieve that is to make ts-xen-build be:
    #!/bin/bash
    set -ex
    os=$1;shift
    exec ts-xen-build-$1 $@

Then things like:
    per-host-ts broken  host-install/@(*) ts-host-install + $os
    per-host-ts .       xen-install/@     ts-xen-install + $os

(the + makes the $os not be in the test id)

Ian.

      reply	other threads:[~2015-03-19 15:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 16:18 [PATCH v4 00/11] osstest: add a FreeBSD host Roger Pau Monne
2015-02-18 16:18 ` [PATCH v4 01/11] osstest: allow to disable the usage of a know_host file Roger Pau Monne
2015-03-19 14:52   ` Ian Campbell
2015-02-18 16:18 ` [PATCH v4 02/11] osstest: add routine to execute ssh with password Roger Pau Monne
2015-03-19 14:58   ` Ian Campbell
2015-02-18 16:18 ` [PATCH v4 03/11] osstest: store a path runvar for built_stash_file Roger Pau Monne
2015-03-19 15:01   ` Ian Campbell
2015-02-18 16:18 ` [PATCH v4 04/11] osstest: add support for installing bare metal FreeBSD Roger Pau Monne
2015-03-19 15:13   ` Ian Campbell
2015-02-18 16:18 ` [PATCH v4 05/11] osstest: add script for building custom mfsBSD images Roger Pau Monne
2015-03-19 15:16   ` Ian Campbell
2015-02-18 16:18 ` [PATCH v4 06/11] osstest: fix ts-build-check to work with freebsd_buildjob Roger Pau Monne
2015-02-18 16:18 ` [PATCH v4 07/11] osstest: add freebsd installer update script Roger Pau Monne
2015-02-18 16:18 ` [PATCH v4 08/11] osstest: prepare FreeBSD host for Xen build Roger Pau Monne
2015-03-19 15:18   ` Ian Campbell
2015-02-18 16:18 ` [PATCH v4 09/11] osstest: make ts-xen-build work on FreeBSD Roger Pau Monne
2015-03-19 15:20   ` Ian Campbell
2015-02-18 16:18 ` [PATCH v4 10/11] osstest: add a script to install Xen on FreeBSD hosts Roger Pau Monne
2015-03-19 15:24   ` Ian Campbell
2015-02-18 16:18 ` [PATCH v4 11/11] osstest: add FreeBSD build recipe Roger Pau Monne
2015-03-19 15:31   ` Ian Campbell [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=1426779081.21742.43.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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.