From: Loic Dachary <loic@dachary.org>
To: Alfredo Deza <alfredo.deza@inktank.com>, Ken Dreyer <kdreyer@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Running make check on each pull requests via jenkins
Date: Sat, 13 Dec 2014 19:56:27 +0100 [thread overview]
Message-ID: <548C8BDB.8010806@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]
Hi Alfredo & Ken,
After a week of testing/fixing, I think http://workbench.dachary.org/ceph/ceph/blob/master/run-make-check.sh is ready to be used for CI. If I'm not mistaken, the next steps are to:
a) add a jenkins slave on a machine
b) add a build script to https://github.com/ceph/ceph-build
c) schedule a new job on http://jenkins.ceph.com/ with something like https://github.com/ceph/ceph-build/pull/35
The only part I'm unclear about is the jenkins slave. The test I did were on a fedora 20 and ubuntu 14.04 and it would be better (as a first step) if there was just a single slave running one of these two operating systems. It will make it easier to diagnose problems.
The build script could be something like (module the pastebinit if jenkins can handle up to 100,000 lines of output).
export PATH=$HOME:/usr/local/bin:$PATH
author=$(git log -1 --pretty='%ae')
if test -z "$(git log -1 --pretty='%H' --author $author master)" ; then
git log -1
echo "Ignored because $author has no previous commit in master"
exit 0
fi
sudo $(which apt-get yum zypper 2>/dev/null) install -y pastebinit
if run-make-check.sh > output 2>&1 ; then
success=true
else
success=false
fi
# because of https://gitlab.com/gitlab-org/gitlab-ci/issues/71
url=$(pastebinit -b http://paste.ubuntu.com/ output)
commit=$(git rev-parse HEAD)
if $success ; then
message="SUCCESS: make check on $commit output is $url"
else
message="FAIL: make check on $commit output is $url"
fi
$success
Cheers
http://tracker.ceph.com/issues/10046
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2014-12-13 18:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=548C8BDB.8010806@dachary.org \
--to=loic@dachary.org \
--cc=alfredo.deza@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=kdreyer@redhat.com \
/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.