- Infra - oVirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4340 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 21 Dec '16

21 Dec '16

------=_Part_46_1404524996.1482329430633 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4340/, Build Number: 4340, Build Status: FAILURE ------=_Part_46_1404524996.1482329430633--

1 3

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-967: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-967: ------------------------------------ Maybe assign the ticket to yourself if you're handling it.... > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-967: ------------------------------------ n/m saw it, so you're doing everything from YAML, so this is the kind of implementation I would call specific, a generic implementation would specify soemthing to put in the automation dir so nobody needs to know YAML... > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-967: ------------------------------------ which patch? I'm not seeing any patch linked here... > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-967: ------------------------------------------------- Not sure I understand, the current patch is as generic as it gets without any relation to getbadgets or gamification, If its merged nothing will happen on CI (already verified) because the URL for the webhook is empty by default. Only if you provide a URL as param from a project then its activated, for e.g for jenkins project: https://gerrit.ovirt.org/#/c/68903/1/jobs/confs/projects/jenkins/jenkins_st… The alternative is to create a new template for it and change multiple projects to use it if we want, which I don't see a reason for, if by default the plugin is not active. > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-955) Re: http://lists.ovirt.org/pipermail/announce/ is not reachable
by Marc Dequènes (Duck) (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-955?page=com.atlassian.jira.p… ] Marc Dequènes (Duck) commented on OVIRT-955: -------------------------------------------- yes, a few days ago. the progress was on the migration ticket. > Re: http://lists.ovirt.org/pipermail/announce/ is not reachable > --------------------------------------------------------------- > > Key: OVIRT-955 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-955 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Tested it, I've access forbidden there: > http://lists.phx.ovirt.org/pipermail/announce/ > archives should be publicly accessible. > On Mon, Dec 12, 2016 at 2:21 PM, Evgheni Dereveanchin <ederevea(a)redhat.com> > wrote: > > I totally agree with Barak on this. The hostname > > must work as there's a bunch of links indexed > > by search engine which lead to it. > > In general the PHX one should not be used > > by end users. I've re-added the CNAME and edited > > the virtualhost on apache so it should be available > > again once existing DNS caches expire. > > > > Regards, > > Evgheni Dereveanchin > > > > ----- Original Message ----- > > From: "Barak Korren" <bkorren(a)redhat.com> > > To: "Eyal Edri" <eedri(a)redhat.com> > > Cc: "infra" <infra(a)ovirt.org>, "Sandro Bonazzola" <sbonazzo(a)redhat.com>, > > "Evgheni Dereveanchin" <ederevea(a)redhat.com>, "duck" <duck(a)redhat.com>, > > infra-owner(a)ovirt.org > > Sent: Monday, 12 December, 2016 2:05:57 PM > > Subject: Re: http://lists.ovirt.org/pipermail/announce/ is not reachable > > > > It can be reached now at lists.phx.ovirt.org (but we we need a CNAME > > from the old name) > > > > On 12 December 2016 at 15:03, Eyal Edri <eedri(a)redhat.com> wrote: > > > I'm not sure who gets emails sent to infra-owner list. best to send it > > to > > > infra or infra support. > > > > > > Adding Evgheni and Duck who are working on migration of the mm server. > > > > > > On Dec 12, 2016 2:58 PM, "Sandro Bonazzola" <sbonazzo(a)redhat.com> wrote: > > >> > > >> The lists server is not reachable anymore. Looks like a dns issue: > > >> > > >> $ traceroute lists.ovirt.org > > >> lists.ovirt.org: Name or service not known > > >> > > >> > > >> -- > > >> Sandro Bonazzola > > >> Better technology. Faster innovation. Powered by community > > collaboration. > > >> See how it works at redhat.com > > > > > > > > > _______________________________________________ > > > Infra mailing list > > > Infra(a)ovirt.org > > > http://lists.phx.ovirt.org/mailman/listinfo/infra > > > > > > > > > > > -- > > Barak Korren > > bkorren(a)redhat.com > > RHCE, RHCi, RHV-DevOps Team > > https://ifireball.wordpress.com/ > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by Barak Korren (oVirt JIRA) 21 Dec '16

21 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-967: ------------------------------------ The big question is if we want to have it generic, which will require extensions to the CI standard, and some thinking and perhaps some non-trivial Jenkins tricks, or, we just want to quickly support GetBadges. > add support for notification plugin in standard CI > -------------------------------------------------- > > Key: OVIRT-967 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4338 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 21 Dec '16

21 Dec '16

------=_Part_38_542710353.1482325391232 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4338/, Build Number: 4338, Build Status: FAILURE ------=_Part_38_542710353.1482325391232--

1 1

Gerrit hooks doesn't mark open patches in other branches as -verified
by Tal Nisan 21 Dec '16

21 Dec '16

Check out this patches for instance: https://gerrit.ovirt.org/#/c/68862 https://gerrit.ovirt.org/#/c/68861 Those are 4.1 and 4.0 patches that are open on master, I'd expect to see them get -verified from the hooks which they didn't: - Update Tracker::#1406042::OK, status: POST - Check Bug-Url::OK - Check Product::#1406042::OK, product: ovirt-engine - Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor target milestone: ovirt-4.0.7 - Set POST::#1406042::IGNORE, bug is already in 'POST' status - Check Backport::IGNORE, The patch backported to all newer branches.(open in 'master' branch/es) found not relevant branch/es: 'ovirt-engine-4.0' (not exist in the newer branches list) This was the flow before and it made my life easier as I didn't have to actively search for cherry-picks in all other branches to see if it can be merged

3 7