This ensures changes to the docs, websites, and other infra do not
kick off a bunch of tests that only pertain to the node software. While these
heuristics may not be perfect, any breaking change will still be caught by
CI after changes are landed.
Details
Details
- Reviewers
Fabien - Group Reviewers
Restricted Project - Commits
- rABC665129e956ab: Only run node-related builds on diffs where the node software has changed
There is currently no good way to test this, so just read it
carefully for now.
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- rod-node-builds
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 14173 Build 28336: Build Diff lint-circular-dependencies · build-without-wallet · build-diff · build-clang-tidy · build-debug · build-clang Build 28335: arc lint + arc unit
Event Timeline
Comment Actions
Just make a template
node:
runOnDiffRegex:
- cmake/
- src/
- test/and use it everywhere
Comment Actions
Used a template where it makes sense. For the others, it doesn't make sense to run them when
only changes to the functional tests are made.
Comment Actions
Use the template on the clang builds. Even though changes to functional tests only will be a false positive,
catching changes to /cmake are important. Functional test only changes are not super common, so we
can live with this tradeoff to reduce maintenance overhead and reduce false negatives.
Comment Actions
The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience.
Comment Actions
The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience.
Comment Actions
The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience.