[JIRA] (OVIRT-3110) OST failure, bad comment

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=41048#comment-41048
 ] 

Michal Skrivanek commented on OVIRT-3110:
-

> On 10. 7. 2021, at 0:14, Nir Soffer  wrote:
> 
> On Sat, Jul 10, 2021 at 12:59 AM Nir Soffer  wrote:
>> 
>> OST failed, and posted unprocessed comment:
>> 
>>OST Verified -1
>>Patch Set 1: Verified-1
>>https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 :
>> OST https://redir.apps.ovirt.org/dj/job/ds-ost-baremetal_manual/$OST_NUMBER
>>failed with: $OST_MESSAGE
>> 
>> https://gerrit.ovirt.org/c/vdsm/+/115642#message-b2993761_adbc1b6a
>> 
>> Looking at:
>> https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313
>> 
>> It looks like environment issue:
>> 
>> ERROR: Build step failed with exception
>> 
>> java.lang.NullPointerException: no workspace from node
>> hudson.slaves.DumbSlave[hpe-bl280g6-12...] which is computer
>> hudson.slaves.SlaveComputer@2e2cb321 and has channel null
>> 
>> So we have 2 issues:
>> 1. If build fails, error is not handled properly producing bad comment
>> 2. the actual build failure
> 
> I started another build manually (8543) and it started normally, so this was
> probably a temporary issue.

Seems someone rebooted the jenkins host in the middle of the run

> 
>> 
>> The first issue should be handled by posting a better comment:
>> 
>>OST build error:
>> https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313
>> 
>> And OST should not mark the patch as verified -1, since it did not run any 
>> test.

It’s a shell script that runs after the job that fails on missing workspace, it 
would be possible to set unstable status on a failure of that script, but It 
doesn’t seem to be possible to handle internal jenkins exception

>> 
>> Marking a patch as -1 means some tests have failed,  and the author
>> needs to check
>> why. A build error means OST or CI maintainers need to check why the
>> error happened.
> ___
> Devel mailing list -- de...@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/de...@ovirt.org/message/H4Q2MT7R7DXKWHRZK7RGPSOLRYZMVZOP/

> OST failure, bad comment
> 
>
> Key: OVIRT-3110
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3110
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> OST failed, and posted unprocessed comment:
> OST Verified -1
> Patch Set 1: Verified-1
> https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313 :
> OST https://redir.apps.ovirt.org/dj/job/ds-ost-baremetal_manual/$OST_NUMBER
> failed with: $OST_MESSAGE
> https://gerrit.ovirt.org/c/vdsm/+/115642#message-b2993761_adbc1b6a
> Looking at:
> https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313
> It looks like environment issue:
> ERROR: Build step failed with exception
> java.lang.NullPointerException: no workspace from node
> hudson.slaves.DumbSlave[hpe-bl280g6-12...] which is computer
> hudson.slaves.SlaveComputer@2e2cb321 and has channel null
> So we have 2 issues:
> 1. If build fails, error is not handled properly producing bad comment
> 2. the actual build failure
> The first issue should be handled by posting a better comment:
> OST build error:
> https://redir.apps.ovirt.org/dj/job/ds-ost-gating-trigger2/313
> And OST should not mark the patch as verified -1, since it did not run any 
> test.
> Marking a patch as -1 means some tests have failed,  and the author
> needs to check
> why. A build error means OST or CI maintainers need to check why the
> error happened.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100168)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/IV2I2UGBTESUYZXUKLZT5XFLQIHKE533/

[JIRA] (OVIRT-3026) making test-ovirt-master.phx.ovirt.org larger

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-3026:
---

 Summary: making test-ovirt-master.phx.ovirt.org larger
 Key: OVIRT-3026
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3026
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Michal Skrivanek
Assignee: infra


Hi,
we have one public ovirt instance created few months ago.
Can you increase the resources for this VM? We’d like to repurpose it for OCP 
CI engine. 
16GB memory and 4 CPUs should suffice - that would be twice as large as today

Thanks,
michal



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100147)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ULDL3MB4BD4RNGG6QVXPNBFHIKURGO73/

[JIRA] (OVIRT-2885) need externally accessible VM temporarily

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=40225#comment-40225
 ] 

Michal Skrivanek commented on OVIRT-2885:
-

yeah, just enough time for the localization team QA.



We do need a mster engine on el8. Both are fine, HE or regular deployment of 
engine in a VM, whatever’s easier.

