Support Triggering a Build that Runs ALL Tests in One Build

[kj4ezj]

Change Description

After merging pull request 8968, I created the eosio-full-test-suite pipeline to trigger a synchronous build on the eosio and eosio-build-unpinned pipelines simultaneously, each with RUN_ALL_TESTS set to true. Where the current pipelines only run some tests when certain conditions are met, this new pipeline Blockchain requested allows engineers to override those conditions to run ALL tests on suspect code with just one click.

This pull request adjust some logic that is only encountered during builds that were triggered by other builds.

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.

• Normal Builds -- Cancelled after step generation
  • Build 21647 -- pinned
  • Build 1587 -- unpinned
• Triggering Build 4 -- RUN_ALL_TESTS='true'
  • Triggered Build 21648 -- pinned
  • Triggered Build 1588 -- unpinned

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]

squiggle