From: Doug Goldstein <cardoe@cardoe.com>
To: xen-devel@lists.xen.org
Cc: Keir Fraser <keir@xen.org>, Doug Goldstein <cardoe@cardoe.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH 1/3] travis: skip building coverity, smoke, and master
Date: Fri, 4 Mar 2016 08:46:05 -0600 [thread overview]
Message-ID: <1457102767-3012-1-git-send-email-cardoe@cardoe.com> (raw)
Skip building of the coverity, smoke and master branches since they just
fast forward from staging.
Suggested-by: Andrew Cooper <andrew.cooper3@citrix.com>
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
---
CC: Ian Jackson <ian.jackson@eu.citrix.com>
CC: Jan Beulich <jbeulich@suse.com>
CC: Keir Fraser <keir@xen.org>
CC: Tim Deegan <tim@xen.org>
CC: Andrew Cooper <andrew.cooper3@citrix.com>
---
.travis.yml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index 6693af2..74fa14e 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,6 +1,12 @@
language: c
dist: trusty
sudo: required
+# don't test master, smoke and coverity branches
+branches:
+ except:
+ - master
+ - smoke
+ - coverity-tested/master
matrix:
include:
- compiler: gcc
--
2.4.10
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-03-04 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 14:46 Doug Goldstein [this message]
2016-03-04 14:46 ` [PATCH 2/3] travis: use matching C++ for GCC version Doug Goldstein
2016-03-04 14:46 ` [PATCH 3/3] travis: actually disable debug for non-debug Doug Goldstein
2016-03-04 15:56 ` Doug Goldstein
2016-03-04 18:28 ` Doug Goldstein
2016-03-04 15:30 ` [PATCH 1/3] travis: skip building coverity, smoke, and master Andrew Cooper
2016-03-04 15:53 ` Doug Goldstein
2016-03-04 15:48 ` Jan Beulich
2016-03-04 15:52 ` Doug Goldstein
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=1457102767-3012-1-git-send-email-cardoe@cardoe.com \
--to=cardoe@cardoe.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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.