[Add Forge Now] process https://gitlab.developers.cam.ac.uk
https://webapp.staging.swh.network/admin/add-forge/request/68/
Type: gitlab
Production request: https://archive.softwareheritage.org/admin/add-forge/request/297/
https://webapp.staging.swh.network/admin/add-forge/request/68/
Type: gitlab
Production request: https://archive.softwareheritage.org/admin/add-forge/request/297/
changed milestone to %Extend archive coverage [Roadmap - Collect]
added AddForgeNow label
Request successfully processed in staging environment.
For the pipeline details, see:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/5910.
Request completly messed up in production environment.
For the pipeline details, see:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/5910.
On production environment listing the 839 origins of this forge took more time than the listing delay (300s).
I relaunch the check-listed-origins
job.
Request successfully processed in production environment.
For the pipeline details, see:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/5910.
changed the description