I've run my fedora-gather-easyfix test script this morning, it makes a new build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1318895 but something's up in https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-f30-build-pipeline/685/
Any clues what's going on ?
Note: it did do the build part: https://jenkins-continuous-infra.apps.ci.centos.org/job/fedora-build-pipeline-trigger/328091/
https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-f30-build-pipeline/685/console
The job is running, but it looks like there could be slow network on jenkins-continuous-infra.apps.ci.centos.org.
11:01:33 > git fetch --no-tags --progress https://github.com/CentOS-PaaS-SIG/upstream-fedora-pipeline +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* 11:05:11 Checking out Revision f204b02517c1de1f316b3ac4180540c4c98bbfb0 (master) 11:05:11 > git config core.sparsecheckout # timeout=10 11:05:55 ‘Jenkins’ doesn’t have label ‘fedora-cloud-09c468b6-f838-4934-a086-407bc538f2b7-allpkgs’ 11:10:13 Agent fedora-cloud-09c468b6-f838-4934-a086-407bc538f2b7-allpkgs-4vxc1 is provisioned from template Kubernetes Pod Template 11:10:13 Agent specification [Kubernetes Pod Template] (fedora-cloud-09c468b6-f838-4934-a086-407bc538f2b7-allpkgs):
@bstinson @siddharthvipul1 any idea what could be?
The trigger jobs should take just few seconds, but in some cases it took long time, like in this case https://jenkins-continuous-infra.apps.ci.centos.org/view/Fedora%20All%20Packages%20Pipeline/job/fedora-build-pipeline-trigger/328090/ it was 12mins.
I've opened a ticket to infrastructure: https://pagure.io/fedora-infrastructure/issue/8020
This is being tracked as an infra issue so I think it can be closed here :)
Metadata Update from @pingou: - Issue status updated to: Closed (was: Open)