Add PAVICS homepage notebooks to Jenkins testsuite and new Jupyter env build

[tlvu]

Overview

• Add PAVICS homepage notebooks to Jenkins testsuite and those notebooks enabled by default.

• Also released new Jupyter build for the homepage notebook. Only unzip is newly added to the Jupyter env. No other update.

Matching required notebook changes PR https://github.com/Ouranosinc/PAVICS-landing/pull/29

Matching PAVICS PR deployment change to test this PR https://github.com/bird-house/birdhouse-deploy/pull/180

Matching PR to update pavics-landing deployment config https://github.com/bird-house/birdhouse-deploy-ouranos/pull/12

Other Changes

• Add new ability to force link to stay on pavics.ouranos.ca in notebooks. Pavics homepage notebooks use a lot of .ncml so it was too much of .nc files to replicated to all the test servers.

Related Issue / Discussion

• Homepage notebooks are also deployed on Binder under tutorial-notebooks. They are already previously deployed to Jupyter env outside of tutorial-notebooks so it is kept as-is

• There is a stable interface between the homepage notebooks and Jenkins for setup the layout the notebooks requires. The stable interface means future layout changes will be transparent to Jenkins.

Additional Information

• Test passing against prod Pavics: http://jenkins.ouranos.ca/job/PAVICS-e2e-workflow-tests/job/add-pavics-homepage-notebooks-to-jenkins-testsuite/13/console

• Test passing against my dev server: http://jenkins.ouranos.ca/job/PAVICS-e2e-workflow-tests/job/add-pavics-homepage-notebooks-to-jenkins-testsuite/14/console

• Test passing against CRIM server to test remote server and ensure the IAC pipeline will also work: https://daccs-jenkins.crim.ca/job/PAVICS-e2e-workflow-tests/job/add-pavics-homepage-notebooks-to-jenkins-testsuite/3/console (one failure unrelated).

[matprov]

@tlvu By curiosity, what's the difference between https://github.com/bird-house/birdhouse-deploy-ouranos and https://github.com/Ouranosinc/birdhouse-deploy?

[tlvu]

@matprov the birdhouse-deploy-ouranos is our custom override of generic birdhouse-deploy.

These are the stuff that can not even be in any kind of optional-components because they are too specific to Ouranos, example this https://github.com/bird-house/birdhouse-deploy-ouranos/blob/e284ab8ad99419cd0d7efde8884e3d3e1bdeb95b/ouranos-config/proxy/cruesdeca-redirect.conf.template#L1-L3 or our extra scheduler jobs that is only ever relevant to us https://github.com/bird-house/birdhouse-deploy-ouranos/tree/master/scheduler-jobs. testdata deploy jobs are included in the generic one because that can potentially be of interest to others.

[matprov]

@tlvu Oh yes, my bad, given the repo name I was confused but looking at the actual files in there makes sense.

What do you think about moving this under Ouranosinc/birdhouse-deploy-ouranos since we try to avoid any org specifics under bird-house organisation?

[tlvu]

What do you think about moving this under Ouranosinc/birdhouse-deploy-ouranos since we try to avoid any org specifics under bird-house organisation?

That would be ideal but not feasible at the moment since this e2e-workflow-test is not pluggable ! We have previously discussed in https://github.com/Ouranosinc/PAVICS-e2e-workflow-tests/issues/57.

Making this e2e-workflow-test repo pluggable will also allow you guys to test your EO and NLP image against your matching notebooks. Right now, the Jupyter image is hardcoded to ours, same as the notebooks :(