[
https://ovirt-jira.atlassian.net/browse/OVIRT-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27893#comment-27893
]
eyal edri [Administrator] commented on OVIRT-1073:
--------------------------------------------------
We won't drop the nightly publishers.
Instead we'll just stop publishing RPMs from it and it will only be used to
sync tested RPMs each night to the snapshot repos, that way we'll have static
nightly updated oVirt repos.
The code to support it for master is already merged and part of the master
publisher.
We need to remove all the YAML code from the publisher job gradually until all
is left is the code that sync the test repo.
fyi [~sbonazo...@redhat.com]
> Drop nightly publishers in oVirt CI
> -----------------------------------
>
> Key: OVIRT-1073
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1073
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: eyal edri [Administrator]
> Assignee: infra
>
> We saw how destructive using the current publishers can be during 4.1 cycle,
> Problems we encountered:
> 1. It hides missing RPMs from experimental flows
> 2. It hides projects that needs to branch or using previous version released
> 3. It creates confusion of which RPMs are really tested in OST and give
> different results than experimental instead of having a single source of RPMs
> for oVirt.
> We should aim to drop it for 4.2 and use only experimental deployment.
> However, since we have errors on deploy to experimental flow, we can't
> progress with this until they will be solved.
--
This message was sent by Atlassian JIRA
(v1000.784.2#100032)
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
