conda merge requestshttps://git.ligo.org/lscsoft/conda/-/merge_requests2021-10-14T13:47:48Zhttps://git.ligo.org/lscsoft/conda/-/merge_requests/33WIP: Move to pinned packages for production deployment2021-10-14T13:47:48ZDuncan Macleodduncan.macleod@ligo.orgWIP: Move to pinned packages for production deploymentThis MR is my first cut at moving from a free-for-all of packages to a production-ready pinned set of packages.
## The plan
- all LSCSoft packages are fixed to a specific build for each of `linux` and `osx` platforms
- each pack...This MR is my first cut at moving from a free-for-all of packages to a production-ready pinned set of packages.
## The plan
- all LSCSoft packages are fixed to a specific build for each of `linux` and `osx` platforms
- each package is defined in a `<package>.yaml` file that outlines the name, version, and build_string,
as well as any `skip`s, and tests
- all upstream packages are fixed to a specific version
- the upstream set is declared in a single `upstream.yaml` file that resembles a conda environment file
- CI/CD will render that set of package files into the following set of environments
- stable (fully pinned)
- proposed (approved changes to the stable environment)
- testing (requested changes to the stable environment)
- unstable (no pins at all)
## The request workflow
- open a MR that updates the `.yaml` file for one or more packages
- this should be automatically merged onto the testing branch, and a new MR opened to merge from `testing` to `proposed`
- the SCCB will then consider the request and merge the request onto `proposed` when approved
- when 'Tuesday maintenance' rolls around, `proposed` will be merged into `stable`/`master` and tagged with a datestamp
## Required development
- [ ] set up the necessary branches to support the different regimes: `stable`/`proposed`/`testing`
- [x] add `.yaml` files for all controlled packages
- [x] add one or more `.yaml` files that list out the upstream packages that we don't control
- [x] update CI to do all the things for us:
- [x] render package files into environment files
- [x] build environments for testing
- [x] run integration tests
- [x] build `latest` singularity image to unpack into `/cvmfs` (`only: [branches@lscsoft/conda]`)
- [x] build `<tag>` singularity image to unpack into `/cvmfs` (`only: [tags@lscsoft/conda]`)
- [x] create documentation page that includes the rendered environment files for both platformsDefine production release management processDuncan Macleodduncan.macleod@ligo.orgDuncan Macleodduncan.macleod@ligo.orghttps://git.ligo.org/lscsoft/conda/-/merge_requests/18Added gwcelery2019-02-16T20:14:10ZDuncan Macleodduncan.macleod@ligo.orgAdded gwceleryfor python3 only.for python3 only.Thomas DownesThomas Downeshttps://git.ligo.org/lscsoft/conda/-/merge_requests/1update deps for lalsuite development environment2019-01-29T23:20:13ZAdam Mercerupdate deps for lalsuite development environmentThis updates the dependencies for the lal development environment. There are a few build issues when building using the Conda compiler but tickets have been filed. More dependencies will probably be needed but this is a start.
Eventuall...This updates the dependencies for the lal development environment. There are a few build issues when building using the Conda compiler but tickets have been filed. More dependencies will probably be needed but this is a start.
Eventually these files should probably be in the LALSuite repository itself but for the time being this repository is as good a place as any for development.