From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com, ian.jackson@eu.citrix.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com
Subject: [PATCH v7 0/2] OSSTEST: introduce a raisin build test
Date: Mon, 22 Jun 2015 16:15:30 +0100 [thread overview]
Message-ID: <alpine.DEB.2.02.1506221610500.21829@kaball.uk.xensource.com> (raw)
Hi all,
the first patch introduces a Raisin build job, meant to test Raisin
itself. The second patch push-gates Raisin on successful builds.
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Changes in v7:
- update raisin git url after http://marc.info/?l=xen-devel&m=143472251602803
- add a patch to push-gate raisin
Changes in v6:
- move divide to Osstest/BuildSupport.pm and rename it to
divide_xen_build; use divide_xen_build in ts-raisin-build and
ts-xen-build.
Changes in v5:
- remove setting DEFAULT_REVISION_RAISIN to master
- disable raisin when branch is not xen*
- do not overwrite raisin default variables unless both revision_* and
tree_* are set of a given component
Changes in v4:
- introduce enable_raisin in mfi-common: only build raisin when building
xen-unstable
- start off from the default raisin config, then append osstest config
options to it
- do not write variable to the raisin config if the conrresponding
runvar is not set
- remove TREE_OVMF and TREE_SEABIOS
Changes in v3:
- use $raisindir throughout ts-raisin-build
- do not specify ENABLED_COMPONENTS so that empty REVISION variables can
be used to disable building a raisin component
Changes in v2:
- set revision_* variables in mfi-common;
- in ts-raisin-build set the *_REVISION config options based on the
revision_* variables;
- in ts-raisin-build, call store_revision appropriately;
- divide the output in an hypervisor and a tools tarball.
Stefano Stabellini (2):
OSSTEST: introduce a raisin build test
OSSTest: push successful raisin builds
Osstest/BuildSupport.pm | 48 +++++++++++++++++
ap-common | 5 ++
ap-fetch-version | 3 ++
ap-fetch-version-old | 5 ++
ap-print-url | 3 ++
ap-push | 5 ++
cr-daily-branch | 8 +++
cri-common | 1 +
mfi-common | 41 +++++++++++++++
sg-run-job | 5 ++
ts-raisin-build | 133 +++++++++++++++++++++++++++++++++++++++++++++++
ts-xen-build | 44 +---------------
12 files changed, 259 insertions(+), 42 deletions(-)
create mode 100755 ts-raisin-build
next reply other threads:[~2015-06-22 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 15:15 Stefano Stabellini [this message]
2015-06-22 15:16 ` [PATCH v7 1/2] OSSTEST: introduce a raisin build test Stefano Stabellini
2015-07-09 15:33 ` Ian Campbell
2015-07-20 12:56 ` Stefano Stabellini
2015-07-20 13:20 ` Ian Campbell
2015-07-20 13:55 ` Ian Jackson
2015-06-22 15:16 ` [PATCH v7 2/2] OSSTest: push successful raisin builds Stefano Stabellini
2015-07-09 15:39 ` Ian Campbell
2015-07-20 13:41 ` Stefano Stabellini
2015-07-20 13:46 ` 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=alpine.DEB.2.02.1506221610500.21829@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@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.