Host and credentials is good enough. Then maybe just centos8 VM is easy enough. 
No need for extra resources, 2 vCPUs, 8GB should be a minimum

> need externally accessible VM temporarily
> -
>
> Key: OVIRT-2885
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2885
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Michal Skrivanek
>Assignee: infra
>
> Hi,
> we need to provide externally accessible VM(with oVirt Hosted Engine env) for 
> localization team QA. Could you please get me a VM with ssh access and port 
> 443 opened? 2 CPUs, 8GB RAM would suffice. 
> Sooner the better:)
> Thanks,
> michal



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100122)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TGXTFDMVKZNWJJ6NKYISBJJE36FUJI45/

[JIRA] (OVIRT-2885) need externally accessible VM temporarily

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=40209#comment-40209
 ] 

Michal Skrivanek commented on OVIRT-2885:
-

any update?

> On 20 Mar 2020, at 17:36, Michal Skrivanek  
> wrote:
> 
> Hi,
> we need to provide externally accessible VM(with oVirt Hosted Engine env) for 
> localization team QA. Could you please get me a VM with ssh access and port 
> 443 opened? 2 CPUs, 8GB RAM would suffice. 
> Sooner the better:)
> 
> Thanks,
> michal

> need externally accessible VM temporarily
> -
>
> Key: OVIRT-2885
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2885
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Michal Skrivanek
>Assignee: infra
>
> Hi,
> we need to provide externally accessible VM(with oVirt Hosted Engine env) for 
> localization team QA. Could you please get me a VM with ssh access and port 
> 443 opened? 2 CPUs, 8GB RAM would suffice. 
> Sooner the better:)
> Thanks,
> michal



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100122)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JTCOAFUXMBVETBJL4RUL3L756FAA5653/

[JIRA] (OVIRT-2885) need externally accessible VM temporarily

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2885:
---

 Summary: need externally accessible VM temporarily
 Key: OVIRT-2885
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2885
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Michal Skrivanek
Assignee: infra


Hi,
we need to provide externally accessible VM(with oVirt Hosted Engine env) for 
localization team QA. Could you please get me a VM with ssh access and port 443 
opened? 2 CPUs, 8GB RAM would suffice. 
Sooner the better:)

Thanks,
michal



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100122)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/2N3FFBCWGPQXW6J3QATZVBAULZGH67D2/

[JIRA] (OVIRT-2871) add Sharon Gratch to ovirt-engine frontend maintainers

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2871:
---

 Summary: add Sharon Gratch to ovirt-engine frontend maintainers
 Key: OVIRT-2871
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2871
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra


following the votes in 
https://lists.ovirt.org/archives/list/de...@ovirt.org/thread/4UVBQC6F4MSO33TSOB3WYM6UQCENJ3CY/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100121)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ADHZGQ2Q4UQPRO4ZYT4EN544FUEP5RJN/

[JIRA] (OVIRT-2842) add Lucia Jelinkova to ovirt-engine frontend maintainers

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2842:
---

 Summary: add Lucia Jelinkova to ovirt-engine frontend maintainers
 Key: OVIRT-2842
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2842
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra


following the votes in 
https://lists.ovirt.org/archives/list/de...@ovirt.org/thread/6IKNDWBPSZRKZ34POJEVVGAO2ZWVS5OI/
 please add Lucia to the list of maintainers

Thanks!
michal



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100114)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/SFPDMMXOZIZKR6DIIMHUZKHA6UICSKIM/

[JIRA] (OVIRT-2834) please install zanata in our ovirt infra

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2834:
---

 Summary: please install zanata in our ovirt infra
 Key: OVIRT-2834
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2834
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra


for now decided to use our own instance, we'll move current translations to it 
once it's ready



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100114)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/AQWJ6RWTZE3ZXWZYBP2UKV7YIH4L6UHG/

[JIRA] (OVIRT-2833) Please add msobczyk to vdsm maintainers

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2833:
---

 Summary: Please add msobczyk to vdsm maintainers
 Key: OVIRT-2833
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2833
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra


per de...@ovirt.org



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100114)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/LTBYKSKG4T4PDIPTEBRWMTLCZ6W5ATDO/

[JIRA] (OVIRT-2812) move Douglas' rhvanalyzer repo under oVirt

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2812:
---

 Summary: move Douglas' rhvanalyzer repo under oVirt
 Key: OVIRT-2812
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2812
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra






