You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: integration_tests/test_suites/backcompat-test-suite/README.md
+1-7Lines changed: 1 addition & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Backcompatability Integration Tests
2
2
3
-
This test suite ensures that the branch Dagster code can successfully communicate cross-process with older Dagster code.
3
+
This test suite ensures that the branch Dagster code can successfully communicate cross-process with older Dagster code. It only tests older user code (i.e. code server), because our backcompat policy is that the host process (e.g. webserver) version must be >= user code version.
4
4
5
5
## Looking at test artifacts in BuildKite
6
6
@@ -38,19 +38,13 @@ If you are on MacOS, ensure you have docker running
38
38
39
39
From `integration_tests/test_suites/backcompat-test-suite` run any of the following commands
- webserver-latest-release: webserver on most recent release (`dagster-webserver`) and user code on current branch
53
-
- webserver-earliest-release: webserver on earliest release (this will run the deprecated `dagit` package if `EARLIEST_TESTED_RELEASE` is less than 1.3.14) to maintain backcompat for, and user code on current branch
54
48
- user-code-latest-release: webserver on current branch and user code on latest minor release
55
49
- user-code-earliest-release: webserver on current branch and user code on earliest release to maintain backcompat for
0 commit comments