search

opensafely-core / job-runner

A client for running jobs in an OpenSAFELY secure environment, requested via job-server (q.v.)
Other
4 stars 5 forks source link

Automate deployment to backends #507

Open lucyb opened 1 year ago

lucyb commented 1 year ago

Changes should be deployed automatically to the secure backends. At the moment, someone has to access each of them, run git pull and then restart job-runner.

This is time consuming and leads to delays. It's also not scalable and as we grow it would be useful to automate this where possible.

Ideally, we'd like to deploy whenever we make changes, possibly using Conventional Commits.

However, because we can't push anything directly to the backends, we'll need to setup the backends to pull in any changes. We could do this using a cronjob that checks regularly for any changes and automatically applies them.

bloodearnest commented 1 year ago

This is related to moving to running job-runner in docker. If we do that, docker-compose will automatically check and pull/deploy new images. This is how release-hatch is deployed