Closed tlvu closed 4 months ago
@tlogan2000 The new Jupyter env is live. You can send announcement to our users to restart their server to get the new version.
The previous "stable" version is now the new "previous" version. I've also added a "last-py38-stable-version" to preserve our last Python 3.8 env in case our user need an even older version to reproduce their work.
We need to cull a few of those entries. beta
, alpha
, gamma
, and last
are a lot of development options for images.
We need to cull a few of those entries.
beta
,alpha
,gamma
, andlast
are a lot of development options for images.
Well beta
, alpha
, gamma
are placeholders when we have many test candidates with slight variations to test for bug fixes. As we have just experienced, it's pretty labor intensive to release a fully tested/certified Jupyter env. So all those placeholders does help during the testing phase.
Previously we deploy those test versions on our staging host but since the staging host do not have all the data, we could not fully test those environments. And the only 100% sure way to not have any surprise is to test directly on the production host ! I've seen case where the JupyterHub is unable to launch the JupyterLab server ! Having the test env on the production host eliminate this issue.
All the app specific envs are for our apps to reproduce the exact env of their runtime. Not all of them, as you can see, are on the "Stable" image. Since their have their own version, they are not force to update at the same time we release a new Stable version. Just ensuring all the notebooks passed is way too labor intensive, I do not want to add all the apps to the certification list !
The last
one are an ancien remark from David. We will eventually have last-py39, last-py311 ...
So that's the reason for all those multiple entries.
We need to cull a few of those entries.
beta
,alpha
,gamma
, andlast
are a lot of development options for images.Well
beta
,alpha
,gamma
are placeholders when we have many test candidates with slight variations to test for bug fixes. As we have just experienced, it's pretty labor intensive to release a fully tested/certified Jupyter env. So all those placeholders does help during the testing phase.Previously we deploy those test versions on our staging host but since the staging host do not have all the data, we could not fully test those environments. And the only 100% sure way to not have any surprise is to test directly on the production host ! I've seen case where the JupyterHub is unable to launch the JupyterLab server ! Having the test env on the production host eliminate this issue.
All the app specific envs are for our apps to reproduce the exact env of their runtime. Not all of them, as you can see, are on the "Stable" image. Since their have their own version, they are not force to update at the same time we release a new Stable version. Just ensuring all the notebooks passed is way too labor intensive, I do not want to add all the apps to the certification list !
The
last
one are an ancien remark from David. We will eventually have last-py39, last-py311 ...So that's the reason for all those multiple entries.
Oh forgot to add that we are trying to release more often so we are continuous trying to test newer versions. Those beta
, alpha
, gamma
will continuously be useful.
Overview
This new full build has latest of almost everything except
xclim
andravenpy
as intermediate step to smooth transition topandas
2.2 freq strings changes.Changes
New: save conda env export, DockerHub build logs and Jenkins test result in the repo to track changes much more easily between releases
Jenkins: add
SAVE_RESULTING_NOTEBOOK_TIMEOUT
for slow notebooks or slow machineJupyter env changes:
conda-pack
so we can export the conda env outside of the docker image if need to run locally without dockermajor upgrade from v2 to v3
major upgrade from v1 to v2
major upgrade to v1
major upgrade from v1 to v2
Python 3.9 to 3.11