June 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2163) Build repoman for fedora 28

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jir... ] eyal edri commented on OVIRT-2163: ---------------------------------- People want to run Lago on their FC28, so its quite important we'll prioritize it. > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jir... ] eyal edri updated OVIRT-2163: ----------------------------- Priority: Highest (was: Medium) > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > Priority: Highest > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2163) Build repoman for fedora 28

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2163?page=com.atlassian.jir... ] eyal edri commented on OVIRT-2163: ---------------------------------- [~ena(a)redhat.com] is that something you can do? did you have time to go over repoman a bit? > Build repoman for fedora 28 > --------------------------- > > Key: OVIRT-2163 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2163 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: repoman > Reporter: Gal Ben Haim > Assignee: infra > > It's needed by lago-ovirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jir... ] eyal edri updated OVIRT-2176: ----------------------------- Epic Link: OVIRT-400 > oVirt CI should support fast moving platform releases > ----------------------------------------------------- > > Key: OVIRT-2176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri > Assignee: infra > > It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. > We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. > This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. > Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases

by eyal edri (oVirt JIRA)

eyal edri created OVIRT-2176: -------------------------------- Summary: oVirt CI should support fast moving platform releases Key: OVIRT-2176 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2176 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: eyal edri Assignee: infra It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right. We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster. This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it. Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2164) Migrate repoman to STDCI v2

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2164?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2164: -------------------------------- Epic Link: OVIRT-2175 > Migrate repoman to STDCI v2 > --------------------------- > > Key: OVIRT-2164 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2164 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: repoman > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: stdci-v2-migrate > > Repoman CI is still using STDCI V1 ATM. Since its an infa project it should move to STDCI V2 quickly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2164) Migrate repoman to STDCI v2

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2164?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2164: -------------------------------- Epic Link: OVIRT-2175 > Migrate repoman to STDCI v2 > --------------------------- > > Key: OVIRT-2164 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2164 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: repoman > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: stdci-v2-migrate > > Repoman CI is still using STDCI V1 ATM. Since its an infa project it should move to STDCI V2 quickly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2175) Move oVirt projects to STDCI V2

by Daniel Belenky (oVirt JIRA)

Daniel Belenky created OVIRT-2175: ------------------------------------- Summary: 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)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2174) Show dedicated message to early infra failures on STDCI build summary

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2174?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-2174: ---------------------------------- Epic Link: OVIRT-400 > Show dedicated message to early infra failures on STDCI build summary > --------------------------------------------------------------------- > > Key: OVIRT-2174 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2174 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to see a dedicated message on STDCI build summary in case STDCI failed before even running my code so I can quickly contact the infra team. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2174) Show dedicated message to early infra failures on STDCI build summary

by Daniel Belenky (oVirt JIRA)

Daniel Belenky created OVIRT-2174: ------------------------------------- Summary: Show dedicated message to early infra failures on STDCI build summary Key: OVIRT-2174 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2174 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra As an STDCI user I want to see a dedicated message on STDCI build summary in case STDCI failed before even running my code so I can quickly contact the infra team. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018