search

Ouranosinc / jenkins-config

Jenkins deployment configurations.
MIT License
0 stars 1 forks source link

Add various env vars to better customize different Jenkins instances #6

Closed tlvu closed 4 years ago

tlvu commented 4 years ago

Each organization can have multiple Jenkins instances running (production, staging, multiple dev instances). We do not want all of them to nightly test the production PAVICS.

This PR adds the IS_PROD and ENABLE_SCHEDULED_TRIGGER env var so each Jenkins instances can set those according to their "role".

Multiples organizations can deploy this Jenkins config. We do not want all of them to test the same PAVICS from Ouranos (and DOS attack it). Each organization should have their own local production PAVICS.

This PR adds the DEFAULT_PAVICS_HOST env var so each organization can set their Jenkins instance to test their local production PAVICS.

It would be nice for the same Jenkins instance to be able to nigthly test more than 1 PAVICS instance. I attempted to create more than 1 job from the same test repo and override the DEFAULT_PAVICS_HOST above to test another PAVICS. This is not working due to know incompatibility between the envinject and the pipeline plugin. Still kept the work for later.

Upgraded Jenkins master image to include envinject plugin pre-installed.

@huard, @tlogan2000 FYI only no need to approve.

davidcaron commented 4 years ago

I can't comment on jcasc configuration files, but thanks for the heads up and adding the default host in the configuration.