diff options
| author | Harald Welte <laforge@osmocom.org> | 2022-06-28 11:26:28 +0200 |
|---|---|---|
| committer | laforge <laforge@osmocom.org> | 2022-06-28 15:14:24 +0000 |
| commit | bab323da5295087dbe5fd4a1896d6c9d176d0099 (patch) | |
| tree | a42e0043770bffb9b6af5cb786c49b624e11302e | |
| parent | 8637f74cedbd5f330dd1fb6317280c9588b3e0f1 (diff) | |
install-coverity: update to 2021.12
Starting in February 2022, coverity stopped to support the old
2019.03 version that we were using. Unfortunately that didn't
generate any e-mail notification to the project admins so it
remained undetected until now :(
What sucks is that the filename states 2021.12 but then the
actual directory created upon extraction is 2021.12.1, meaning
our ansible rule breaks. We have to rename the tarball to 2021.12.1
before running the playbook...
Closes: OS#5594
Change-Id: I950834cc2ad70979a53a563610bbc9feef1f5f20
| -rw-r--r-- | ansible/roles/install-coverity/defaults/main.yml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ansible/roles/install-coverity/defaults/main.yml b/ansible/roles/install-coverity/defaults/main.yml index 6b97781..d7a8082 100644 --- a/ansible/roles/install-coverity/defaults/main.yml +++ b/ansible/roles/install-coverity/defaults/main.yml @@ -1,4 +1,4 @@ --- -coverity_version: 2019.03 +coverity_version: 2021.12.1 coverity_installer_file: "cov-analysis-linux64-{{ coverity_version }}.tar.gz" |