History

Tomas Susanka 5edd0a55f3 ci: document arduino pins		4 years ago
..
hardware_tests	ci: document arduino pins	4 years ago
ui_test_records	ci: rename tmp folder to ui_test_records	4 years ago
.gitignore	docker: don't use nixos/nix as base, use alpine from scratch	4 years ago
Dockerfile	ci/Dockerfile: use nix-shell instead of nix-env	4 years ago
README.md	docs: document CI jobs	4 years ago
build.yml	tests/upgrade-tests: modify paths in release jobs and add job for MacOS	4 years ago
check_fixup.sh	ci: check if commit message contains fixup on travis	4 years ago
check_release_commit_messages.sh	ci: fix release commit check	4 years ago
deploy.yml	tests/upgrade-tests: modify paths in release jobs and add job for MacOS	4 years ago
environment.yml	ci: use nix docker image	4 years ago
posttest.yml	ci: fail if coverage falls under threshold	4 years ago
prebuild.yml	ci: run release commit message check only on one Gitlab	4 years ago
prepare_ui_artifacts.py	ci: move ui reports to the root to simplify artifacts browsing	4 years ago
shell.nix	poetry: add pyproject.toml + lock file	4 years ago
test.yml	tests/upgrade-tests: modify paths in release jobs and add job for MacOS	4 years ago

README.md

CI

The complete test suite is running on a public GitLab CI. If you are an external contributor, we also have a Travis instance where a small subset of tests is running as well - mostly style and easy fast checks, which are quite common to fail for new contributors.

See this list of CI jobs descriptions for more info.

The CI folder contains all the .yml GitLab files that are included in the main .gitlab.yml to provide some basic structure. All GitLab CI Jobs run inside a docker image, which is built using the present Dockerfile. This image is stored in the GitLab registry.