The first development phase is done.
It's time to deploy it and fix the eventual remaing paper cuts.
Plan
- [x] Tag cvs loader v0.1.1
- [x] Eventual missing part for the ci to actually pypi package the module
- [x] T3798: debian packaging the repository module
- [x] D6851: Add swh-worker@loader_cvs service puppet manifest
- [x] Actually deploy in staging
- [x] Register load-cvs in the staging scheduler db (`swh scheduler task-type register`)
- [x] D6863: Activate sentry for the cvs loader
- [ ] Invite @stsp in sentry (so he can browse through issues easily)
- [x] Tag the proper v0.1 once D6823 lands and push the tags (jenkins will do the packaging)
- [ ] Unstuck build if problem [2]
- [ ] Upgrade python3-swh.loader.cvs package v0.1 on workers and restart services
- [ ] Make it consume the actual sourceforge cvs origins (requires T3789 adaptation in the lister to be deployed first)
[1] P1242
[2] https://jenkins.softwareheritage.org/job/debian/job/packages/job/DLDCVS/job/gbp-buildpackage/5/console