-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support birdhouse-deploy>=2.4.0 #10
base: master
Are you sure you want to change the base?
Conversation
Can someone advise what the release procedure is for this repo? |
Add details in the CHANGES (I see that https://github.com/bird-house/pavics-jupyter-base/tree/0.5.0 exists, but the section is not updated, so need to adjust this). Once merged, DockerHub should auto-build the latest with I see that https://github.com/bird-house/pavics-jupyter-base/tree/support-birdhouse-deploy-2.4.0 build fails: https://hub.docker.com/repository/registry-1.docker.io/birdhouse/pavics-jupyter-base/builds/e9ffc5ec-9b3e-4ca0-b5b0-68875900e0c4
Need to address this before merging/tag/release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See failed build and necessary adjustments (to investigate).
This updates the
scheduler-jobs/deploy_data_pavics_jupyter.env
script to allow it to discover the log directory using theBIRDHOUSE_LOG_DIR
or thePAVICS_LOG_DIR
environment variable.This is in order to support the variable name changes introduced in birdhouse-deploy versions >= 2.4.0.