The jenkins_wrapper.sh script in lsst-sqre/ci-scripts was changed to make the conda environment name explicitly contain its git hash. This allows Jenkins run-rebuild pipelines to run safely even while preserving state from run to run.

Unfortunately, the nightly-release pipeline uses run-rebuild but also activates the same conda environment again in run-publish in order to eups distrib create packages. The name of the environment in run-publish is the default used by setup.sh, or lsst-scipipe without git hash.

We need to ensure that the run-publish activation embedded in https://github.com/lsst-dm/jenkins-dm-jobs/blob/master/pipelines/release/run_publish.groovy#L87 uses the correct conda environment name, either by setting the LSST_CONDA_ENV_NAME variable or passing an argument.