[
https://ovirt-jira.atlassian.net/browse/OVIRT-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36936#comment-36936
]
Daniel Belenky commented on OVIRT-2160:
---------------------------------------
STDCI didn't run any build jobs because the PR was sent to branch *BZ1588465*
which is not mapped to any ovirt change queue.
STDCI only build projects that release one of the queues during
build-artifacts, otherwise, it's pointless to build.
If one needs a "manual" build, he can do so by asking STDCI to build via "ci
build please".
Regarding the poll-upstream-sources message - It's unrelated to this case.
It means what it says: STDCI couldn't find any poll-upstream-sources stage
(which is true - the stage is check-merged/build-artifacts).
In any case, currently, we don't support for GH poll jobs currently (at least
not automatically sending a PR).
> ovirt-ansible-disaster-recovery build jobs not triggered
> --------------------------------------------------------
>
> Key: OVIRT-2160
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2160
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Dafna Ron
> Assignee: infra
> Labels: ost_build-arifacts, ost_failures, ost_infra
>
> https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-disaster-recovery_standard-on-ghpush/196/artifact/
> shows no build job triggered. Can you please fix it?
> Thanks,
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/I4CJTWVEVO7K5HVCNCPQ5MEPB73FZ23D/
