Skip to content

Clarify constraints use in canary run in CI diagrams #35858

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
potiuk merged 1 commit into from
Nov 26, 2023
Merged

Clarify constraints use in canary run in CI diagrams #35858

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions CI_DIAGRAMS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -314,7 +314,7 @@ the "v2-*-test" branches. The "Canary" run attempts to upgrade dependencies to t
and quickly pushes an early cache the CI/PROD images to the GitHub Registry - so that pull requests
can quickly use the new cache - this is useful when Dockerfile or installation scripts change because such
cache will already have the latest Dockerfile and scripts pushed even if some tests will fail.
When successful, the run updates the constraints files in the "constraints-main" branch with the latest
When successful, the run updates the constraints files in the "constraints-BRANCH" branch with the latest
constraints and pushes both cache and latest CI/PROD images to the GitHub Registry.

```mermaid
Expand Down Expand Up @@ -410,17 +410,21 @@ sequenceDiagram
end
par
GitHub Registry ->> Tests: Use cache from registry
Note over Tests: Build CI latest images/cache<br>Use pushed constraints
Airflow Repo ->> Tests: Get latest constraints from 'constraints-BRANCH'
Note over Tests: Build CI latest images/cache
Tests ->> GitHub Registry: Push CI latest images/cache
GitHub Registry ->> Tests: Use cache from registry
Note over Tests: Build PROD latest images/cache<br>Use pushed constraints
Airflow Repo ->> Tests: Get latest constraints from 'constraints-BRANCH'
Note over Tests: Build PROD latest images/cache
Tests ->> GitHub Registry: Push PROD latest images/cache
and
GitHub Registry ->> Tests: Use cache from registry
Note over Tests: Build ARM CI cache<br>Use pushed constraints
Airflow Repo ->> Tests: Get latest constraints from 'constraints-BRANCH'
Note over Tests: Build ARM CI cache
Tests ->> GitHub Registry: Push ARM CI cache
GitHub Registry ->> Tests: Use cache from registry
Note over Tests: Build ARM PROD cache<br>Use pushed constraints
Airflow Repo ->> Tests: Get latest constraints from 'constraints-BRANCH'
Note over Tests: Build ARM PROD cache
Tests ->> GitHub Registry: Push ARM PROD cache
end
Tests -->> Airflow Repo: Status update
Expand Down