From: larsxschneider@gmail.com
To: git@vger.kernel.org
Cc: Lars Schneider <larsxschneider@gmail.com>
Subject: [RFC/PATCH v1] Add Travis CI support
Date: Thu, 24 Sep 2015 23:43:23 +0200 [thread overview]
Message-ID: <1443131004-39284-1-git-send-email-larsxschneider@gmail.com> (raw)
From: Lars Schneider <larsxschneider@gmail.com>
Hi,
I recently broke a few tests...
In order to avoid that in the future I configured Travis CI for Git. With this
patch Travis can run all Git tests including the "git-p4" and "Git-LFS" tests.
The tests are executed on "Ubuntu 12.04 LTS Server Edition 64 bit" and on
"OS X Mavericks" using gcc and clang.
My idea is that the owner of "https://github.com/git/git" enables this account
for Travis (it's free!). Then we would automatically get the test state for all
official branches.
Every contributor can enable Travis for their respective GitHub accounts. Then
they would know if their patches pass all tests in advance, too.
You can see the state of my branches here:
https://travis-ci.org/larsxschneider/git/branches
It's pretty red. The reason is that maint, master, and next have a failure on
OS X (test "t9815-git-p4-submit-fail.sh" does not pass). Furthmore pu does not
pass on either Linux or OS X (which is propably OK since it is pu).
You can also inspect the build/test logs. Here for instance the log for the
next branch compiled on Linux with gcc:
https://travis-ci.org/larsxschneider/git/jobs/82032861
Cheers,
Lars
Lars Schneider (1):
Add Travis CI support
.travis.yml | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
create mode 100644 .travis.yml
--
2.5.1
next reply other threads:[~2015-09-24 21:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 21:43 larsxschneider [this message]
2015-09-24 21:43 ` [RFC/PATCH v1] Add Travis CI support larsxschneider
2015-09-25 0:41 ` Junio C Hamano
2015-09-25 3:14 ` Dennis Kaarsemaker
2015-09-25 7:27 ` Johannes Schindelin
2015-09-25 8:05 ` Luke Diamand
2015-09-25 17:41 ` Junio C Hamano
2015-09-26 16:40 ` Lars Schneider
2015-09-27 12:11 ` Matthieu Moy
2015-09-28 17:21 ` Stefan Beller
2015-09-28 17:37 ` Matthieu Moy
2015-09-28 18:47 ` Junio C Hamano
2015-09-28 19:07 ` Matthieu Moy
2015-10-03 22:23 ` Roberto Tyley
2015-10-04 1:27 ` Junio C Hamano
2015-10-04 1:37 ` Junio C Hamano
2015-10-04 8:13 ` Dennis Kaarsemaker
2015-10-04 12:51 ` Johannes Schindelin
2015-10-04 7:59 ` Matthieu Moy
2015-10-04 17:46 ` Junio C Hamano
2015-10-04 18:06 ` Dennis Kaarsemaker
2015-10-05 6:54 ` Matthieu Moy
2015-10-05 16:51 ` Junio C Hamano
2015-10-12 8:03 ` Sebastian Schuberth
2015-10-04 17:59 ` Junio C Hamano
2015-10-04 3:34 ` Jeff King
2015-10-02 16:40 ` Sebastian Schuberth
2015-09-25 16:26 ` Jeff King
2015-09-25 18:29 ` Junio C Hamano
2015-09-25 18:52 ` Jeff King
2015-09-26 21:54 ` Shawn Pearce
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1443131004-39284-1-git-send-email-larsxschneider@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).