From: Lars Schneider <larsxschneider@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, l.s.r@web.de
Subject: [PATCH v1] travis-ci: add static analysis build job to run coccicheck
Date: Tue, 11 Apr 2017 09:26:37 +0200 [thread overview]
Message-ID: <20170411072637.57369-1-larsxschneider@gmail.com> (raw)
Add a dedicated build job for static analysis. As a starter we only run
coccicheck but in the future we could run Clang Static Analyzer or
similar tools, too.
Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
---
Notes:
Base Ref: master
Web-Diff: https://github.com/larsxschneider/git/commit/f191458df1
Checkout: git fetch https://github.com/larsxschneider/git travisci/cocci-v1 && git checkout f191458df1
.travis.yml | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/.travis.yml b/.travis.yml
index 591cc57b80..52855c806c 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -60,6 +60,18 @@ matrix:
# Use the following command to debug the docker build locally:
# $ docker run -itv "${PWD}:/usr/src/git" --entrypoint /bin/bash daald/ubuntu32:xenial
# root@container:/# /usr/src/git/ci/run-linux32-build.sh
+ - env: Static Analysis
+ os: linux
+ compiler:
+ addons:
+ apt:
+ packages:
+ - coccinelle
+ before_install:
+ script:
+ # "before_script" that builds Git is inherited from base job
+ - make coccicheck
+ after_failure:
- env: Documentation
os: linux
compiler: clang
base-commit: b14f27f91770e0f99f64135348977a0ce1c7993a
--
2.12.2
next reply other threads:[~2017-04-11 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 7:26 Lars Schneider [this message]
2017-04-16 13:31 ` [PATCH v1] travis-ci: add static analysis build job to run coccicheck Sebastian Schuberth
2017-04-18 19:20 ` Stefan Beller
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=20170411072637.57369-1-larsxschneider@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
/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 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 NNTP newsgroup(s).