{"thread":{"id":"45657","subject":"[PATCH v1] travis-ci: add static analysis build job to run coccicheck","startedAt":"2017-04-11T07:26:51Z","lastAt":"2017-04-18T19:20:56Z","messageCount":3,"participants":["Lars Schneider","Sebastian Schuberth","Stefan Beller"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"316550","messageId":"20170411072637.57369-1-larsxschneider@gmail.com","threadId":"45657","inReplyTo":null,"subject":"[PATCH v1] travis-ci: add static analysis build job to run coccicheck","fromName":"Lars Schneider","fromEmail":"larsxschneider@gmail.com","sentAt":"2017-04-11T07:26:37Z","receivedAt":"2017-04-11T07:26:51Z","isPatch":true,"sender":{"key":"larsxschneider@gmail.com","avatar":"https://avatars.githubusercontent.com/u/477434?v=4"},"body":"Add a dedicated build job for static analysis. As a starter we only run\ncoccicheck but in the future we could run Clang Static Analyzer or\nsimilar tools, too.\n\nSigned-off-by: Lars Schneider <larsxschneider@gmail.com>\n---\n\nNotes:\n    Base Ref: master\n    Web-Diff: https://github.com/larsxschneider/git/commit/f191458df1\n    Checkout: git fetch https://github.com/larsxschneider/git travisci/cocci-v1 && git checkout f191458df1\n\n .travis.yml | 12 ++++++++++++\n 1 file changed, 12 insertions(+)\n\ndiff --git a/.travis.yml b/.travis.yml\nindex 591cc57b80..52855c806c 100644\n--- a/.travis.yml\n+++ b/.travis.yml\n@@ -60,6 +60,18 @@ matrix:\n         # Use the following command to debug the docker build locally:\n         # $ docker run -itv \"${PWD}:/usr/src/git\" --entrypoint /bin/bash daald/ubuntu32:xenial\n         # root@container:/# /usr/src/git/ci/run-linux32-build.sh\n+    - env: Static Analysis\n+      os: linux\n+      compiler:\n+      addons:\n+        apt:\n+          packages:\n+          - coccinelle\n+      before_install:\n+      script:\n+        # \"before_script\" that builds Git is inherited from base job\n+        - make coccicheck\n+      after_failure:\n     - env: Documentation\n       os: linux\n       compiler: clang\n\nbase-commit: b14f27f91770e0f99f64135348977a0ce1c7993a\n-- \n2.12.2\n\n"},{"id":"316947","messageId":"55524921-3295-90e6-6473-ae1289eeeb75@gmail.com","threadId":"45657","inReplyTo":"20170411072637.57369-1-larsxschneider@gmail.com","subject":"Re: [PATCH v1] travis-ci: add static analysis build job to run coccicheck","fromName":"Sebastian Schuberth","fromEmail":"sschuberth@gmail.com","sentAt":"2017-04-16T13:31:36Z","receivedAt":"2017-04-16T13:31:51Z","isPatch":true,"sender":{"key":"sschuberth@gmail.com","avatar":"https://avatars.githubusercontent.com/u/349154?v=4"},"body":"On 2017-04-11 09:26, Lars Schneider wrote:\n\n> Add a dedicated build job for static analysis. As a starter we only run\n> coccicheck but in the future we could run Clang Static Analyzer or\n> similar tools, too.\n\nJust FYI, some time ago someone (I don't recall who) signed up Git with \nCoverity's free scan service for OSS projects:\n\nhttps://scan.coverity.com/projects/git?tab=overview\n\nMaybe it makes sense to at least link to this page, too?\n\n-- \nSebastian Schuberth\n\n"},{"id":"317132","messageId":"CAGZ79kbwQYCLXzVMr3wZsx3vA2zBMisqySt7SRQsnU_mQDB4gg@mail.gmail.com","threadId":"45657","inReplyTo":"55524921-3295-90e6-6473-ae1289eeeb75@gmail.com","subject":"Re: [PATCH v1] travis-ci: add static analysis build job to run coccicheck","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2017-04-18T19:20:51Z","receivedAt":"2017-04-18T19:20:56Z","isPatch":true,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On Sun, Apr 16, 2017 at 6:31 AM, Sebastian Schuberth\n<sschuberth@gmail.com> wrote:\n> On 2017-04-11 09:26, Lars Schneider wrote:\n>\n>> Add a dedicated build job for static analysis. As a starter we only run\n>> coccicheck but in the future we could run Clang Static Analyzer or\n>> similar tools, too.\n>\n>\n> Just FYI, some time ago someone (I don't recall who) signed up Git with\n> Coverity's free scan service for OSS projects:\n>\n> https://scan.coverity.com/projects/git?tab=overview\n>\n> Maybe it makes sense to at least link to this page, too?\n>\n\nyeah 'someone' is a good description. I accidentally took it over when\nit looked stale. Now I have a cron job to upload the pu branch there\neach night. (Which is one of the downsides of that service: Git is so\nlarge measured by lines of code, such that we're allowed only one scan\nper day. I wonder if that could be circumvented by each contributor having\nits own fork, but let's not go that way)\n"}]}