June 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-983) Improve CI output for Jenkins repo

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-983?page=com.atlassian.jira... ] eyal edri commented on OVIRT-983: --------------------------------- [~bkorren(a)redhat.com] did we made progress on this during last year with V2 and BO? > Improve CI output for Jenkins repo > ---------------------------------- > > Key: OVIRT-983 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-983 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Since we've added more ci jobs to the {{jenkins}} repo, the CI output because unclear. When it was one job, it was easy to understand it failed because of YAML issues. Now, when it passes on all platforms but el7, its easy to mistake this for a infra failure on el7 rather then a real problem with the patch. > The following improvements should be made to the job output: > # The YAML failure message should be placed directly in the Gerrit comment, this can be done with the "Unsuccessful Message File" feature of the Gerrit plugin. > # When YAML check succeeds ther sohuld be a message in Gerrit saying so and indicating where the DIFF output can be seen (will "Unsuccessful Message File" also work on success?) > # The {{differences.html}} file should probably be called {{index.html}} to get it placed in the job status page. > # Maybe add some javascript to {{differences.html}} to allow collapsing individual differences. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

5 years, 11 months

1
0
0 / 0

[CQ]: d00d8ca (stage-gh-stdci2) failed "dummy-master" system tests

by oVirt Jenkins

Change d00d8ca (stage-gh-stdci2) is probably the reason behind recent system test failures in the "dummy-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://github.com/oVirt/stage-gh-stdci2/commit/d00d8cac105f7be15d2a05595... For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/141/

5 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-562) find a way not to fail CI jobs if git clone fails

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-562?page=com.atlassian.jira... ] eyal edri updated OVIRT-562: ---------------------------- Resolution: Won't Do Status: Done (was: To Do) > find a way not to fail CI jobs if git clone fails > ------------------------------------------------- > > Key: OVIRT-562 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-562 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri > Assignee: infra > Priority: Low > > We need to find away to tell gerrit trigger plugin not to put -1 if git clone fails (obviously an infra issue) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

5 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1113?page=com.atlassian.jir... ] eyal edri updated OVIRT-1113: ----------------------------- Priority: Low (was: Medium) > Automate project Gerrit repo creation > ------------------------------------- > > Key: OVIRT-1113 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: first_time_task > > Because the doc is annoying to follow manually, and its easy to automate Gerrit, the API is basically 'ssh'. > Long term if the automation is good we could make this "self service". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

5 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-895) mailing list memberships reminder - do we need that?

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-895?page=com.atlassian.jira... ] eyal edri updated OVIRT-895: ---------------------------- Resolution: Fixed Status: Done (was: To Do) Not sure this is an issue anymore, anyone can go to thier settings on the UI and update their preference. > mailing list memberships reminder - do we need that? > ---------------------------------------------------- > > Key: OVIRT-895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-895 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > I'm subscribed to a bunch of lists and every month I get membership reminder emails. Do we have them for a reason? If not - I'd like to disable them (can be done per-list in the settings or globally across the Mailman instance) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

5 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jir... ] eyal edri updated OVIRT-1385: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) [~vojtech] as [~bkorren(a)redhat.com] mock_runner is in stabilization mode and we're not planning any new features there, if this is something that is still needed, we can check if its possible to support via V2 of future work planned for the CI > Support installing latest version of specific pkgs > -------------------------------------------------- > > Key: OVIRT-1385 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1385 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Vojtech Szocs > Assignee: infra > Priority: Low > Labels: mock_runner.sh > > There are multiple oVirt projects (see below) which contain a {{build.packages.force}} (or similar) file, along with the following code in their build script: > {code} > # The "build.packages.force" file contains BuildRequires packages > # to be installed using their latest version. > # Force CI to get the latest version of these packages: > dependencies="$(sed -e '/^[ \t]*$/d' -e '/^#/d' automation/build.packages.force)" > yum-deprecated clean metadata || yum clean metadata > yum-deprecated -y install ${dependencies} || yum -y install ${dependencies} > {code} > Used in projects: ovirt-engine-dashboard, ovirt-engine-nodejs-modules, ovirt-web-ui > Is it possible for CI to support this out of the box, using {{.force}} file convention? (basically a suffix to standard {{.packages}} files) > I've looked at OVIRT-921 and IIUC the yum cache is cleaned every 2 days, so an alternative to above proposal would be to have this interval configurable per-project. > Not sure what's the best approach here, please advise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

5 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-1399) Install Jenkins TAP results plugin

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1399?page=com.atlassian.jir... ] eyal edri updated OVIRT-1399: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) > Install Jenkins TAP results plugin > ---------------------------------- > > Key: OVIRT-1399 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1399 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Nadav Goldin > Assignee: infra > Priority: Low > > Please install the TAP Plugin - https://wiki.jenkins-ci.org/display/JENKINS/TAP+Plugin > It allows to display TAP test results, which we use in Lago(with bats). > Not urgent, can be done whenever time allows(with some other upgrade etc). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

5 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jir... ] eyal edri updated OVIRT-1500: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > Priority: Low > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

5 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jir... ] eyal edri commented on OVIRT-1295: ---------------------------------- [~tnisan(a)redhat.com] is this still needed? I didn't see any issues during 4.2 development which required an additional flow other than existing change queue. If so, can you elaborate more on the need, maybe as a user story so we'll understand the problem at hand. > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri > Assignee: infra > Priority: Low > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

5 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-1971) oVirt Bugzilla automation: Bugs didn't move to ON_QA [Bug 1542087]

by eyal edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1971?page=com.atlassian.jir... ] eyal edri commented on OVIRT-1971: ---------------------------------- [~amarchuk] ping > oVirt Bugzilla automation: Bugs didn't move to ON_QA [Bug 1542087] > ------------------------------------------------------------------ > > Key: OVIRT-1971 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1971 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Anton Marchukov > Labels: bugzilla, > > Sending to infra-support to track this as a ticket. > On Fri, Apr 13, 2018 at 3:35 PM, Anton Marchukov <amarchuk(a)redhat.com> > wrote: > > Hello Greg. > > > > Thanks. > > > > Anton. > > > > > > On 13 April 2018 at 14:27:26, Greg Sheremeta (gshereme(a)redhat.com) wrote: > > > Thanks. I moved the rest (we had 3) > > > > > > On Fri, Apr 13, 2018 at 8:24 AM, Anton Marchukov > > > wrote: > > > > > > > Hello Greg. > > > > > > > > You are right and the patch is included in the tag. Sounds like there > > > > are some problems with detecting earlier changes. I moved to ON_QA > > > > manually while we check this. > > > > > > > > Anton. > > > > > > > > > > > > On 13 April 2018 at 14:16:30, Greg Sheremeta (gshereme(a)redhat.com) > > wrote: > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1542087 > > > > > > > > > > > > > > > > -- > > > > > > GREG SHEREMETA > > > > > > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > > > > > > Red Hat NA > > > > > > > > > > > > gshereme(a)redhat.com IRC: gshereme > > > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018