From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH v2] .github/workflows: add coverity action
Date: Thu, 21 Sep 2023 16:30:02 -0700 [thread overview]
Message-ID: <xmqqo7hv3y11.fsf@gitster.g> (raw)
In-Reply-To: <b23951c569660e1891a7fb3ad2c2ea1952897bd7.1695332105.git.me@ttaylorr.com> (Taylor Blau's message of "Thu, 21 Sep 2023 17:53:31 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> This fell to the bottom of my queue, but I got back to it today while
> doing some ~~spring~~ fall inbox cleaning :-). Thanks Peff and Johannes
> for helpful review in the first round. Range-diff is below:
>
> Range-diff against v1:
> 1: f74ae75ddb < -: ---------- .github/workflows: add coverity action
> -: ---------- > 1: b23951c569 .github/workflows: add coverity action
That's a useful range-diff ;-). Even with --word-diff, range-diff does
not notice that they correspond to each other, without an absurd setting
like --creation-factor=999.
> .github/workflows/coverity.yml | 22 ++++++++++++++++++++++
> ci/install-dependencies.sh | 2 +-
> ci/lib.sh | 2 +-
> 3 files changed, 24 insertions(+), 2 deletions(-)
> create mode 100644 .github/workflows/coverity.yml
>
> diff --git a/.github/workflows/coverity.yml b/.github/workflows/coverity.yml
> new file mode 100644
> index 0000000000..3ba00b3929
> --- /dev/null
> +++ b/.github/workflows/coverity.yml
> @@ -0,0 +1,22 @@
> +name: Coverity
> +
> +on: [push, pull_request]
This no longer hardcocdes the condition to master and tagged ones,
as ...
> +jobs:
> + coverity:
> + if: (vars.ENABLE_COVERITY == 'true') &&
> + (vars.COVERITY_BRANCHES == '' ||
> + contains(vars.COVERITY_BRANCHES, github.ref_name) ||
> + contains(vars.COVERITY_BRANCHES, '*'))
... this lets you control when to run it via the "vars". This round
also can act on pull-requests in addition to pushes.
> + runs-on: ubuntu-latest
> + steps:
> + - uses: actions/checkout@v3
> + - run: ci/install-dependencies.sh
> + env:
> + jobname: coverity
> + - uses: vapier/coverity-scan-action@cae3c096a2eb21c431961a49375ac17aea2670ce
> + with:
> + email: ${{ secrets.COVERITY_SCAN_EMAIL }}
> + token: ${{ secrets.COVERITY_SCAN_TOKEN }}
> + command: make -j8
And the actual implementation is vastly different by just using a
canned one, which requires less maintenance on our end, which is
nice.
> diff --git a/ci/lib.sh b/ci/lib.sh
> index 6fbb5bade1..2ad0ae340e 100755
> --- a/ci/lib.sh
> +++ b/ci/lib.sh
> @@ -227,7 +227,7 @@ export SKIP_DASHED_BUILT_INS=YesPlease
>
> case "$runs_on_pool" in
> ubuntu-*)
> - if test "$jobname" = "linux-gcc-default"
> + if test "$jobname" = "linux-gcc-default" || test "$jobname" = "coverity"
> then
> break
> fi
This part is new in this iteration, to avoid further customization
that enables more exotic features, which makes sense.
next prev parent reply other threads:[~2023-09-21 23:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 3:34 [PATCH] .github/workflows: add coverity action Taylor Blau
2023-08-25 21:32 ` Jeff King
2023-08-25 21:56 ` Jeff King
2023-08-29 8:18 ` Johannes Schindelin
2023-08-30 0:18 ` Jeff King
2023-08-30 8:07 ` Johannes Schindelin
2023-08-30 19:03 ` Jeff King
2023-09-21 21:53 ` [PATCH v2] " Taylor Blau
2023-09-21 23:30 ` Junio C Hamano [this message]
2023-09-22 11:09 ` Johannes Schindelin
2023-09-23 6:21 ` Jeff King
2023-09-23 7:09 ` Jeff King
2023-09-23 6:10 ` Jeff King
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=xmqqo7hv3y11.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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.