fedora-ci / general

#23 CI jobs won't run on PRs
Closed by churchyard. Opened by churchyard.

Closed
Reopen Issue

https://src.fedoraproject.org/rpms/pipenv/pull-request/8
https://src.fedoraproject.org/rpms/pipenv/pull-request/9
https://src.fedoraproject.org/rpms/pipenv/pull-request/10

no CI job started

Same problem with lorax - https://src.fedoraproject.org/rpms/lorax/pull-request/3

Talked to @adamwill about it for a sec, and his speculation is that the CI system is still using a whitelist. eg. https://github.com/CentOS-PaaS-SIG/ci-pipeline/blob/master/JenkinsfileTrigger#L111-L138

BTW This used to work for pipenv before.

Hmm, jobs are not even triggered huh ,,, https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/fedora-f29-pr-pipeline/activity

Investigating

Metadata Update from @mvadkert:
- Issue assigned to mvadkert

Metadata Update from @mvadkert:
- Issue priority set to: Critical (was: Medium)

It seems to be a Fedora infra issue: https://pagure.io/fedora-infrastructure/issue/7493

Metadata Update from @mvadkert:
- Issue unmarked as blocking: #21

Metadata Update from @churchyard:
- Issue status updated to: Closed (was: Open)

The CI runs.
Metadata
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.