--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100111)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/LH7R2HKLD633H4P5TOOAW3AMMMQ3B4GD/

[JIRA] (OVIRT-2795) Re: [ovirt-devel] ovirt-vmconsole package issues

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39818#comment-39818
 ] 

Michal Skrivanek commented on OVIRT-2795:
-

hm….we don’t properly handle master builds vs version build in this package. we 
don’t build it too often so it was ignored until now. I had to rebuild the same 
content to match d/s where we bumped up version without really following the 
upstream version:(

> Re: [ovirt-devel] ovirt-vmconsole package issues
> 
>
> Key: OVIRT-2795
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2795
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Nir Soffer
>Assignee: Evgheni Dereveanchin
>
> On Wed, Sep 11, 2019 at 4:38 PM Michal Skrivanek <
> michal.skriva...@redhat.com> wrote:
> >
> >
> > On 11 Sep 2019, at 11:19, Marcin Sobczyk  wrote:
> >
> > Hi,
> >
> > we get a lot of failures in the CI for el7 and fc29 regarding this package
> > since this morning, i.e. for fc29:
> >
> >
> > in which CI?
> >
> Here are some examples:
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/11308/pipeline
> https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-patch/detail/vdsm_standard-check-patch/11307/pipeline/123
> Adding infra-support to file a bug.
> >
> >
> >  
> > [2019-09-11T07:55:42.107Z]
> >  [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header 
> > callback: Server reports Content-Length: 38712 but expected size is: 38804
> >  
> > [2019-09-11T07:55:42.107Z]
> >  [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header 
> > callback: Server reports Content-Length: 38712 but expected size is: 38804
> >  
> > [2019-09-11T07:55:42.107Z]
> >  [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header 
> > callback: Server reports Content-Length: 38712 but expected size is: 38804
> >  
> > [2019-09-11T07:55:42.107Z]
> >  [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header 
> > callback: Server reports Content-Length: 38712 but expected size is: 38804
> >  
> > [2019-09-11T07:55:42.107Z]
> >  [FAILED] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: No more mirrors to try - 
> > All mirrors were already tried without success
> >  
> > [2019-09-11T07:55:42.107Z]
> >  Error: Error downloading packages:
> >  
> > [2019-09-11T07:55:42.107Z]
> >Cannot download noarch/ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: All 
> > mirrors were tried
> >
> > Can someone take a look at this?
> >
> > as it looks like incomplete package or webserver issue it’s best to report
> > this to infra
> >
> > Thanks, Marcin
> >
> >
> > ___
> > Infra mailing list -- infra@ovirt.org
> > To unsubscribe send an email to infra-le...@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/GE3G2RZ3TPXHV6YFPE7HVQ5GFSCGVTHU/
> >



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100109)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/Q2K6OFDN3MHVLKZKJUMDR3TRQBZQCTEY/

[JIRA] (OVIRT-2784) please update maintainers for ovirt-engine-nodejs-modules

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2784:
---

 Summary: please update maintainers for ovirt-engine-nodejs-modules
 Key: OVIRT-2784
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2784
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra


as per 
https://lists.ovirt.org/archives/list/de...@ovirt.org/thread/S3ULX7EQZ7YHRM6TWUUY26VOHNQZE43I/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100108)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/XWFPHXK6ZMKJ2PYZOTGC4OPXRXO2LSPE/

[JIRA] (OVIRT-2751) add Andrej Krejcir to ovirt-engine maintainers

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2751:
---

 Summary: add Andrej Krejcir to ovirt-engine maintainers
 Key: OVIRT-2751
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2751
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra


As approved by
https://lists.ovirt.org/archives/list/de...@ovirt.org/thread/5BHTBPVVAKVKQBZBXZA2QX3PITEVXXRW/
please grant +2 rights to Andrej



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100105)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/I6XWNASENSIX7DPEKUBWSAWWLM2KB65R/

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39239#comment-39239
 ] 

Michal Skrivanek commented on OVIRT-2714:
-

I see. So how many we have? One? Can it be shared with other hosts?
And even if we have just one right now - why is it not available? It's 
happening relatively frequently (roughly once in two weeks from what I've seen)

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
> ---
>
> Key: OVIRT-2714
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Michal Skrivanek
>Assignee: infra
>
> This one is about manual OST runs
> cloned from OVIRT-2704
> ---
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/WWVYAEIH7TGLZ5VHUOSKI7JNNCPHXWO6/

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39235#comment-39235
 ] 

Michal Skrivanek edited comment on OVIRT-2714 at 4/10/19 10:04 AM:
---

the intent of the original ticket to solve manual OST, but it only solves 
building artifacts. e still need more concurrent (or at least 1!!!) worker for 
the actual OST run


was (Author: mskrivanek):
actually, now that i read the description again. it was the intent of the 
original ticket to solve manual OST...so the original ticket is the right one

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
> ---
>
> Key: OVIRT-2714
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Michal Skrivanek
>Assignee: infra
>
> This one is about manual OST runs
> cloned from OVIRT-2704
> ---
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/RZTDRLKV7Z5AYRVZJ4JRNV2NV4FW73DG/

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs

[Michal Skrivanek (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michal Skrivanek updated OVIRT-2714:

Status: To Do  (was: In Progress)

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
> ---
>
> Key: OVIRT-2714
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Michal Skrivanek
>Assignee: infra
>
> This one is about manual OST runs
> cloned from OVIRT-2704
> ---
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/AZCPC4C3DPKOQ7QQTOJOM4NOCDNPDNJM/

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs

[Michal Skrivanek (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michal Skrivanek reopened OVIRT-2714:
-

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
> ---
>
> Key: OVIRT-2714
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Michal Skrivanek
>Assignee: infra
>
> This one is about manual OST runs
> cloned from OVIRT-2704
> ---
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/KHURQNNWCKDQPMFJQN754IZKSCAAV5PN/

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs

[Michal Skrivanek (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michal Skrivanek updated OVIRT-2714:

Resolution: Duplicate
Status: Done  (was: To Do)

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
> ---
>
> Key: OVIRT-2714
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Michal Skrivanek
>Assignee: infra
>
> This one is about manual OST runs
> cloned from OVIRT-2704
> ---
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/ZHIC35OHM6H3K5UQW6K4JJ2SX7L44ZND/

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39235#comment-39235
 ] 

Michal Skrivanek commented on OVIRT-2714:
-

actually, now that i read the description again. it was the intent of the 
original ticket to solve manual OST...so the original ticket is the right one

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
> ---
>
> Key: OVIRT-2714
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Michal Skrivanek
>Assignee: infra
>
> This one is about manual OST runs
> cloned from OVIRT-2704
> ---
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/I6MF3HZUUEV6IQZLRAQS4M7MLMJ2EOLX/

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs

[Michal Skrivanek (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michal Skrivanek updated OVIRT-2714:

Description: 
This one is about manual OST runs

cloned from OVIRT-2704
---
We started to use this job to build artifacts for running OST.

Looks like this job is limited to one concurrent job, which make it less
useful than
it could be.

If we don't make it easy to run OST, people will not run it, and the change
queue
will break.

Please change the limit to use the same limit used for regular builds. We
seem to be
able to create more then 10 concurrent builds by uploading patches to
gerrit. The manual
runner should this as well.

Nir

  was:
We started to use this job to build artifacts for running OST.

Looks like this job is limited to one concurrent job, which make it less
useful than
it could be.

If we don't make it easy to run OST, people will not run it, and the change
queue
will break.

Please change the limit to use the same limit used for regular builds. We
seem to be
able to create more then 10 concurrent builds by uploading patches to
gerrit. The manual
runner should this as well.

Nir


> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
> ---
>
> Key: OVIRT-2714
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Michal Skrivanek
>Assignee: infra
>
> This one is about manual OST runs
> cloned from OVIRT-2704
> ---
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/YVSCMG4TACN46POLROMWFC3H3V6IZMPZ/

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs

[Michal Skrivanek (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michal Skrivanek updated OVIRT-2714:

Summary: Increase limits on concurrent 
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs  (was: CLONE - 
Increase limits on concurrent 
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs)

> Increase limits on concurrent 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
> ---
>
> Key: OVIRT-2714
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Michal Skrivanek
>Assignee: infra
>
> We started to use this job to build artifacts for running OST.
> Looks like this job is limited to one concurrent job, which make it less
> useful than
> it could be.
> If we don't make it easy to run OST, people will not run it, and the change
> queue
> will break.
> Please change the limit to use the same limit used for regular builds. We
> seem to be
> able to create more then 10 concurrent builds by uploading patches to
> gerrit. The manual
> runner should this as well.
> Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/JELRMFACHVTB6RTUNZJFCL3ZBZ73L2KA/

[JIRA] (OVIRT-2714) CLONE - Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2714:
---

 Summary: CLONE - Increase limits on concurrent 
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
 Key: OVIRT-2714
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra


We started to use this job to build artifacts for running OST.

Looks like this job is limited to one concurrent job, which make it less
useful than
it could be.

If we don't make it easy to run OST, people will not run it, and the change
queue
will break.

Please change the limit to use the same limit used for regular builds. We
seem to be
able to create more then 10 concurrent builds by uploading patches to
gerrit. The manual
runner should this as well.

Nir



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100099)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/YF4CWIJQTWP6R2PGSWOGBQ44CWGNDZEQ/

[JIRA] (OVIRT-2576) please add smelamud as ovirt-engine maintainer

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2576:
---

 Summary: please add smelamud as ovirt-engine maintainer
 Key: OVIRT-2576
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2576
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra


Based on
https://lists.ovirt.org/archives/list/de...@ovirt.org/thread/TBYGMRTCF3BUMZ4ZC46DI6BQONNUMWOV/

Thanks,
michal



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/QQKOETVNYB4EOHECPMFILYORRLTAWPZ2/

[JIRA] (OVIRT-2575) list of cpu

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2575:
---

 Summary: list of cpu 
 Key: OVIRT-2575
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2575
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra
Priority: High


Do you have an inventory of all the slaves and can you please get "virsh -r  
capabilities|grep model|head -1" for all of them?"
it's important for the upcoming 4.3 supported cpus change



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/746CAF6ZZD7QGSGBS3Q7Z6WVQS4DOQI4/

[JIRA] (OVIRT-2510) Please add Mikhailo to CI whitelist

[Michal Skrivanek (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michal Skrivanek updated OVIRT-2510:

Description: 
Hi,

please add Mykhailo Kozlovskyy  to following projects CI 
whitelist:

ovirt-engine

Thanks,
Michal

  was:
Hi,

please add Avital Pinnick (apinnick) to following projects CI whitelist:

ovirt-engine-api-model

Avital is part of documentation team working on api-model.

[~apinn...@redhat.com]

Thanks,
Ondra

Summary: Please add Mikhailo to CI whitelist  (was: CLONE - Please add 
Mikhailo to CI whitelist)

> Please add Mikhailo to CI whitelist
> ---
>
> Key: OVIRT-2510
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2510
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Michal Skrivanek
>Assignee: infra
>
> Hi,
> please add Mykhailo Kozlovskyy  to following projects CI 
> whitelist:
> ovirt-engine
> Thanks,
> Michal



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/QQ27BGHOUEICDH6MWRIXTOVECGDUYACV/

[JIRA] (OVIRT-2510) CLONE - Please add Mikhailo to CI whitelist

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-2510:
---

 Summary: CLONE - Please add Mikhailo to CI whitelist
 Key: OVIRT-2510
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2510
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra


Hi,

please add Avital Pinnick (apinnick) to following projects CI whitelist:

ovirt-engine-api-model

Avital is part of documentation team working on api-model.

[~apinn...@redhat.com]

Thanks,
Ondra



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100092)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/EYDWG5FEJ35RCKGWCFMYUHAD624MUP4Y/

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=31417#comment-31417
 ] 

Michal Skrivanek commented on OVIRT-1408:
-

ah, ok, thanks for clarification.

[~eedri] to answer - well, the project decided to go through a more simple way 
than what's currently implemented for most other ovirt projects, being quite 
different in technology and scope. It works well and I do not see a need for 
more complex verification any time soon.(It doesn't mean it cannot be consumed 
by OST like anything else, I just currently do not see any way how would it be 
useful)
The automation dir is getting in a way just in the sense of the broken jobs. 
So..it saves some common oVirt infrastructure resources.

> Please remove github/ovirt-web-ui from standard CI
> --
>
> Key: OVIRT-1408
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Marek Libra
>Assignee: infra
>
> Please remove github/ovirt-web-ui from standard CI since Travis is used 
> instead.



--
This message was sent by Atlassian JIRA
(v1000.1010.0#100044)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=31412#comment-31412
 ] 

Michal Skrivanek commented on OVIRT-1408:
-

[~mli...@redhat.com], I wonder what is being requested from infra? Why you 
can't simply remove the automation/ directory in the project when it's not 
needed? Does it break anything?

> Please remove github/ovirt-web-ui from standard CI
> --
>
> Key: OVIRT-1408
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>Reporter: Marek Libra
>Assignee: infra
>
> Please remove github/ovirt-web-ui from standard CI since Travis is used 
> instead.



--
This message was sent by Atlassian JIRA
(v1000.1010.0#100044)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=29615#comment-29615
 ] 

Michal Skrivanek commented on OVIRT-1299:
-

+1 for ovirt-web-ui, we're going to use the same flow

> Please provide a koji (and if possible bodhi) instance for ovirt repositories
> -
>
> Key: OVIRT-1299
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: infra
>
> Some of the maintainers of oVirt project wants to have control on the builds 
> going into the release repositories without 3rd party intervention on it.
> They would like to have a dist-git + koji like developer experience.
> A bodhi instance would help reviewing the package before it lands on 
> repositories.



--
This message was sent by Atlassian JIRA
(v1000.883.0#100040)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=29507#comment-29507
 ] 

Michal Skrivanek commented on OVIRT-1250:
-

any progress? example of a message every 2 hours: 
https://github.com/oVirt/ovirt-web-ui/pull/113

> Github PR builder plugin generates too many messages
> 
>
> Key: OVIRT-1250
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Pavel Zhukov
>Assignee: infra
>
> Seems like GH PR builder plugin posts one message like:
> Can one of the admins verify this patch?
> Per job which should be triggered. For example if we have 
> el7/fc25/fc24/master jobs to be triggered by Pull Request it means message 
> will appear 4 times in the GH UI which is useless and annoying. 



--
This message was sent by Atlassian JIRA
(v1000.870.5#100039)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1249) spamming in github pull requests by ...not sure what it is.

[Michal Skrivanek (oVirt JIRA)]

Michal Skrivanek created OVIRT-1249:
---

 Summary: spamming in github pull requests by ...not sure what it 
is.
 Key: OVIRT-1249
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1249
 Project: oVirt - virtualization made easy
  Issue Type: Task
Reporter: Michal Skrivanek
Assignee: infra


See https://github.com/oVirt/ovirt-web-ui/pull/98

There's a series of comments:
@lago-bot lago-bot commented 2 days ago
Can one of the admins verify this patch?

- spamming is not useful
- i'm not clear what is it actually trying to say



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=27535#comment-27535
 ] 

Michal Skrivanek commented on OVIRT-1154:
-

Hmm, I suppose CR+1 from a maintainer is a good idea anyway. Though I'm not 
sure whther the actual list of maintainers is truly up to date and easy to 
getbut if it is it does sound good enough if the previously mentioned 
method of git log is not feasible

> Improve and automate the jenkins-whitelist mechanism
> 
>
> Key: OVIRT-1154
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> Right now our white list is based on a text file with email addresses in it. 
> Its kinda silly when we already have lists and groups of users in Gerrit.
> Some suggestions:
> * make any members of a project's "maintainers" group automatically 
> white-listed
> * make a specific group for other white-listed people 



--
This message was sent by Atlassian JIRA
(v1000.773.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=27533#comment-27533
 ] 

Michal Skrivanek commented on OVIRT-1154:
-

if you by "confirm" mean something like those "ci build" comments then please 
no. I never remember what's the right abracadabra magic wordit just sucks

> Improve and automate the jenkins-whitelist mechanism
> 
>
> Key: OVIRT-1154
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> Right now our white list is based on a text file with email addresses in it. 
> Its kinda silly when we already have lists and groups of users in Gerrit.
> Some suggestions:
> * make any members of a project's "maintainers" group automatically 
> white-listed
> * make a specific group for other white-listed people 



--
This message was sent by Atlassian JIRA
(v1000.773.2#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1154) Make jenkins-whitelist use Gerrit groups

[Michal Skrivanek (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=27300#comment-27300
 ] 

Michal Skrivanek commented on OVIRT-1154:
-

would be best to use list of contributors rather than only maintainers

> Make jenkins-whitelist use Gerrit groups
> 
>
> Key: OVIRT-1154
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins
>Reporter: Barak Korren
>Assignee: infra
>
> Right now our white list is based on a text file with email addresses in it. 
> Its kinda silly when we already have lists and groups of users in Gerrit.
> Some suggestions:
> * make any members of a project's "maintainers" group automatically 
> white-listed
> * make a specific group for other white-listed people 



--
This message was sent by Atlassian JIRA
(v1000.769.0#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra