All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST 2/5] Handle osstest's own local push gate in non-master production instances
Date: Thu, 2 Apr 2015 12:13:05 +0100	[thread overview]
Message-ID: <21789.9281.449911.318689@mariner.uk.xensource.com> (raw)
In-Reply-To: <1427901022-24314-2-git-send-email-ian.campbell@citrix.com>

Ian Campbell writes ("[PATCH OSSTEST 2/5] Handle osstest's own local push gate in non-master production instances"):
> We want to arrange that the master XenProject instance continues to
> test its own pretest branch while any downstream instances will pickup
> changes from the master instance's production (i.e. tested) branch,
> which is published at git://xenbits.xen.org/osstest.git#master.
...	;;
>  osstest)
> -	if [ "x$OSSTEST_USE_HEAD" != "xy" ] ; then
> +	if [ x"$TREEBRANCH_OSSTEST_UPSTREAM" != x ] ; then

Shouldn't the OSSTEST_USE_HEAD option override this ?  Ie I think this
is the wrong way round.

> +	    OSSTEST_REVISION_MERGE=`repo_tree_rev_fetch_git osstest \
> +		$TREEBRANCH_OSSTEST_UPSTREAM $LOCALREV_OVMF`

OSSTEST_REVISION_MERGE doesn't seem to be an environment variable.  I
think it should either be honoured if pre-set, or just be an ordinary
(lowercase) variable name (in which case it doesn't need the OSSTEST
prefix).

> +	    echo >&2 "$TREEBRANCH_OSSTEST_UPSTREAM = $OSSTEST_REVISION_MERGE"
> +
> +	    rm -rf $repos/osstest-merge >&2
> +	    git clone -b pretest $HOME/testing.git $repos/osstest-merge >&2
> +
> +	    git -C $repos/osstest-merge \
> +		fetch $repos/osstest $LOCALREV_OVMF:ap-merge >&2

LOCALREV_OVMF (here and earlier).  It's not clear to me that you
actually need to indirect it; you could just specify a branch name.

The rest looks fine.

Having thought about how to override things, particularly:

> +	if [ x"$TREEBRANCH_OSSTEST_UPSTREAM" != x ] ; then
> +	    # could push to instance specific location, but
> +	    # certainly not to master instance's xenbits repo!
> +	    :
> +	else

I think ap-fetch-* and ap-push should have a general purpose hook
which occurs just after ap-common is loaded, something like this:

  diff --git a/ap-fetch-version b/ap-fetch-version
  index 33aaf00..a3028f6 100755
  --- a/ap-fetch-version
  +++ b/ap-fetch-version
  @@ -31,6 +31,8 @@ if info_linux_tree "$branch"; then
          exit 0
   fi

  +. ${OSSTEST_HOOK_AP_FETCH-/dev/null}
  +
   case "$branch" in
   xen-3.*)
          ./sg-hg-heads sh -ec '

We can postpone actually writing that until someone needs it.

Ian.

  reply	other threads:[~2015-04-02 11:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 15:09 [PATCH OSSTEST 0/5] Tweaks to allow running non-master production instances Ian Campbell
2015-04-01 15:10 ` [PATCH OSSTEST 1/5] cri-args-hostslists: allow instance specific settings Ian Campbell
2015-04-02 10:52   ` Ian Jackson
2015-04-01 15:10 ` [PATCH OSSTEST 2/5] Handle osstest's own local push gate in non-master production instances Ian Campbell
2015-04-02 11:13   ` Ian Jackson [this message]
2015-04-02 11:21     ` Ian Campbell
2015-04-01 15:10 ` [PATCH OSSTEST 3/5] cambridge: Add a crontab Ian Campbell
2015-04-02 11:13   ` Ian Jackson
2015-04-01 15:10 ` [PATCH OSSTEST 4/5] cambridge: Do not try to push harness to XenProject instance output Ian Campbell
2015-04-02 11:13   ` Ian Jackson
2015-04-01 15:10 ` [PATCH OSSTEST 5/5] cambridge: Stop publishing logs to chiark Ian Campbell
2015-04-02 11:16   ` Ian Jackson
2015-04-02 11:25     ` Ian Campbell
2015-04-02 15:34       ` Ian Campbell

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=21789.9281.449911.318689@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=xen-devel@lists.xen.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.