Remove hardcoded package version from NVIDIA image#3671
Conversation
|
Created a staging project on OBS for 16.0: home:pushman:BCI:Staging:16.0:16.0-3671 Build ResultsRepository
Repository
Repository
Repository
Repository
Repository
Repository
Repository
Build succeeded ✅ To run BCI-tests against this PR, use the following command: OS_VERSION=16.0 TARGET=custom BASEURL=registry.opensuse.org/home/pushman/bci/staging/16.0/16.0-3671/ tox -- -n autoThe following images can be pulled from the staging project:
|
|
Created a staging project on OBS for 16.1: home:pushman:BCI:Staging:16.1:16.1-3671 Build ResultsRepository
Repository
Repository
Repository
Repository
Repository
Repository
Repository
Build succeeded ✅ To run BCI-tests against this PR, use the following command: OS_VERSION=16.1 TARGET=custom BASEURL=registry.opensuse.org/home/pushman/bci/staging/16.1/16.1-3671/ tox -- -n autoThe following images can be pulled from the staging project:
|
| "7": { | ||
| "latest": "6.4.0-150700.53.34", | ||
| "versions": [ | ||
| "6.4.0-150700.51", |
There was a problem hiding this comment.
do we ever need to keep the release numbers for anything other than the same version? just checking. because then we could also automatically cleanup the list as soon as the version part of the ver-release is changing. and we only need to record the release part as well (but that would be optional)
There was a problem hiding this comment.
I prefer to keep the full version, it is easier to understand. Unfortunately for AMD and NVIDIA we need all kernel versions ever released, but in theory, this will be needed only for a few selected packages, right now only kernel and its flavors.
We could change to only save 6.12.0 once and 160000.27 and else multiple times, but this gets trickier to handle IMHO.
There was a problem hiding this comment.
I prefer to keep the full version, it is easier to understand. Unfortunately for AMD and NVIDIA we need all kernel versions ever released
ok, but only for the code stream I believe (e.g. 16.0/16.1 share the same kernel, but 16.2 won't)
There was a problem hiding this comment.
I'm not sure we need to change anything here, the json is cleaner now, and only two packages have the release history, not that bad.
If enabled, also track the previous versions of a given package.
Allow package_versions.json to also include the release version. For this to work properly, we need to fetch the package information from SCC instead of OBS.
Remove the hardcoded kernel versions from the NVIDIA image and migrate it to package_versions.json.
9f60213 to
84eab6f
Compare
Grab the released package version from SCC, the only true source of truth for all codestreams.
Save all known versions to
package_versions.json.