- Infra - oVirt List Archives

[JIRA] (OVIRT-2172) STDCI build summary to write message when no threads were found
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2172?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2172: -------------------------------- Epic Link: (was: OVIRT-400) > STDCI build summary to write message when no threads were found > --------------------------------------------------------------- > > Key: OVIRT-2172 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2172 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to see a dedicated message at STDCI build summary that warns me that no threads were executed for my build to prevent cases where I think something runs while it doesn't (currently it shows blank page - users can think it's a bug in the summary.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2172) STDCI build summary to write message when no threads were found
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2172?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2172: -------------------------------- Epic Link: (was: OVIRT-400) > STDCI build summary to write message when no threads were found > --------------------------------------------------------------- > > Key: OVIRT-2172 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2172 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to see a dedicated message at STDCI build summary that warns me that no threads were executed for my build to prevent cases where I think something runs while it doesn't (currently it shows blank page - users can think it's a bug in the summary.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2173) STDCI build summary to include details about the STDCI event
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2173?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2173: -------------------------------- Epic Link: (was: OVIRT-400) > STDCI build summary to include details about the STDCI event > ------------------------------------------------------------ > > Key: OVIRT-2173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to have quick view of the event details such as who is the change owner, what branch it was pushed to, and etc so I won't have to extract this information from the SCM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2173) STDCI build summary to include details about the STDCI event
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2173?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2173: -------------------------------- Epic Link: (was: OVIRT-400) > STDCI build summary to include details about the STDCI event > ------------------------------------------------------------ > > Key: OVIRT-2173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to have quick view of the event details such as who is the change owner, what branch it was pushed to, and etc so I won't have to extract this information from the SCM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2174) Show dedicated message to early infra failures on STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2174: -------------------------------- Epic Link: (was: 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)

1 0

[JIRA] (OVIRT-2174) Show dedicated message to early infra failures on STDCI build summary
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2174?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2174: -------------------------------- Epic Link: (was: 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)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2176: ------------------------------------- Putting this under OVIRT-2184 as it seems full gating of platform changes would solve this as well. > 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)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2176: -------------------------------- Epic Link: OVIRT-2184 > 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)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2176: -------------------------------- Epic Link: OVIRT-2184 > 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)

1 0

[JIRA] (OVIRT-2176) oVirt CI should support fast moving platform releases
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2176?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2176: -------------------------------- Epic Link: (was: 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)

1 0