Remove the variable DUNE_RUNNING_IN_CI from the local gitlab-ci, since already set in the docker image

Currently the CI config requires that the `core/ci-config`
project exists on the same gitlab server. This prevents
the CI from working when pushing the repository to another
server. While one may argue, that one also has to push
`core/ci-config` then, it is a very strong restriction to
require that the gitlab group `core` is available.

This can be avoided by using a gitlab remote include for those
files with a link pointing to the dune server instead of a local
include.

See https://reuse.software/ for a description.

The shared runner might not pick up the job otherwise.

Plus, ignore everything in pybind11.  Since this is code we import
from outside I couldn't be bothered to fix the typos there, too.

change ci yml since python bindings now on by default

still need flag DUNE_RUNNING_IN_CI which is now turned on by default in CI config.opts file - this is used to set the index url to the gitlab registry for package download

test both turing of bindings and turning off python altogether in CI

make sure embeded test does not cause testing to fail if dune package could not be installed - this is not a perfect solution but works for now

exclude dune.src_dir from module load since this is a link set by cmake

- moved some parts relating to the venv out of PythonCommonMacros to Virtualenv
- removed PythonMacros file
- use an external active env instead of generating a new internal one.
  Also added some checks to avoid a user mixing up different builds within the same env
- finally made some changes on how and when the dune-py module is regenerated

some minor fixes

[testing] ci with index-url set

remove extra-index-url from pip install

add a stopgap solution unti ci repo up and running again

we need pip>=21 so that 'make', 'make install_python', 'make' does not
mess up the packages in an external env (with older versions of pip
the last 'make' wouldn't correctly remove the non editable install).

use clang 10-20 for python test since some other parallel tests fail with the clang 10-17 toolchain

fix an issue with a double installation of the dune module in the case
of using packages (there was a 2.8.0 version and a dev version being added to the venv)

minor improvement to plotting

Add a 'flag' argument to the 'dune_python_install_package' command which contains cmake variables to store in metadata file.
This is to be used to fix for example the compiler to use for dune-py but that hasn't been added to the builder yet.
Also changed builddirs output to contain ';' separator (using a cmake string instead of a list).

added 'cmake flags' from metadata file to CMakeLists.txt.template

correctly throw exception if dune-py not available in assertHave

Robert K authored 4 years ago and Simon Praetorius committed 3 years ago

trigger the core pipeline in dune-nightly-tests

run downstream tests in separate stage

Allow failure for triggered downstream pipeline

Simon Praetorius authored 4 years ago and Andreas Dedner committed 4 years ago

switch to docker registry in dune-project.org

use debian11 from dune gitlab registry

This is a workaround for a bug that showed up after gitlab migration. See issue
infrastructure/issues0#62 for further
discussion.

Robert K authored 4 years ago and Andreas Dedner committed 4 years ago

Python bindings, default is OFF.

[feature][CI] enable Python bindings.

make sure DUNE_ENABLE_PYTHPMBINDINGS is set to true in dune-py

Other implementations should only be selected if the compiler is specifically
told to support them.

Closes: #165

All of the other modules don't specify the quick label on their tests.

The special vectorization test run stays in the local configuration, as it is specific to
dune-common.