You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
trezor-firmware/ci
Pavol Rusnak b9c0b597bc
nix: bump stable nixos-20.09 to latest
4 years ago
..
hardware_tests ci: enable editorconfig checks, fix whitespace issues 4 years ago
ui_test_records
.gitignore docker: don't use nixos/nix as base, use alpine from scratch 4 years ago
Dockerfile ci: handle full dependencies in shell.nix 4 years ago
README.md
build.yml build(core): include generated resources.py in repo 4 years ago
check_fixup.sh
check_release_commit_messages.sh ci: change [NO MASTER] to [RELEASE ONLY] in release check 4 years ago
deploy.yml ci: skip submodules download where applicable 4 years ago
environment.yml ci: also remove docker pull from environment, it is not needed 4 years ago
posttest.yml build(core): include generated resources.py in repo 4 years ago
prebuild.yml ci: enable editorconfig checks, fix whitespace issues 4 years ago
prepare_ui_artifacts.py
shell.nix nix: bump stable nixos-20.09 to latest 4 years ago
test.yml ci(core): increase PYTEST_TIMEOUT for memory profiling 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.