Searched full:ci (Results 1 – 24 of 24) sorted by relevance
26 ./ci/check-signed-off-by.sh29 ./ci/mynewt_install.sh32 ./ci/mynewt_run.sh
53 ./ci/check-signed-off-by.sh60 ./ci/sim_install.sh63 ./ci/sim_run.sh
24 ./ci/imgtool_install.sh30 ./ci/imgtool_run.sh
61 ./ci/check-signed-off-by.sh68 - ./ci/${TEST}_install.sh71 - ./ci/${TEST}_run.sh
8 [:/root/work/tfm:rw,z mcuboot/fih-test /bin/sh -c '/root/work/tfm/mcuboot/ci/fih_test_docker/exec…28 …d):/root/work/tfm:rw,z mcuboot/fih-test /bin/sh -c '/root/work/tfm/mcuboot/ci/fih_test_docker/exec…
15 pip3 install --user -r ci/requirements.txt
23 for target in $(ls ci/mynewt_targets); do
36 python ../ci/compare_versions.py --old $last_release --new $repo_version
15 GET_FEATURES="$(pwd)/ci/get_features.py"
56 $MCUBOOT_PATH/ci/fih_test_docker/run_fi_test.sh $BOOTLOADER_AXF $SKIP_SIZE $DAMAGE_TYPE> fih_test_o…65 python3 $MCUBOOT_PATH/ci/fih_test_docker/generate_test_report.py fih_test_output.yaml
1210 ## [Testing in CI](#testing-in-ci)1214 The CI currently tests the Fault Injection Hardening feature of MCUboot by1237 To run on a desired architecture in the CI, the tests need to be executed on an1238 emulator (as real devices are not available in the CI environment). For this1245 The tests run in a docker container inside the CI VMs, to make it more easy to1246 deploy build and test environment (QEMU, compilers, interpreters). The CI VMs1253 # Implemented in ci/fih-tests_install.sh1256 # See details below. Implemented in ci/fih-tests_run.sh.1257 # Calling the function with different parameters is done by Travis CI based on1262 # implemented in ci/fih_test_docker/execute_test.sh[all …]
20 - '@mcuboot/ci/mynewt_targets/basic/syscfg.yml'
246 .arg("./ci/sim_run.sh") in run()
42 # Weather or now execute post build script after build - set to 0 for CI
362 // FIXME: travis-ci still uses gcc 4.8.4 which defaults to std=gnu90. in main()
