Page MenuHomeSoftware Heritage

Enable Sentry for CLIs, and Gunicorn and Celery workers.
ClosedPublic

Authored by vlorentz on Dec 10 2019, 2:53 PM.

Diff Detail

Repository
rDENV Development environment
Branch
sentry
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 9672
Build 14254: arc lint + arc unit

Event Timeline

ardumont added inline comments.
docker/env/common_python.env
5

why is it empty?

docker/env/common_python.env
5

Because no sentry in the docker env?

docker/env/common_python.env
5

We decided against running Sentry in our Docker env, it's too big and too niche. Instead, you should run it on your own.

docker/env/common_python.env
5

ack.

But why do we need to specify this if this is empty?

This revision is now accepted and ready to land.Dec 10 2019, 3:06 PM
docker/env/common_python.env
5

We don't need to.

comment out SWH_SENTRY_DSN.

vlorentz retitled this revision from [WIP] Enable Sentry for CLIs and Gunicorn workers. to Enable Sentry for CLIs and Gunicorn workers..
douardda added inline comments.
docker/docker-compose.yml
270

? swh-deposit-api is now swh-scheduler

docker/docker-compose.yml
270

oops, I messed up my rebase

vlorentz retitled this revision from Enable Sentry for CLIs and Gunicorn workers. to Enable Sentry for CLIs, and Gunicorn and Celery workers..Dec 11 2019, 2:12 PM