Now that the loader is deployed on staging (and the cvs listing is ok)
We need to have it make a pass on the cvs origins from the sourceforge lister (it's one of the forge with the most cvs origins).
And then analyze the results of the ingestion (through sentry [1]).
[1] https://sentry.softwareheritage.org/organizations/swh/issues/?project=21&query=is%3Aunresolved
| rDWAPPS Web applications | |||
| D7221 | rDWAPPSc14cfd1b2814 misc/coverage: Display counters for bzr/cvs visit types conditionally | ||
| rSPSITE puppet-swh-site | |||
| rSPSITE848c13064221 Fix sentry setup for cvs loader | |||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T2845 Improve Subversion loader and develop CVS loader | ||
| Migrated | gitlab-migration | T3691 Implement CVS loader | ||
| Migrated | gitlab-migration | T3835 staging: Ingest sourceforge cvs origins | ||
| Migrated | gitlab-migration | T3789 Adapt sourceforge lister to list cvs origins according to what the cvs loader expects | ||
| Migrated | gitlab-migration | T3947 Deploy swh.lister v2.7 |
@stsp as mentioned in the main task, it'd be neat if you could create yourself an account in sentry [1].
Ping me when it's done so i can invite you in the #swh-team so you can browse the cvs loader
related issues from there.
That reports issues with the execution context, it's pretty neat to reproduce the issue in test
context and then fix the problem \o/.
[1] https://sentry.softwareheritage.org
Thanks in advance.