From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: [PATCH 0/4] Improve travis-ci integration
Date: Sat, 28 Jul 2018 22:31:19 +0000 [thread overview]
Message-ID: <cover.1532816583.git.marcelo.leitner@gmail.com> (raw)
As now we probe for some kernel features, it is important that we try to
build the library against different kernel headers.
That's what the first patch does.
patch 2 and 3 seize the moment to build using different
compilers/versions and patch 4 minimize emails by only sending build
fail/success if it changes.
Build status can be seen at https://www.travis-ci.org/sctp/lksctp-tools
Marcelo Ricardo Leitner (4):
travis: build against multiple kernel versions
travis: build against multiple gcc versions
travis: build against multiple clang versions
travis: only send notifications if build status changed
.travis.yml | 110 ++++++++++++++++++++++++++++++++++++++---
.travis/linux-build.sh | 43 ++++++++++++++++
2 files changed, 147 insertions(+), 6 deletions(-)
create mode 100755 .travis/linux-build.sh
--
2.17.1
next reply other threads:[~2018-07-28 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 22:31 Marcelo Ricardo Leitner [this message]
2018-07-31 13:25 ` [PATCH 0/4] Improve travis-ci integration Marcelo Ricardo Leitner
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=cover.1532816583.git.marcelo.leitner@gmail.com \
--to=marcelo.leitner@gmail.com \
--cc=linux-sctp@vger.kernel.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.