[Add Forge Now] process https://repo.or.cz

https://webapp.staging.swh.network/admin/add-forge/request/55/
Type: gitweb

changed milestone to %Extend archive coverage [Roadmap - Collect]

added AddForgeNow label

Request completly messed up in staging environment.
For the pipeline details, see:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/5451.

Request completly messed up in production environment.
For the pipeline details, see:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/5451.

First job execution, the lister-gitweb pod creation took too long:

$ scheduler_check_listed_origins
Forge repo.or.cz (gitweb) isn't registered in the scheduler database.
Cleaning up project directory and file based variables
00:01
ERROR: Job failed: exit code 1

Second job execution, the lister-gitweb found no origin (may be base_git_url parameter is needed):

$ scheduler_check_listed_origins
Forge repo.or.cz (gitweb) has 0 listed origin in the scheduler database.
Cleaning up project directory and file based variables
00:01
ERROR: Job failed: exit code 1

closed

mentioned in issue sysadm-environment#5156 (closed)