[
https://ovirt-jira.atlassian.net/browse/OVIRT-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37172#comment-37172
]
eyal edri commented on OVIRT-2175:
----------------------------------
I agree, let's start tracking which projects are on V1 and schedule dates for
moving at least 2 projects a week.
If a project maintainer can't / won't move, we need to document the reason and
possibly open JIRA tickets to research the gap or document the missing feature.
I suggest starting opening tickets to each project we plan to move and document
progress there, start reaching out to the project maintainers.
This might also help speed up adding downstream jobs.
> Move oVirt projects to STDCI V2
> -------------------------------
>
> Key: OVIRT-2175
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2175
> Project: oVirt - virtualization made easy
> Issue Type: Epic
> Components: oVirt CI
> Reporter: Daniel Belenky
> Assignee: infra
>
> As STDCI V2 is live and production for a while now, it's time to proactively
> push and assist oVirt projects to move to STDCI V2. Projects will benefit
> from new STDCI V2 features such as the ability to modify the distributions
> and architectures they build on without having to send patches to the
> 'Jenkins' repo.
--
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/FROAFJVSJBXVEHLSEB6HRTP4BEWFHEJ5/
