[Add Forge Now] process https://git.harrault.fr
https://webapp.staging.swh.network/admin/add-forge/request/124/
Type: gitlab
Production request: https://archive.softwareheritage.org/admin/add-forge/request/264/
https://webapp.staging.swh.network/admin/add-forge/request/124/
Type: gitlab
Production request: https://archive.softwareheritage.org/admin/add-forge/request/264/
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/6184.
The lister image seems to not be present on node so pod creation took more time than the listing delay (300s):
ᐅ kbs describe pods $(kbs get po -n swh | awk '/gitlab/{print $1}') -n swh | awk '/Pulled.*lister/'
Normal Pulled 69s kubelet Successfully pulled image "container-registry.softwareheritage.org/swh/infra/swh-apps/lister:20231205.2" in 7m3.021140473s (7m3.021171109s including waiting)
I relaunch the job.
Request successfully processed in staging environment.
For the pipeline details, see:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/6184.
Request successfully processed in production environment.
For the pipeline details, see:
https://gitlab.softwareheritage.org/swh/infra/add-forge-now-requests/-/pipelines/6184.
changed the description