Now that the incremental loader has been committed, it seems like a good time to test it
in the staging environment. While a more optimized version of the loader is still under
development, the current version should be robust enough to handle anything archivable.
Plan:
- [x] D7117: swh-loader-bzr: Add module swh.loader.bzr.tasks module declared
- [x] Reference new swh-loader-bzr project in sentry [1]
- [x] Make loader run in docker
- [x] Prepare the necessary debian metadata files to allow CI package build
- [x] Debian packages built
- [x] unstable
- [x] D7132, D7133: stable is ko because conflit of breezy version (we need breezy > 3.1, only 3.0 is debian packaged).
- [x] backports python3-breezy and friends so the python3-swh.loader.bzr is finally happy on stable.
- [x] D7112: Prepare puppet manifest to deploy the worker service
- [x] D7124: Make the loader run in docker reproducible for dev
- [x] Actually deploy service on staging workers
- [x] Register the new load-bzr task-type in the scheduler (requires the python3-swh.loader.bzr install on the scheduler node)
- [x] Restart swh-scheduler-scheduler-recurrent service
- [ ] Make it consume bzr tasks (D7172: sourceforge ones, launchpad ones?)
[1] https://sentry.softwareheritage.org/organizations/swh/issues/?project=22#welcome