-
Type:
Task
-
Resolution: Done
-
Priority:
L3 - Default
-
Affects Version/s: None
-
Component/s: CI
-
None
Current state:
At the moment, the Sidetrack pipeline has two behaviors:
- When triggered daily on an SCM change (standalone and on master), it will execute the QA CRDB stages (sql-scripts, upgrade-db, instance-migration, old-engine, rolling-update, large-dataset-tests);
- When triggered by an upstream build:
- On the master branch, it will execute the UNIT CRDB stages (engine-unit, engine-unit-auth, webapp-unit, webapp-unit-auth)
- On a PR, it will execute stages that match the PR labels assigned.
Problem:
Scenarios [1] and [2.1] are executed on the master branch, and the results are kept on the same branch. At the moment, the last 5 builds per branch are kept. This means that the results of the Daily build [1] will be removed, if too many master builds [2.1] are executed. As a result, a failure of the CRDB QA tests might be missed.
Possible solutions:
- We only execute the Sidetrack pipeline daily on an SCM change.
- We use the Main EE pipeline pattern and create separate pipelines for the daily and master builds.