From: Simone Ballarin <simone.ballarin@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: consulting@bugseng.com,
Simone Ballarin <simone.ballarin@bugseng.com>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Wei Liu <wl@xen.org>
Subject: [XEN PATCH v4 0/4] automation: Add ECLAIR pipelines
Date: Wed, 26 Jul 2023 18:20:46 +0200 [thread overview]
Message-ID: <cover.1690387393.git.simone.ballarin@bugseng.com> (raw)
This patch series adds two pipelines that analyze an ARM64 and a X86_64
build with the ECLAIR static analyzer on the guidelines contained in Set1.
The builds analyzed are the ones triggered by automation/eclair_analysis/build.sh.
automation/eclair_analysis/ECLAIR contains the ECLAIR configuration files
(.ecl files) and scripts that implement the integration (action* scripts).
All commits on the xen-project/xen:staging branch will be analyzed
and their artifacts will be stored indefinitely; the integration will
report differential information with respect to the previous analysis.
All commits on other branches or repositories will be analyzed and
only the last ten artifacts will be kept; the integration will report
differential information with respect to the analysis done on the common
ancestor with xen-project/xen:staging (if available).
Additionaly any repository should be able to read a masked variable
named WTOKEN with the token provided by BUGSENG, otherwise the pipeline
will fail.
The analysis fails if it contains violations of guidelines tagged as
clean:added. The list of clean guidelines are maintained in
automation/eclair_analysis/ECLAIR/tagging.ecl.
--
Changes in v4:
- move link to the analysis results at the end of the console log
- avoid git warning
- avoid undesired git logs
- remove undesired blanks in MAINTAINERS
Simone Ballarin (4):
automation: Add ECLAIR utilities and settings
automation: Add xen builds for the ECLAIR analyses
automation: Add ECLAIR pipelines
maintainers: Add ECLAIR reviewer
.gitlab-ci.yml | 2 +
MAINTAINERS | 6 +
automation/eclair_analysis/ECLAIR/Set1.ecl | 59 ++++
automation/eclair_analysis/ECLAIR/Set2.ecl | 25 ++
automation/eclair_analysis/ECLAIR/Set3.ecl | 67 ++++
.../eclair_analysis/ECLAIR/action.helpers | 193 ++++++++++++
.../eclair_analysis/ECLAIR/action.settings | 172 ++++++++++
.../ECLAIR/action_clean_added.sh | 36 +++
.../eclair_analysis/ECLAIR/action_log.sh | 15 +
.../ECLAIR/action_pull_request.sh | 57 ++++
.../eclair_analysis/ECLAIR/action_push.sh | 95 ++++++
.../ECLAIR/action_upload_sarif.sh | 31 ++
.../eclair_analysis/ECLAIR/analysis.ecl | 25 ++
automation/eclair_analysis/ECLAIR/analyze.sh | 106 +++++++
.../ECLAIR/call_properties.ecl | 106 +++++++
.../eclair_analysis/ECLAIR/deviations.ecl | 298 ++++++++++++++++++
.../eclair_analysis/ECLAIR/out_of_scope.ecl | 127 ++++++++
.../ECLAIR/print_analyzed_files.sh | 66 ++++
.../eclair_analysis/ECLAIR/public_APIs.ecl | 6 +
automation/eclair_analysis/ECLAIR/report.ecl | 4 +
automation/eclair_analysis/ECLAIR/tagging.ecl | 34 ++
.../eclair_analysis/ECLAIR/toolchain.ecl | 275 ++++++++++++++++
automation/eclair_analysis/Makefile.prepare | 6 +
automation/eclair_analysis/build.sh | 44 +++
automation/eclair_analysis/prepare.sh | 42 +++
automation/eclair_analysis/xen_arm_config | 147 +++++++++
automation/eclair_analysis/xen_x86_config | 152 +++++++++
automation/gitlab-ci/analyze.yaml | 38 +++
automation/gitlab-ci/build.yaml | 1 +
automation/scripts/eclair | 34 ++
30 files changed, 2269 insertions(+)
create mode 100644 automation/eclair_analysis/ECLAIR/Set1.ecl
create mode 100644 automation/eclair_analysis/ECLAIR/Set2.ecl
create mode 100644 automation/eclair_analysis/ECLAIR/Set3.ecl
create mode 100644 automation/eclair_analysis/ECLAIR/action.helpers
create mode 100644 automation/eclair_analysis/ECLAIR/action.settings
create mode 100755 automation/eclair_analysis/ECLAIR/action_clean_added.sh
create mode 100755 automation/eclair_analysis/ECLAIR/action_log.sh
create mode 100644 automation/eclair_analysis/ECLAIR/action_pull_request.sh
create mode 100755 automation/eclair_analysis/ECLAIR/action_push.sh
create mode 100755 automation/eclair_analysis/ECLAIR/action_upload_sarif.sh
create mode 100644 automation/eclair_analysis/ECLAIR/analysis.ecl
create mode 100755 automation/eclair_analysis/ECLAIR/analyze.sh
create mode 100644 automation/eclair_analysis/ECLAIR/call_properties.ecl
create mode 100644 automation/eclair_analysis/ECLAIR/deviations.ecl
create mode 100644 automation/eclair_analysis/ECLAIR/out_of_scope.ecl
create mode 100755 automation/eclair_analysis/ECLAIR/print_analyzed_files.sh
create mode 100644 automation/eclair_analysis/ECLAIR/public_APIs.ecl
create mode 100644 automation/eclair_analysis/ECLAIR/report.ecl
create mode 100644 automation/eclair_analysis/ECLAIR/tagging.ecl
create mode 100644 automation/eclair_analysis/ECLAIR/toolchain.ecl
create mode 100644 automation/eclair_analysis/Makefile.prepare
create mode 100755 automation/eclair_analysis/build.sh
create mode 100755 automation/eclair_analysis/prepare.sh
create mode 100644 automation/eclair_analysis/xen_arm_config
create mode 100644 automation/eclair_analysis/xen_x86_config
create mode 100644 automation/gitlab-ci/analyze.yaml
create mode 100755 automation/scripts/eclair
--
2.34.1
next reply other threads:[~2023-07-26 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 16:20 Simone Ballarin [this message]
2023-07-26 16:20 ` [XEN PATCH v4 1/4] automation: Add ECLAIR utilities and settings Simone Ballarin
2023-07-26 16:20 ` [XEN PATCH v4 2/4] automation: Add xen builds for the ECLAIR analyses Simone Ballarin
2023-07-26 16:20 ` [XEN PATCH v4 3/4] automation: Add ECLAIR pipelines Simone Ballarin
2023-07-26 22:46 ` Stefano Stabellini
2023-07-26 16:20 ` [XEN PATCH v4 4/4] maintainers: Add ECLAIR reviewer Simone Ballarin
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=cover.1690387393.git.simone.ballarin@bugseng.com \
--to=simone.ballarin@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.com \
--cc=dpsmith@apertussolutions.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.
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.