Page History

...

Need an environment where "conda-smithy" is installed (we have put this in psrel's conda_build env).  After making changes to versions/sha256/buildnumber, then : "git commit -a -m" (using feedstock.py --cmd option).  Then rerender with "conda smithy rerender -c auto" , then push.  Watch the status of the builds at https://travis-ci.com(again using feedstock.py --cmd option).

 The "git push" must be done carefully because it triggers the travis build, and order 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 should 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:

• libnl, libnl3, roentdek, amityping, prometheus-cpp, libusdusb4, psmon, networkfox, rogue, epix, lcls2_timetool, cameralink-gateway, lcls2-pgp-pcie-apps, xtcdata, ami
• rmda-core (depends on libnl), psalg (depends on xtcdata)
• fabric (depends rmda-core), psana (depends on psalg)
• psdaq (depend on psalg, fabric)

The 4 build waves above can be launched with a command like this (then watch for them to complete at https://travis-ci.com):

python /cds/sw/ds/ana/conda2/manage/bin/feedstock.py --cmd "git push" --wave 1

If a package is built for python build matrix tells it to build for the officially supported conda-forge versions (3.6,3.7,3.8).

...