Merge ~sbeattie/ubuntu-cve-tracker/+git/ubuntu-cve-tracker:add-lpci-validation-ubuntu.com into ubuntu-cve-tracker:master
Status: | Merged |
---|---|
Merged at revision: | 905f7e26a5998dad18740c364d9b436580feda59 |
Proposed branch: | ~sbeattie/ubuntu-cve-tracker/+git/ubuntu-cve-tracker:add-lpci-validation-ubuntu.com |
Merge into: | ubuntu-cve-tracker:master |
Diff against target: |
28 lines (+13/-0) 1 file modified
.launchpad.yaml (+13/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alex Murray | Approve | ||
Review via email: mp+465324@code.launchpad.net |
Commit message
Merge lpci: validate the release configuration of the cve tracker website
The post-release-
validate the configuration of releases in the CVE website; add a
separate lpci job to validate the configuration so we know when it
changes unexpectedly.
Description of the change
Because we want to know if the release configuration of the ubuntu.com cCVE website changes unexpectedly, it would useful to perform the validation step in the post-release-
Right now the test fails, correctly because Diogo's change in https:/
Running ['bash', '--noprofile', '--norc', '-ec', './scripts/
:: noble (24.04) okay:
:: mantic (23.10) okay:
:: lunar (23.04) okay:
:: kinetic (22.10) okay:
:: jammy (22.04) okay:
:: impish (21.10) okay:
:: hirsute (21.04) okay:
:: groovy (20.10) okay:
:: focal (20.04) okay:
:: bionic (18.04) okay:
:: xenial (16.04) okay:
:: --- stored trusty info
:: +++ https:/
:: @@ -1,11 +1,11 @@
:: {
:: "codename": "trusty",
:: "development": false,
:: - "esm_expires": "2024-04-
:: + "esm_expires": "2026-04-
:: "lts": true,
:: "name": "Trusty Tahr",
:: "release_date": "2014-04-
:: "support_expires": "2019-04-
:: "support_tag": "ESM",
:: "version": "14.04"
:: }
Job 'check-
LGTM - thanks sbeattie.