Page History

...

make sure the psana1-py2 env is used (needed by py2 ana-rel-admin)
cd /cds/sw/ds/ana/conda1/manage/
ana-rel-admin --force --cmd psana-conda-src --name 2.0.6 --basedir `pwd`

cp .tar.gz to where travis GitHub can see it:
/reg/g/psdm/web/swdoc/tutorials/

...

git push launches the build on travis GitHub (using GitHub Actions) when it finishes it uploads it
to anaconda.org/valmar (currently) but need to switch to it to officiallcls-i

this is our real control of the build process (e.g. .travis.yml the GitHub Actions Workflow yaml file gets
generated automatically)

...

feedstocks:
libpressio-feedstock psana1-py2-feedstock sz-feedstock
ndarray-psana-feedstock psgeom-feedstock ztcav-py2-feedstock xtcav2-feedstock
ndarray-psana-py2-feedstock psocake-py2-feedstock psocake-feedstock
psana1-feedstock stdcompat-feedstock

...

After all packages have finished building on TravisCI,GitHub (Unfortunately, GitHub Actions do not provide a "dashboard" to check if the packages have been built or when they are finished. There are only two ways to check this: 1) Manually check every feedstock repository (Under the "Actions" tab) 2) Wait for either the package to appear on anaconda.org/lcls-i or for an email notifying a failure to arrive):

As psreldev:

• source /cds/sw/ds/ana/conda1/inst/etc/profile.d/conda.sh
• cd /cds/sw/ds/ana/conda1/manage/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

...

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

...

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 we were in conda-forge officially, they take care of these build-order dependencies (but not the versions/sha256/buildnumber).  They may have a bot that tells you that the version was updated, but we still have to update the version number by hand. We haven't gone the conda-forge route because (1) we don't know how much work it is, and (2) cannot upload source .tar.gz to conda-forge, usually get it from GitHub, but the rogue packages are not public.

Unfortunately, GitHub Actions do not provide a "dashboard" to check if the packages have been built or when they are finished. There are only two ways to check this: 1) Manually check every feedstock repository (Under the "Actions" tab) 2) Wait for either the package to appear on anaconda.org/lcls-ii or for an email notifying a failure to arrive.

To create the environment as psrel, use these commands:

...