# CI pipeline (Generated automatically by `tools/generate_ci_docs.py`. Do not edit by hand.) It consists of multiple stages below, each having one or more jobs Latest CI pipeline of master branch can be seen at [https://gitlab.com/satoshilabs/trezor/trezor-firmware/-/pipelines/master/latest](https://gitlab.com/satoshilabs/trezor/trezor-firmware/-/pipelines/master/latest) ## ENVIRONMENT stage - [environment.yml](https://github.com/trezor/trezor-firmware/blob/master/ci/environment.yml) Connected with creating the testing image for CI. Consists of **3 jobs** below: ### [.environment](https://github.com/trezor/trezor-firmware/blob/master/ci/environment.yml#L7) Environment job builds the `ci/Dockerfile` and pushes the built docker image into our GitLab registry. Since modifications of this Dockerfile are very rare this is a _manual_ job which needs to be triggered on GitLab. Almost all CI jobs run inside this docker image. ### [environment manual](https://github.com/trezor/trezor-firmware/blob/master/ci/environment.yml#L31) ### [environment scheduled](https://github.com/trezor/trezor-firmware/blob/master/ci/environment.yml#L35) --- ## PREBUILD stage - [prebuild.yml](https://github.com/trezor/trezor-firmware/blob/master/ci/prebuild.yml) Static checks on the code. Consists of **7 jobs** below: ### [style prebuild](https://github.com/trezor/trezor-firmware/blob/master/ci/prebuild.yml#L16) Check the code for style correctness and perform some static code analysis. Biggest part is the python one - using `flake8`, `isort`, `black`, `pylint` and `pyright`, also checking Rust files by `rustfmt` and C files by `clang-format`. Changelogs formats are checked. ### [common prebuild](https://github.com/trezor/trezor-firmware/blob/master/ci/prebuild.yml#L25) Check validity of coin definitions and protobuf files. ### [gen prebuild](https://github.com/trezor/trezor-firmware/blob/master/ci/prebuild.yml#L32) Check validity of auto-generated files. ### [editor prebuild](https://github.com/trezor/trezor-firmware/blob/master/ci/prebuild.yml#L39) Checking format of .editorconfig files. ### [yaml prebuild](https://github.com/trezor/trezor-firmware/blob/master/ci/prebuild.yml#L46) All .yml/.yaml files are checked for syntax validity and other correctness. ### [release commit messages prebuild](https://github.com/trezor/trezor-firmware/blob/master/ci/prebuild.yml#L53) Checking the format of release commit messages. ### [changelog prebuild](https://github.com/trezor/trezor-firmware/blob/master/ci/prebuild.yml#L70) Verifying that all commits changing some functionality have a changelog entry or contain `[no changelog]` in the commit message. --- ## BUILD stage - [build.yml](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml) All builds are published as artifacts so they can be downloaded and used. Consists of **28 jobs** below: ### [core fw regular build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L20) Build of Core into firmware. Regular version. **Are you looking for Trezor T firmware build? This is most likely it.** ### [core fw regular debug build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L41) Build of Core into firmware with enabled _debug_ mode. In debug mode you can upload mnemonic seed, use debug link etc. which enables device tests. Storage on the device gets wiped on every start in this firmware. ### [core fw regular production build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L54) ### [core fw btconly build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L77) Build of Core into firmware. Bitcoin-only version. ### [core fw btconly debug build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L94) ### [core fw btconly production build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L117) ### [core fw btconly t1 build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L136) ### [core unix regular build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L154) Non-frozen emulator build. This means you still need Python files present which get interpreted. ### [core unix regular asan build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L166) ### [core unix frozen regular build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L185) Build of Core into UNIX emulator. Something you can run on your laptop. Frozen version. That means you do not need any other files to run it, it is just a single binary file that you can execute directly. ### [core unix frozen btconly debug build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L202) Build of Core into UNIX emulator. Something you can run on your laptop. Frozen version. That means you do not need any other files to run it, it is just a single binary file that you can execute directly. See [Emulator](../core/emulator/index.md) for more info. Debug mode enabled, Bitcoin-only version. ### [core unix frozen btconly debug asan build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L218) ### [core unix frozen debug build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L241) Build of Core into UNIX emulator. Something you can run on your laptop. Frozen version. That means you do not need any other files to run it, it is just a single binary file that you can execute directly. **Are you looking for a Trezor T emulator? This is most likely it.** ### [core unix frozen ui2 debug build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L255) ### [core unix frozen debug asan build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L269) ### [core unix frozen debug build arm](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L285) ### [core unix frozen btconly debug t1 build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L307) ### [core macos frozen regular build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L323) ### [crypto build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L348) Build of our cryptographic library, which is then incorporated into the other builds. ### [legacy fw regular build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L377) ### [legacy fw regular debug build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L393) ### [legacy fw btconly build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L410) ### [legacy fw btconly debug build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L429) ### [legacy emu regular debug build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L450) Regular version (not only Bitcoin) of above. **Are you looking for a Trezor One emulator? This is most likely it.** ### [legacy emu regular debug asan build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L465) ### [legacy emu regular debug build arm](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L483) ### [legacy emu btconly debug build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L509) Build of Legacy into UNIX emulator. Use keyboard arrows to emulate button presses. Bitcoin-only version. ### [legacy emu btconly debug asan build](https://github.com/trezor/trezor-firmware/blob/master/ci/build.yml#L526) --- ## TEST stage - [test.yml](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml) All the tests run test cases on the freshly built emulators from the previous `BUILD` stage. Consists of **35 jobs** below: ### [core unit test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L15) Python and rust unit tests, checking TT functionality. ### [core unit ui2 test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L23) ### [core unit asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L32) ### [core unit t1 test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L49) ### [core device test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L64) Device tests for Core. Running device tests and also comparing screens with the expected UI result. See artifacts for a comprehensive report of UI. See [docs/tests/ui-tests](../tests/ui-tests.md) for more info. ### [core device ui2 test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L93) ### [core device asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L127) ### [core btconly device test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L146) Device tests excluding altcoins, only for BTC. ### [core btconly device asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L166) ### [core monero test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L187) Monero tests. ### [core monero asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L206) ### [core u2f test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L228) Tests for U2F and HID. ### [core u2f asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L247) ### [core fido2 test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L265) FIDO2 device tests. ### [core fido2 asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L288) ### [core click test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L308) Click tests. See [docs/tests/click-tests](../tests/click-tests.md) for more info. ### [core click asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L325) ### [core upgrade test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L346) Upgrade tests. See [docs/tests/upgrade-tests](../tests/upgrade-tests.md) for more info. ### [core upgrade asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L365) ### [core persistence test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L387) Persistence tests. ### [core persistence asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L403) ### [core hwi test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L421) ### [crypto test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L439) ### [legacy device test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L470) ### [legacy asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L497) ### [legacy btconly test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L509) ### [legacy btconly asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L529) ### [legacy upgrade test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L544) ### [legacy upgrade asan test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L563) ### [legacy hwi test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L584) ### [python test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L603) ### [python support test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L622) ### [storage test](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L632) ### [core unix memory profiler](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L656) ### [connect test core](https://github.com/trezor/trezor-firmware/blob/master/ci/test.yml#L680) --- ## TEST-HW stage - [test-hw.yml](https://github.com/trezor/trezor-firmware/blob/master/ci/test-hw.yml) Consists of **5 jobs** below: ### [hardware core regular device test](https://github.com/trezor/trezor-firmware/blob/master/ci/test-hw.yml#L25) [Device tests](../tests/device-tests.md) that run against an actual physical Trezor T. The device needs to have special bootloader, found in `core/embed/bootloader_ci`, that makes it possible to flash firmware without confirmation on the touchscreen. All hardware tests are run nightly on the `master` branch, as well as on push to branches with whitelisted prefix. If you want hardware tests ran on your branch, make sure its name starts with `hw/`. Currently it's not possible to run all regular TT tests without getting into a state where the micropython heap is too fragmented and allocations fail (often manifesting as a stuck test case). For that reason some tests are skipped. See also: https://github.com/trezor/trezor-firmware/issues/1371 ### [hardware core btconly device test](https://github.com/trezor/trezor-firmware/blob/master/ci/test-hw.yml#L54) Also device tests on physical Trezor T but with Bitcoin-only firmware. ### [hardware core monero test](https://github.com/trezor/trezor-firmware/blob/master/ci/test-hw.yml#L83) ### [hardware legacy regular device test](https://github.com/trezor/trezor-firmware/blob/master/ci/test-hw.yml#L113) [Device tests](../tests/device-tests.md) executed on physical Trezor 1. This works thanks to [tpmb](https://github.com/mmahut/tpmb), which is a small arduino device capable of pushing an actual buttons on the device. ### [hardware legacy btconly device test](https://github.com/trezor/trezor-firmware/blob/master/ci/test-hw.yml#L137) Also device tests on physical Trezor 1 but with Bitcoin-only firmware. --- ## POSTTEST stage - [posttest.yml](https://github.com/trezor/trezor-firmware/blob/master/ci/posttest.yml) Consists of **2 jobs** below: ### [core unix coverage posttest](https://github.com/trezor/trezor-firmware/blob/master/ci/posttest.yml#L10) ### [unix ui changes](https://github.com/trezor/trezor-firmware/blob/master/ci/posttest.yml#L31) --- ## DEPLOY stage - [deploy.yml](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml) Consists of **14 jobs** below: ### [release core fw regular deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L5) ### [release core fw btconly deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L26) ### [release core fw regular debug deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L47) ### [release core fw btconly debug deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L68) ### [release legacy fw regular deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L91) ### [release legacy fw btconly deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L112) ### [release legacy fw regular debug deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L133) ### [release legacy fw btconly debug deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L154) ### [release core unix debug deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L177) ### [release legacy unix debug deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L202) ### [ui tests fixtures deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L229) ### [ui tests ui2 fixtures deploy](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L249) ### [sync emulators to aws](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L270) ### [common sync](https://github.com/trezor/trezor-firmware/blob/master/ci/deploy.yml#L295) ---