FYI, the jenkin-config repo (https://github.com/Ouranosinc/jenkins-config) I did to deploy Ouranos internal Jenkins uses docker-compose and has that feature that the sensitive info is separated into a different repo and is combined back at deployment time.
It's much more trivial than what we need but can serve as an inspiration.
See https://github.com/Ouranosinc/jenkins-config/blob/ba72822660e3a3cbffb396b8e865cd9af6a67aac/env.local.example#L12-L21 for private override capability and https://github.com/Ouranosinc/jenkins-config/blob/ba72822660e3a3cbffb396b8e865cd9af6a67aac/jenkins-compose.sh#L36-L45 for how the 2 repos are recombined at deployment time.
@tlvu Thanks for sharing the jenkins config. I will keep it on my mind. Currently we just use an ansible deployment script which we run manually on a VM.
I still haven’t used rancher by myself. Some of my colleagues do. As I remember from a presentation it looked simple to use and it works with
I have removed
birdhouse-birdy from the conda birdhouse channel:
birdy from conda-forge.
Oh, we are fine at Ouranos. We are not pinning any old version of birdy, and we have docker images to pin old versions, thanks for your concern.
I was simply stating the fact that removing old publicly released version might impact other people if they ever want to recreate an old environment.
In general, old publicly released versions should only be deleted if they are actually causing real harm.
Please update the doodle for the next video Conference, I ll fix the next date_time the upcoming days:
Let me know who wants to get informed also by email.
conda-forgeand not rely on the
The next VC will be
Thursday 26.Sep 15:00-16:00 UTC
See you online soon.