Mercurial > kallithea

view .coveragerc @ 6583:8a60eb2b7603

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Jenkinsfile: run each py.test on a separate executor Running all py.test processes in parallel on the same executor is not a good idea. If a node has not much RAM, it could run out of memory when all py.test processes run at the same time. And If there are only 2 CPU cores, it doesn't make sense to run more then 2 processes either. Therefore use a separate executor for each one. The py.test processes will thus only run in parallel if there are multiple Jenkins executors available.
author domruf <dominikruf@gmail.com>
date Sun, 09 Apr 2017 00:13:17 +0200
parents 7790b34a0cef
children 0acb46763886
line wrap: on
line source

[run]
omit =
    # the bin scripts are not part of the Kallithea web app
    kallithea/bin/*
    # we ship with no active extensions
    kallithea/config/rcextensions/*
    # dbmigrate and paster_commands are not part of the Kallithea web app
    kallithea/lib/dbmigrate/*
    kallithea/lib/paster_commands/*
    # the tests themselves should not be part of the coverage report
    kallithea/tests/*
    # the scm hooks are not run in the kallithea process
    kallithea/config/post_receive_tmpl.py
    kallithea/config/pre_receive_tmpl.py