Support Running ALL Tests in One Build

[kj4ezj]

Change Description

This pull request enables engineers to start a build with RUN_ALL_TESTS set to true to run ALL tests in the CICD pipeline, for example, to include the time-consuming post-merge checks on a pre-merge build.

Pinned and unpinned builds and tests must still be done in separate builds due to step (AKA Buildkite job) name collisions. This is possible to do, but the cost and risk of changing the step names and updating the infrastructure built around them is not worth the tradeoff, as we have learned in the past.

Tested Working

Some builds show the pipeline step generation and then were cancelled so as not to waste agents, while other builds show pipeline step generation and passing tests.

• Pinned
  • Build 21527 -- normal build
  • Build 21529 -- ran all tests by setting RUN_ALL_TESTS='true'
• Unpinned
  • Build 1556 -- normal build
  • Build 1558 -- ran all tests by setting RUN_ALL_TESTS='true'

See Also

• Support Running ALL Tests in One Build
  • Pull request 8961 -- eos:develop
  • Pull request 8968 -- eos:release/2.0.x
  • Pull request 8969 -- eos:release/1.8.x
• Support Triggering a Build that Runs ALL Tests in One Build
  • Pull request 9001 -- eos:develop
  • Pull request 9002 -- eos:release/2.0.x
  • Pull request 9003 -- eos:release/1.8.x

Consensus Changes

• Consensus Changes
  None.

API Changes

• API Changes
  None.

Documentation Additions

• Documentation Additions
  None.

[scottarnette]