[JIRA] (OVIRT-724) Re: Lost merge rights on engine stable branch

[ https://ovirt-jira.atlassian.net/browse/OVIRT-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20427#comment-20427 ] Shlomo Ben David commented on OVIRT-724: Hi, I've restored the previous permissions fo

oVirt infra daily report - unstable production jobs - 69

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/69//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins upstream_report.html Description: Binary data __

[JIRA] (OVIRT-724) Re: Lost merge rights on engine stable branch

[ https://ovirt-jira.atlassian.net/browse/OVIRT-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shlomo Ben David reassigned OVIRT-724: -- Assignee: Shlomo Ben David (was: infra) > Re: Lost merge rights on engine stable bran

[JIRA] (OVIRT-724) Re: Lost merge rights on engine stable branch

sbonazzo created OVIRT-724: -- Summary: Re: Lost merge rights on engine stable branch Key: OVIRT-724 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-724 Project: oVirt - virtualization made easy Is

Re: Lost merge rights on engine stable branch

Opening a ticket. Il 06/Set/2016 22:04, "Piotr Kliczewski" ha scritto: > I attempted to merge few patches but it looks like I do not see merge > button on "ready to be merged patches" for engine stable branch. > > Can someone check what happened? > > Thanks, > Piotr > > _

Lost merge rights on engine stable branch

I attempted to merge few patches but it looks like I do not see merge button on "ready to be merged patches" for engine stable branch. Can someone check what happened? Thanks, Piotr ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/l

Build failed in Jenkins: ovirt_3.6_system-tests #466

See Changes: [Gal Ben Haim] Disabled cockpit installation test on basic suite 3.6 -- [...truncated 702 lines...] ## took 2391 seconds ## rc = 1

Build failed in Jenkins: ovirt_master_system-tests #493

See Changes: [Gal Ben Haim] Disabled cockpit installation test on basic suite 3.6 -- [...truncated 764 lines...] ## took 2231 seconds ## rc = 1 #

Jenkins build is back to normal : ovirt_master_system-tests #491

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Re: [JIRA] (OVIRT-696) create an 'infra-ansible' repo

On Tue, Sep 6, 2016 at 4:35 PM, Marc Dequènes (Duck) wrote: > > On 09/06/2016 10:10 PM, Barak Korren wrote: > > > I find that typically work history can be lease then ideal for > > presenting work to other developers. For me I typically find that I > > can narrow down commits by a factor of 3-5 w

Re: [JIRA] (OVIRT-696) create an 'infra-ansible' repo

On 09/06/2016 10:10 PM, Barak Korren wrote: > I find that typically work history can be lease then ideal for > presenting work to other developers. For me I typically find that I > can narrow down commits by a factor of 3-5 when going from actual work > history to a commit series that describes g

Re: [JIRA] (OVIRT-696) create an 'infra-ansible' repo

On 6 September 2016 at 15:21, Marc Dequènes (Duck) wrote: > > On 09/06/2016 09:15 PM, Marc Dequènes (Duck) wrote: > >> That is not very practical in this case. I'd like to preserve the work >> history, as said in the meeting. > > I mean in most cases squashing is perfectly fine, unless it is very

Re: [JIRA] (OVIRT-696) create an 'infra-ansible' repo

> I'm not really sure to understand what would happen if I push to review > several commit with the same Change-Id; would it create a patchset or > replace the former commits? Patch sets within the same change ID replace each other with the most recent one is the one being reviewed and potentially

Re: [JIRA] (OVIRT-696) create an 'infra-ansible' repo

On 09/06/2016 09:15 PM, Marc Dequènes (Duck) wrote: > That is not very practical in this case. I'd like to preserve the work > history, as said in the meeting. I mean in most cases squashing is perfectly fine, unless it is very big, so I agree with this method. I'm just looking for a way to get

Re: [JIRA] (OVIRT-696) create an 'infra-ansible' repo

On 09/06/2016 04:32 PM, Barak Korren wrote: > In Gerrit every commit becomes a patch, there is no way to put > multiple commits in the same patch (this is probably the most notable > difference between Gerrit and pull-request based systems). > The idea in Gerrit is that once you are done develop

[JIRA] (OVIRT-723) otopi jobs using python3 fail on fedora 24

Yedidyah Bar David created OVIRT-723: Summary: otopi jobs using python3 fail on fedora 24 Key: OVIRT-723 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-723 Project: oVirt - virtualization made

Build failed in Jenkins: ovirt_master_system-tests #490

See Changes: [Gal Ben Haim] Disabled cockpit installation test on basic suite 3.6 -- [...truncated 709 lines...] ## took 1981 seconds ## rc = 1 #

Re: Re: [ovirt-devel] I have this issue when trying to connect to gerrit

ok, can you please try to connect to gerrit.ovirt.org via port 22 and send me the output? $ ssh -vv gerrit.ovirt.org -p 22 (from your previous email i saw that your default port to the server is via 29418) BTW, why are you trying to connect to gerrit? Is there anything that i can help you with?

[JIRA] (OVIRT-708) run repos-check-closure jobs inside mock

[ https://ovirt-jira.atlassian.net/browse/OVIRT-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] snaftaly reassigned OVIRT-708: -- Assignee: snaftaly (was: infra) > run repos-check-closure jobs inside mock >

[JIRA] (OVIRT-722) rebuild alterway02 and add it to PHX engine

[ https://ovirt-jira.atlassian.net/browse/OVIRT-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-722: -- Assignee: Evgheni Dereveanchin (was: infra) > rebuild alterway02 and add it t

[JIRA] (OVIRT-722) rebuild alterway02 and add it to PHX engine

Evgheni Dereveanchin created OVIRT-722: -- Summary: rebuild alterway02 and add it to PHX engine Key: OVIRT-722 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-722 Project: oVirt - virtualization

Jenkins build is back to normal : ovirt_4.0_he-system-tests #234

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Patch pushed to stable branch not by a maintainer (?)

Hi, Roy Golan pushed this patch to the stable branch ovirt-engine-3.6 - https://gerrit.ovirt.org/#/c/62425 and it was merged, can someone please check how can a patch be merged not by Gerrit and by someone who is not a stabke branch maintainer? ___ Infra

Jenkins build is back to normal : ovirt_3.6_system-tests #463

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-721) Re: gerrit - Prevent pushing directly to origin/branches

eyal edri [Administrator] created OVIRT-721: --- Summary: Re: gerrit - Prevent pushing directly to origin/branches Key: OVIRT-721 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-721 Project:

Re: [ovirt-devel] I have this issue when trying to connect to gerrit

Hi Maokexu, Its seems that there is some iptables/firewall issue on your machine. Please make sure that port 29418 (tcp) is open. Best Regards, Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL RHCSA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011

Re: gerrit - Prevent pushing directly to origin/branches

Opening a ticket on it. On Tue, Sep 6, 2016 at 11:13 AM, Roy Golan wrote: > Using ```git push origin HEAD:origin/ovirt-engine-3.6``` I'm able to > merge my work and bypass any review. This needs to be prevented to > unprivileged people i.e only stable branch maintainers. > > See example in https

gerrit - Prevent pushing directly to origin/branches

Using ```git push origin HEAD:origin/ovirt-engine-3.6``` I'm able to merge my work and bypass any review. This needs to be prevented to unprivileged people i.e only stable branch maintainers. See example in https://gerrit.ovirt.org/#/c/62425/ ___ Infra m

Build failed in Jenkins: ovirt_master_system-tests #489

See Changes: [Gal Ben Haim] Disabled cockpit installation test on basic suite 3.6 -- [...truncated 709 lines...] ## took 1993 seconds ## rc = 1 #

Re: [lago-devel] lago_master_check-patch-fc23-x86_64 #224 Console [Jenkins]

Looks like [1] indeed. I ran my failed build with jenkins repo prior to the patch and it works. Didi, any ideas? Thanks, Nadav. http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/200/ (reverted - works) http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/196/ (wit

Re: [ovirt-devel] I have this issue when trying to connect to gerrit

Adding infra. On Tue, Sep 6, 2016 at 10:01 AM, maok...@126.com wrote: > hi,all: > I have this issue when trying to connect to gerrit: > [maokx@maokx ~]$ ssh -vv gerrit.ovirt.org > OpenSSH_6.6.1, OpenSSL 1.0.1e-fips 11 Feb 2013 > debug1: Reading configuration data /home/maokx/.ssh

Re: [JIRA] (OVIRT-696) create an 'infra-ansible' repo

On 6 September 2016 at 10:21, Marc Dequènes (Duck) wrote: > > So cleanup done. In fact the commit hook added them when doing the git > am :-/. > > So, when working on a topic branch, people usually intend to work on the > same feature, so to stakup improvements and fixes on the same > "patchset".

Re: [JIRA] (OVIRT-696) create an 'infra-ansible' repo

So cleanup done. In fact the commit hook added them when doing the git am :-/. So, when working on a topic branch, people usually intend to work on the same feature, so to stakup improvements and fixes on the same "patchset". I fail to see how to do that with git review and the current commit hoo