CI/CD and various scripts in .github/scripts
#1276
-
I was looking through the CI/CD workflows for the project, and came across the calls to the installation and testing scripts in the It feels a bit strange having many scripts for this setup, rather than just invoking the Setup Miniconda workflow with the appropriate environment file. I think using this workflow would greatly simplify the CI/CD eliminating the use for the custom scripts (and would also make for a good example for fellow researchers to copy to get started with unit testing and CI/CD in their parcels projects). My questions are:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Thanks for the question, @VeckoTheGecko. The CI was set up for us by IT support from Utrecht University (specifically @jelletreep), building on some older legacy code.
Yes, I only think for CI/CD. The packaging is done at https://github.com/conda-forge/parcels-feedstock for anaconda, and at https://github.com/OceanParcels/parcels/blob/master/.github/workflows/pypi-release.yaml for PyPi
I think these are remnants of when we also tested for plotting and visualisation. See https://github.com/OceanParcels/parcels/blob/master/tests/test_scripts.py. But I'm not entirely sure this actually works anymore? |
Beta Was this translation helpful? Give feedback.
Thanks for the question, @VeckoTheGecko. The CI was set up for us by IT support from Utrecht University (specifically @jelletreep), building on some older legacy code.
Yes, I only think for CI/CD. The packaging is done at https://github.com/conda-forge/parcels-feedstock for anaconda, and at https://github.com/OceanParcels/parcels/blob/master/.github/workflows/pypi-release.yaml for PyPi