uaudit: Run static analysis tools with full paths to source code
This should in general then produce output files containing the full paths
to the various files in the source code tree to make jumping to the various
errors easier.
* sespiros/esm-chroot-names-3:
Put the chroot compatible release name in a separate variable
Fix bug when detecting package's release
Fix invalid architecture warning for chroot
Revert "Add feature to autogenerate chroot name for ESM builds"
Revert "Add feature to autogenerate chroot name for ESM builds"
umt testflinger: Create testflinger snap config dir if doesn't exist
If testflinger-cli has never been run before the directory
~/snap/testflinger-cli/common will not already exist, so make sure we
create it first in that case.
Static analysis results summary in JIRA.md has the coverity
count number of defects missing, re-adding.
In case coverity is not used, modify the text to say that.
umt uses .ubuntu-security-tools.conf's release_list to try and
detect the release by comparing it to the current path when building
a package. For ESM releases it failed to do so.
Since we handle ESM releases as different releases, a new field
'base_release' was added in the package details struct.
i.e a package built for esm-infra/xenial will have:
details['release'] = 'esm-infra/xenial'
details['base_release'] = 'xenial'
The sanity check for changelog_release will now happen against the
package's base_release field.
chroots for ESM will be automatically detected as well as long as
they follow the naming convention <release>-<arch> where <release>
can also be of the form esm-X_<release> or <release>_esm.
