From 45b8bd97d9aece8b4bc1e511b94cbcc1d5ec566e Mon Sep 17 00:00:00 2001 From: Matt Rendina Date: Fri, 28 Jun 2019 13:16:53 -0400 Subject: Update doc --- Jenkinsfile | 2 +- README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Jenkinsfile b/Jenkinsfile index 6bd8169..3bbc86f 100644 --- a/Jenkinsfile +++ b/Jenkinsfile @@ -1,4 +1,4 @@ -//@Library('utils@dow-filter') _ +//@Library('utils@master') _ // [skip ci] and [ci skip] have no effect here. if (utils.scm_checkout(['skip_disable':true])) return diff --git a/README.md b/README.md index 9c068f4..9de3bf4 100644 --- a/README.md +++ b/README.md @@ -114,7 +114,7 @@ It has the following properties: | --- | --- | --- | --- | | `nodetype` | string | yes | The Jenkins node label to which the build is assigned | | `name` | string | yes | A (short) arbitrary name/description of the build configuration. Builds are named `/` in the build status GUI. I.e. "linux/stable" or "linux/debug" | -| `run_on_days` | list of strings | no | Primarily for periodic regression test (RT) job use. A list of day-of-week names on which to execute the associated BuildConfig. Example: `bc0.run_on_days = ['sat', 'sun']` to only run the BuildConfig on those two days. | +| `run_on_days` | list of strings | no | (When absent, default behavior is to always run the BuildConfig.) Primarily for periodic regression test (RT) job use. A list of day-of-week names on which to execute the associated BuildConfig. Example: `bc0.run_on_days = ['sat', 'sun']` to only run the BuildConfig on those two days. | | `conda_packages` | list of strings | no | If this list is defined, the associated build job will create a temporary conda environment to host the job which contains the packages specified. Package specifications are of the form
  • ``
  • `=`
Example: `bc0.conda_packages = ["pytest", "requests", "numpy=1.14.3"]` | | `conda_override_channels` | boolean | no | Instructs the conda environment creation process to not implicitly prepend the anaconda defaults channel to the list of channels used. This allows the priority of channels to be used for environment creation to be specified exactly in the order of channels provided in the `conda_channels` list, described below. If `conda_packages` is not defined in the Jenkinsfile this property is ignored. | | `conda_channels` | list of strings | no | The list of channels, in order of search priority, to use when retrieving packages for installation. If `conda_override_channels` is not defined, this list will have the conda `defaults` channel implicitly prepended to it at installation time. If `conda_packages` is not defined in the Jenkinsfile this property is ignored. Example: `bc0.conda_channels = ["http://ssb.stsci.edu/astroconda"]` | -- cgit