Skip to content

Document new GWCelery deployment stages

The manual section Continuous deployment says:

There are two instances of GWCelery that are running on the LIGO-Caltech computing cluster and that are managed in this manner:

  • Playground: The playground instance is re-deployed on every push to main that passes the unit tests. It uses the gwcelery.conf.playground configuration preset.
  • Production: The production instance is re-deployed only when manually triggered through GitLab. It uses the gwcelery.conf.production configuration preset.

When we observe that the Playground instance shows correct end-to-end behavior, we have the option of triggering a re-deployment to Production. Deployment to production should preferably occur at a release. The procedure for performing a release is described below.

This is out of date. Update it to document the name and purpose of the other deployments.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information