June 2018 - Infra - oVirt List Archives

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

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2201: --------------------------------- It covers ~90% of what we had in v1, it still miss: - a way to quickly see if jobs are failing on a specific branch - a way to consume builds from a specific branch (some jobs take latestSuccessfulBuild from Jenkins for building and this causes random branch selection based on last build). About this, maybe jobs should be changed for not consuming builders directly, but needs to track down them. > [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

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 110 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '18

18 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/110/ Build Number: 110 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #110 [Milan Zamazal] Make sure complete SS_PATH exists ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2066) Re: Users list mail issue
by Marc Dequènes (Duck) (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2066?page=com.atlassian.jira.… ] Marc Dequènes (Duck) updated OVIRT-2066: ---------------------------------------- Resolution: Fixed Status: Done (was: To Do) Whoua, it's old. Also there was some latency due to greylisting, both on the new server and world's servers because the IP changed. Four hours seem a bit long though. I had no such complaints recently and all seem to work fine, so let's close. > Re: Users list mail issue > ------------------------- > > Key: OVIRT-2066 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2066 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Marc Dequènes (Duck) > > Opening a ticket > On Wed, May 30, 2018, 18:39 Fred Rolland <frolland(a)redhat.com> wrote: > > Hi, > > > > It seems that I am receiving some emails from users list after a long > > delay. > > > > For example this thread: > > > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/5N6N4BHF6ZFJLE… > > > > I have received only 2 emails from this thread, and my colleagues did not > > receive the one I sent 4 hours ago. > > > > > > Any idea what is the problem? > > > > Thanks, > > Freddy > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > 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/infra@ovirt.org/message/6EKS6OYUQK7BK… > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

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

17 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/522/ Build Number: 522 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #522 [Milan Zamazal] Make sure complete SS_PATH exists [Barak Korren] Change V1 jobs for the 'jenkins' to not use fc26 [Sandro Bonazzola] ovirt-engine: drop scan_security_and_license job ----------------- Failed Tests: ----------------- All tests passed

1 1

[JIRA] (OVIRT-2204) A user request
by Galit Rosenthal (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2204?page=com.atlassian.jira.… ] Galit Rosenthal commented on OVIRT-2204: ---------------------------------------- I have access to the ovirt, I can see the projects/issues for exampe On Sun, Jun 17, 2018 at 11:36 AM, eyal edri (oVirt JIRA) < > A user request > -------------- > > Key: OVIRT-2204 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2204 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Galit Rosenthal > Assignee: infra > > Hi, > I will need a user to *Ovirt Jira system* > *Thanks* > *Galit* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

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

17 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: 249 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #249 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- All tests passed

1 2

[JIRA] (OVIRT-2205) Permissions to Jenkins
by Emil Natan (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2205?page=com.atlassian.jira.… ] Emil Natan reassigned OVIRT-2205: --------------------------------- Assignee: Emil Natan (was: infra) > Permissions to Jenkins > ---------------------- > > Key: OVIRT-2205 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2205 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Galit Rosenthal > Assignee: Emil Natan > > Hi, > I need to have permissions to Jenkins > user: grosenth > Thanks > Galit -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2207) Collect findbugs results in pipeline jobs
by Daniel Belenky (oVirt JIRA) 17 Jun '18

17 Jun '18

Daniel Belenky created OVIRT-2207: ------------------------------------- Summary: Collect findbugs results in pipeline jobs Key: OVIRT-2207 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2207 Project: oVirt - virtualization made easy Issue Type: Bug Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra As an STDCI user, I want to be able to view "findbugs" results in a convenient way such as the Jenkins "findbugs" plugin provides so that I can analyze the results. Currently, this feature is supported in STDCI V1 jobs only and we need to have the same support in STDCI V2 jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2207) Collect findbugs results in pipeline jobs
by Daniel Belenky (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2207?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2207: ---------------------------------- Epic Link: OVIRT-400 > Collect findbugs results in pipeline jobs > ----------------------------------------- > > Key: OVIRT-2207 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2207 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user, I want to be able to view "findbugs" results in a convenient way such as the Jenkins "findbugs" plugin provides so that I can analyze the results. > Currently, this feature is supported in STDCI V1 jobs only and we need to have the same support in STDCI V2 jobs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2204) A user request
by eyal edri (oVirt JIRA) 17 Jun '18

17 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2204?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2204: ----------------------------- Resolution: Fixed Status: Done (was: To Do) you should have an active user, let me know if you can't login. > A user request > -------------- > > Key: OVIRT-2204 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2204 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Galit Rosenthal > Assignee: infra > > Hi, > I will need a user to *Ovirt Jira system* > *Thanks* > *Galit* -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0