From: Ian Campbell <ian.campbell@citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST 3/4] ts-devstack: Deploy OpenStack then test it with Tempest
Date: Fri, 17 Jul 2015 17:10:18 +0100 [thread overview]
Message-ID: <1437149418.22698.16.camel@citrix.com> (raw)
In-Reply-To: <1437045519-13914-4-git-send-email-anthony.perard@citrix.com>
On Thu, 2015-07-16 at 12:18 +0100, Anthony PERARD wrote:
> +sub deploy() {
> + # This clone many repos and may take sometime until the GitProxyCache is
> + # filled
Can we find those repos and therefore record the version actual in use
via store_vcs_revision?
Even without the ability to control which things get used I think this
would be useful data to have when looking into errors etc...
next prev parent reply other threads:[~2015-07-17 16:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 11:18 [PATCH OSSTEST 0/4] Have OpenStack tested on top of xen's master and libvirt's master Anthony PERARD
2015-07-16 11:18 ` [PATCH OSSTEST 1/4] ts-kernel-build: Enable CONFIG_NETFILTER_XT_TARGET_CHECKSUM Anthony PERARD
2015-07-17 15:48 ` Ian Campbell
2015-07-16 11:18 ` [PATCH OSSTEST 2/4] Toolstack: Add OpenStack as a toolstack Anthony PERARD
2015-07-17 15:58 ` Ian Campbell
2015-07-17 16:32 ` Anthony PERARD
2015-07-17 16:45 ` Ian Campbell
2015-07-16 11:18 ` [PATCH OSSTEST 3/4] ts-devstack: Deploy OpenStack then test it with Tempest Anthony PERARD
2015-07-17 16:04 ` Ian Campbell
2015-07-20 14:12 ` Anthony PERARD
2015-07-20 14:31 ` Ian Campbell
2015-07-17 16:10 ` Ian Campbell [this message]
2015-07-20 14:16 ` Anthony PERARD
2015-07-16 11:18 ` [PATCH OSSTEST 4/4] Create a flight to test OpenStack with xen-unstable and libvirt Anthony PERARD
2015-07-17 16:08 ` Ian Campbell
2015-07-17 15:51 ` [PATCH OSSTEST 0/4] Have OpenStack tested on top of xen's master and libvirt's master Ian Campbell
2015-07-17 16:22 ` Ian Campbell
2015-07-20 15:07 ` Anthony PERARD
2015-07-20 15:27 ` Ian Jackson
2015-07-20 15:35 ` 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=1437149418.22698.16.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=anthony.perard@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.