It's now possible to control the following parameters using environment
variables:
- Minimum allowed coverage, using `$COVERAGE_MIN`
- Decimal precision, usin `$COVERAGE_PRECISION`

When the above variables are not set , values will fallback to their
defaults, i.e. 0.

This was already implemented in the old CI [1] and added to the project
template [2].

For more information, please check the configuration reference of
Coverage.py on [3].

[1] https://github.com/Vauxoo/maintainer-quality-tools/pull/314
[2] https://git.vauxoo.com/vauxoo/project-template/commit/93bd8c1d
[3] https://coverage.readthedocs.io/en/coverage-5.0/config.html

The last CI build has an error and it didn't deploy the package to pypi

The error is the following one:

    /usr/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.

We are using `build` package and it was tested with the same docker image

It is working well

Also, it is fixing the following install build error:

    docker run -it --rm quay.io/vauxoo/dockerv:latest pip install -q build
        ERROR: Cannot uninstall 'pep517'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.

Fixed using ignore-installed parameter:

    docker run -it --rm quay.io/vauxoo/dockerv:latest pip install -q --ignore-installed build
        Package installed

Moisés López - https://www.vauxoo.com/ authored Sep 02, 2022 and Tulio Ruiz committed Sep 05, 2022

The old CI was using INCLUDE and EXCLUDE environment variables in order to know what modules to test:
 - https://github.com/OCA/maintainer-quality-tools/blob/d705b9d68abd2616ad786bd29f760ee0ca182692/travis/test_server.py#L305-L306

The rules were:
 - if INCLUDE is defined so only these modules (separated by commas) are used to test
 - if INCLUDE is not defined so all modules of the main repository will be tested
 - if EXCLUDE is defined so these modules will be removed from included result
 - if EXCLUDE is not defined so any modules are excluded

Check the code related:
 - https://github.com/OCA/maintainer-quality-tools/blob/d705b9d68abd2616ad786bd29f760ee0ca182692/travis/test_server.py#L151-L169

Since that deployv could be used for repositories using this way to be tested
so we need to support the same environment variables in order to avoid new changes and working out-of-box

Even it is good to test modules where a main app is not even assigned

Extra tags now are available since it is a valid extra parameter to avoid testing something
or add to test another thing

* [REF] common: test - Show command executed in order to reproduced it locally

Moisés López - https://www.vauxoo.com/ authored Sep 04, 2022 and Moisés López - https://www.vauxoo.com/ committed Sep 05, 2022

Odoo versions is showing a WARNING when there are packages changes:
 - `WARNING ? py.warnings: ir_actions_report.py:66: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead.`

These warnings are not easy to fix since it depends on Odoo code itself
or Odoo requirements.txt

A change in the requirements.txt could require a heavy migration of the code of Odoo

and this could break the Stable Odoo Policies

I was been adding a log-handler to silent these kind of errors
for each project but I think it is even better showing them
but ignoring them as known in the pipeline

Even the pipeline is running unittest if it is not red then all is well for us

This MR silent py.warnings raised from odoo core path

Running the following script:

    for VERSION in 150 140 130 120
    do
        echo -e "\nRunning in $VERSION without tcl"
        docker run -it --rm vauxoo/odoo-${VERSION}-image /bin/bash -c "apt update -qq && apt -yq install expect-dev > /dev/null && unbuffer ls --color=auto";
        echo -e "Ran in $VERSION without tcl\n"
        echo -e "\nRunning in $VERSION with tcl"
        docker run -it --rm vauxoo/odoo-${VERSION}-image /bin/bash -c "apt update -qq && apt -yq install expect-dev tcl8.6 > /dev/null && unbuffer ls --color=auto";
        echo -e "Ran in $VERSION with tcl\n"
    done

