It ran once and we got ~214 origins about it (source: db: swh-lister, table: bitbucket_repo)
It's not been deployed through the scheduler though (it most probably anterior to the scheduler).
Once the fix is done ([2] pushed, packaged), deploy it through the "standard" scheduling facilities.
[1] Related T1826
[2] Related D1634
It's not been deployed through the scheduler though (it most probably anterior to the scheduler).
Maybe not, i see task-type references in the scheduler db...
Anyway, it got stopped and configuration got changed somehow.
So meh, please @ardumont fix that.
Maybe not, i see task-type references in the scheduler db...
Hi ho, i see reference in 50-swh-data.sql but not in the real scheduler db.
So the initial description is correct in the end.