- Infra - oVirt List Archives

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches
by Barak Korren (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2201: ------------------------------------- [~sbonazzo(a)redhat.com] I'll need some help to write the user stories for the requirements you state so we can properly evaluate and triage them. {quote} a way to quickly see if jobs are failing on a specific branch {quote} How about: "As an oVirt developer, I want to see the build status for the HEAD commit of a particular branch of my project so that I can <need to fill in reason here>" {quote} a way to consume builds from a specific branch {quote} "As an oVirt developer I want to have a way to acquire the lasted CI build on a particular branch on a particular project so that I can use it as a dependency for other jobs". About this last one - I guess we can ask people in devel if "tested" would be a good enough compromise? > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuil… > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92278,1 (ovirt-appliance) failed "ovirt-master" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

Change 92278,1 (ovirt-appliance) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/92278/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8264/

2 1

[CQ]: 92278,1 (ovirt-appliance) failed "ovirt-master" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

Change 92278,1 (ovirt-appliance) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/92278/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8262/

2 1

[CQ]: 92323,2 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

Change 92323,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/92323/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2431/

1 0

[CQ]: 92245,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

Change 92245,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/92245/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8258/

2 1

[JIRA] (OVIRT-2213) Cleaning up ISO in tested repo and keeping latest version
by Ehud Yonasi (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2213?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2213: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > Cleaning up ISO in tested repo and keeping latest version > --------------------------------------------------------- > > Key: OVIRT-2213 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2213 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt Infra > Reporter: Ehud Yonasi > Assignee: Ehud Yonasi > > ISO images under tested repo got huge and require an automatic cleanup to free tested repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2213) Cleaning up ISO in tested repo and keeping latest version
by Ehud Yonasi (oVirt JIRA) 18 Jun '18

18 Jun '18

Ehud Yonasi created OVIRT-2213: ---------------------------------- Summary: Cleaning up ISO in tested repo and keeping latest version Key: OVIRT-2213 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2213 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt Infra Reporter: Ehud Yonasi Assignee: infra ISO images under tested repo got huge and require an automatic cleanup to free tested repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2213) Cleaning up ISO in tested repo and keeping latest version
by Ehud Yonasi (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2213?page=com.atlassian.jira.… ] Ehud Yonasi updated OVIRT-2213: ------------------------------- Epic Link: OVIRT-1744 > Cleaning up ISO in tested repo and keeping latest version > --------------------------------------------------------- > > Key: OVIRT-2213 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2213 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt Infra > Reporter: Ehud Yonasi > Assignee: infra > > ISO images under tested repo got huge and require an automatic cleanup to free tested repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92245,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 18 Jun '18

18 Jun '18

Change 92245,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/92245/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8255/

2 1

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 253 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '18

18 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 253 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #253 [Milan Zamazal] Make sure complete SS_PATH exists ----------------- Failed Tests: ----------------- All tests passed

1 2