You will see the following output:

    Running in 150 without tcl
    bin  boot  dev  etc  home  lib  lib32  lib64  libx32  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
    Ran in 150 without tcl

    Running in 150 with tcl
    bin  boot  dev  etc  home  lib  lib32  lib64  libx32  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
    Ran in 150 with tcl

    Running in 140 without tcl
    bin  boot  dev  etc  home  lib  lib32  lib64  libx32  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
    Ran in 140 without tcl

    Running in 140 with tcl
    bin  boot  dev  etc  home  lib  lib32  lib64  libx32  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
    Ran in 140 with tcl

    Running in 130 without tcl
    9 /usr/bin/unbuffer: 4: exec: tclsh8.6: not found
    Ran in 130 without tcl

    Running in 130 with tcl
    9 bin  boot  dev  etc  home  lib  lib64  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
    Ran in 130 with tcl

    Running in 120 without tcl
    140 /usr/bin/unbuffer: 4: exec: tclsh8.6: not found
    Ran in 120 without tcl

    Running in 120 with tcl
    140 bin  boot  dev  etc  home  lib  lib64  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
    Ran in 120 with tcl

Notice 130 and 120 has the following error without tcl:

    140 /usr/bin/unbuffer: 4: exec: tclsh8.6: not found

Also, notice 140 and 150 even is working well installing tcl

We could add this package in the Dockerfile of the images

but I tried to rebuild a 120 image and it started to raises new errors related with
pip packages

So, it is risky to update the image

Better using this way to install only when it is needed and safe where it is not needed

Moisés López - https://www.vauxoo.com/ authored Aug 10, 2022 and Tulio Ruiz committed Aug 29, 2022

Continuation from:
 - !67

Moisés López - https://www.vauxoo.com/ authored Aug 19, 2022 and Moisés López - https://www.vauxoo.com/ committed Aug 19, 2022

Newer Odoo versions is showing a WARNING when there are not tests to run

The log warning is the following:
 - `WARNING db odoo.tests.runner: 0 failed, 0 error(s) of 0 tests when loading database 'db'`

But new projects doens't have tests in the first time

So, the "warnings" pipeline could be raised

But it is not a warning easy to fix in the first step

So, it is better to ignore it

The new colorized log from tests using "unbuffer" needs to be parsed correctly

In order to detect errors, warnings and so on

In the past, the code was adapted to support colorized warnings

Now it is adapted to support all kind of colorized logs

Note: It was extracted from MQT and it was extracted from serverfault:
  - https://github.com/OCA/maintainer-quality-tools/blob/d705b9d68abd2/travis/test_server.py#L65
    - http://serverfault.com/questions/71285

Moisés López - https://www.vauxoo.com/ authored Aug 09, 2022 and Tulio Ruiz committed Aug 12, 2022

Allow to the user to know where the logs are saved
in order to check if next step is using the correct path

Moisés López - https://www.vauxoo.com/ authored Aug 08, 2022 and Moisés López - https://www.vauxoo.com/ committed Aug 11, 2022

Avoid raising error if the directoy was already created
Allowing to run 2 times the same command locally
The coverage content is created with file flag "w" instead of "a"
in order to be cleaned if it already exists
The coverage content was removed the extra spaces
The coverage is showed in the logs similar to old way and ran first

Compatible with docker remote where you do not have installed

Fixing the following error:
 - "ConnectionError: ('Connection aborted.', error(2, 'No such file or directory'))"

- Just in case someone use the main branch in the -dev group for any reason we detect if it is a dev repo so it don't push to latest, just to dev.

We do so by detecting if the branch name is the same as the version and now we also check if the group name ends with -dev, because we have as general rule to name the groups with 'group-dev' for development and 'group' for the main repo

- Expressions like  wheren't evaluated properly, the string was spllitting in the second = instead of the first.

If for some reason there is a file with the same name as the folder we are trying to create to store the image name the CI will show an error, now we need to remove such file so the mkdir can create the folder after.

[FIX] Pip is using p3 but default is p2

[FIX] ALLOW_DEPRECATED is not required as an env var

[FIX] Show deprecation count

[FIX] Remove debug message

[FIX] Do not count deprecation as general warnings

[IMP] Better log format and add debug information