Page History

...

• source /cds/sw/ds/ana/conda1/inst/etc/profile.d/conda.sh
• cd /cds/sw/ds/ana/conda1/manage-feedstocks/jenkins/
• conda env create -n ana-4.0.11 --file ana-env-py2.yaml
• conda env create -n ana-4.0.11-py3 --file ana-env-py3.yaml

LCLS2

First, tag lcls2 and ami repos.

checkout the 20 feedstock packages (gitHubin github.com/slac-lcls/): 

python /cds/sw/ds/ana/conda2/manage/bin/feedstock.py --clone

...

python /cds/sw/ds/ana/conda2/manage/bin/feedstock.py --cmd "pwd; git pull --rebase"

Either update version , (with new git tag) or update the build number in each meta.yaml.  conda-forge enforces manual maintenance of version numbers and sha256 hashes (no automatic determination from latest GitHub tag).  If version has changed, compute new sha256 from .tar.gz from GitHub with:

...

For a new version, remember to reset build number to zero. Commit  Commit the codechanges.

Need The next step requires an environment where "conda-smithy" is installed (we have put this in psrel's conda_build env).  After making changes to versions/sha256/buildnumber: "git commit -a -m" (using feedstock.py --cmd option).  Then rerender with "conda smithy rerender -c auto" (again using feedstock.py --cmd option).  This last command does its own git-commit for you with the changes.

 The The final "git push" of the above changes must be done carefully because it triggers the travis build, and order of the travis builds matters because of conda's "build:, host:" section dependencies (run-time dependencies do not affect this order).  We believe pure-python packages can go in the first wave, since they have no complex dependencies in "build:, host:" sections of meta.yaml. These are the waves of builds that can be launched in parallel:

...