vdk-plugins: test only oldest and newest supported python version #1811
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As part of my effort to stabilize our Nightly builds and the CICD cluster I am removing testing middle versions. We test with the oldest supported version to make sure we do not use a new feature added lately which would break compatability. We test with newest version to make sure that it runs with newest version. Although the python itself is very likely to be backwords compatible (for minor release), there are sometimes small changes that are not and same cannot be told for 3th party dependecies we may use which may not support latest version fully. Testing Done: this CI Signed-off-by: Antoni Ivanov <aivanov@vmware.com>
gageorgiev
approved these changes
Mar 31, 2023
ivakoleva
approved these changes
Mar 31, 2023
There was a problem hiding this comment.
What are the chances for bringing back those deleted ci jobs?
For example, the possibility of having resources updated or increased in accordance with our current needs (since onboarding of new release cycles). Or, not on every change, but occasionally checking the compliance with all minor versions?
In case the chance is good, then, we may consider a configurable or feature flag approach towards this.
murphp15
approved these changes
Mar 31, 2023
yonitoo
pushed a commit
that referenced
this pull request
Apr 4, 2023
) As part of my effort to stabilize our Nightly builds and the CICD cluster I am removing testing middle versions. We test with the oldest supported version to make sure we do not use a new feature added lately which would break compatability. We test with newest version to make sure that it runs with newest version. Although the python itself is very likely to be backwords compatible (for minor release), there are sometimes small changes that are not and same cannot be told for 3th party dependecies we may use which may not support latest version fully. Testing Done: this CI Signed-off-by: Antoni Ivanov <aivanov@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of my effort to stabilize our Nightly builds and the CICD cluster I am removing testing middle versions.
We test with the oldest supported version to make sure we do not use a new feature added lately which would break compatability.
We test with newest version to make sure that it runs with newest version. Although the python itself is very likely to be backwords compatible (for minor release), there are sometimes small changes that are not and same cannot be told for 3th party dependecies we may use which may not support latest version fully.
Testing Done: this CI