Page MenuHomeSoftware Heritage

Add sentry DSN to remaining worker instances
ClosedPublic

Authored by ardumont on Dec 19 2019, 4:24 PM.

Details

Reviewers
olasd
douardda
Group Reviewers
Reviewers

Diff Detail

Repository
rSPSITE puppet-swh-site
Branch
staging
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 9909
Build 14632: arc lint + arc unit

Event Timeline

No need to touch mercurial and svn, they are already set up

See them in the sentry ui

No need to touch mercurial and svn, they are already set up

See them in the sentry ui

Yeah, $sentry_name defaults to $title

This revision is now accepted and ready to land.Dec 19 2019, 4:37 PM

Shouldn't they be loader_debian, loader_npm, and loader_pypi?

Shouldn't they be loader_debian, loader_npm, and loader_pypi?

No. They're all instances of loaders that live in swh.loader.core now.

In D2480#58893, @olasd wrote:

No. They're all instances of loaders that live in swh.loader.core now.

I know. But aren't they different enough (especially in the data they deal with) to justify having their own project in Sentry?