Changeset View
Changeset View
Standalone View
Standalone View
contrib/teamcity/build-configurations.sh
Show First 20 Lines • Show All 194 Lines • ▼ Show 20 Lines | ninja \ | ||||
check-secp256k1 \ | check-secp256k1 \ | ||||
check-univalue \ | check-univalue \ | ||||
# Functional tests | # Functional tests | ||||
ninja check-functional-extended | ninja check-functional-extended | ||||
ninja check-functional-upgrade-activated-extended | ninja check-functional-upgrade-activated-extended | ||||
;; | ;; | ||||
build-smoke-tests) | |||||
Fabien: Thinking more about this it might not even be at the right place.
What is the point of having… | |||||
jasonbcoxAuthorUnsubmitted Done Inline ActionsThe intent was this could be reused in places other than just automated commits, but it does not need to run in CI on every commit. The other existing builds that complete rather quickly (just a couple minutes) do not have good general test coverage because they're focusing on something specific (build-without-wallet, build-werror, etc). IMO the name build-smoke-tests is self explanatory when thought about in a general context. jasonbcox: The intent was this could be reused in places other than just automated commits, but it does… | |||||
# Build and run some quick tests. This build does not need perfect test | |||||
# coverage, but should detect basic failures in happy paths. | |||||
"${CI_SCRIPTS_DIR}"/build_cmake.sh | |||||
# Unit tests | |||||
run_test_bitcoin | |||||
# Functional tests | |||||
ninja check-functional | |||||
;; | |||||
build-without-wallet) | build-without-wallet) | ||||
# Build without wallet and run the unit tests. | # Build without wallet and run the unit tests. | ||||
CMAKE_FLAGS=( | CMAKE_FLAGS=( | ||||
"-DBUILD_BITCOIN_WALLET=OFF" | "-DBUILD_BITCOIN_WALLET=OFF" | ||||
) | ) | ||||
CMAKE_FLAGS="${CMAKE_FLAGS[*]}" "${CI_SCRIPTS_DIR}"/build_cmake.sh | CMAKE_FLAGS="${CMAKE_FLAGS[*]}" "${CI_SCRIPTS_DIR}"/build_cmake.sh | ||||
ninja check-bitcoin-qt | ninja check-bitcoin-qt | ||||
▲ Show 20 Lines • Show All 54 Lines • Show Last 20 Lines |
Thinking more about this it might not even be at the right place.
What is the point of having an new build type in the CI, that reports status (what does the status mean ?) for automated commits ?