[JIRA] (OVIRT-721) Re: gerrit - Prevent pushing directly to origin/branches
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-721?page=com.atlassian.jira... ]
eyal edri [Administrator] updated OVIRT-721:
--------------------------------------------
Epic Link: OVIRT-403
> Re: gerrit - Prevent pushing directly to origin/branches
> --------------------------------------------------------
>
> Key: OVIRT-721
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-721
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: eyal edri [Administrator]
> Assignee: Shlomo Ben David
> Priority: Highest
>
> Opening a ticket on it.
> On Tue, Sep 6, 2016 at 11:13 AM, Roy Golan <rgolan(a)redhat.com> 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.ovirt.org/#/c/62425/
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian JIRA
(v1000.319.1#100012)
8 years, 2 months
[JIRA] (OVIRT-721) Re: gerrit - Prevent pushing directly to origin/branches
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-721?page=com.atlassian.jira... ]
eyal edri [Administrator] updated OVIRT-721:
--------------------------------------------
Priority: Highest (was: Medium)
> Re: gerrit - Prevent pushing directly to origin/branches
> --------------------------------------------------------
>
> Key: OVIRT-721
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-721
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: eyal edri [Administrator]
> Assignee: Shlomo Ben David
> Priority: Highest
>
> Opening a ticket on it.
> On Tue, Sep 6, 2016 at 11:13 AM, Roy Golan <rgolan(a)redhat.com> 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.ovirt.org/#/c/62425/
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R&D
> Red Hat Israel
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
--
This message was sent by Atlassian JIRA
(v1000.319.1#100012)
8 years, 2 months
[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira... ]
eyal edri [Administrator] updated OVIRT-612:
--------------------------------------------
Epic Link: OVIRT-400
> Support to FTP files for Kimchi Project
> ---------------------------------------
>
> Key: OVIRT-612
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Paulo Ricardo Paz Vital
> Assignee: infra
>
> Hello,
> Kimchi is a sub-project of oVirt and we are planning to make available to users
> simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with
> Kimchi installed in there.
> We need support to store the files and make them available to download, in a
> service like FTP. Since Kimchi mailing lists already use oVirt infrastructure,
> I'd like to know if it's possible to be supported by oVirt and how to do that.
> Thanks and best regards, Paulo.
> --
> Paulo Ricardo Paz Vital
> Linux Technology Center, IBM Systems
> http://www.ibm.com/linux/ltc/
--
This message was sent by Atlassian JIRA
(v1000.319.1#100012)
8 years, 2 months
[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.... ]
eyal edri [Administrator] updated OVIRT-95:
-------------------------------------------
Priority: Lowest
> [jenkins] add job to run upgrade vdsm from version X to version Y
> -----------------------------------------------------------------
>
> Key: OVIRT-95
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-95
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: Jenkins
> Affects Versions: Test
> Reporter: eyal edri [Administrator]
> Assignee: infra
> Priority: Lowest
> Labels: infra,vdsm,jenkins
>
> vdsm upgrade should be tested. (following on bug that was found).
> suggested flow:
> 1. install vdsm version X (e.g from 3.2)
> 2. build latest vdsm version (3.3 or master)
> 3. yum update vdsm
> 4. check if service is up and running.
--
This message was sent by Atlassian JIRA
(v1000.319.1#100012)
8 years, 2 months
[JIRA] (OVIRT-627) Implement Zuul as pre-merge action to run experimental flows
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-627?page=com.atlassian.jira... ]
eyal edri [Administrator] commented on OVIRT-627:
-------------------------------------------------
Actually replacing the existing flows which run post merge, we need to check if its possible to run pre-merge with Zuul the entire flow and reject patches if it fails.
> Implement Zuul as pre-merge action to run experimental flows
> -------------------------------------------------------------
>
> Key: OVIRT-627
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-627
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: eyal edri [Administrator]
> Assignee: infra
>
> Today, we can test a patch per project on each of the ovirt versions using experimanal flow
> i,e:
> run build_artifacts with a patch -> deploy to experimental -> run test job
> this is problematic since it actually deploys the build with the patch to the experimental repo which should only contain built pkg that are merged.
> We need to either close the flow or add param to the build artifacts that says 'create temp repo/test repo' so the built rpm won't be part of the official tested repo and the link to latest_tested won't be updated if this option is triggered.
--
This message was sent by Atlassian JIRA
(v1000.319.1#100012)
8 years, 2 months
[JIRA] (OVIRT-627) Implement Zuul as pre-merge action to run experimental flows
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-627?page=com.atlassian.jira... ]
eyal edri [Administrator] updated OVIRT-627:
--------------------------------------------
Summary: Implement Zuul as pre-merge action to run experimental flows (was: add per patch testing flow to experimental to ovirt-engine)
> Implement Zuul as pre-merge action to run experimental flows
> -------------------------------------------------------------
>
> Key: OVIRT-627
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-627
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: eyal edri [Administrator]
> Assignee: infra
>
> Today, we can test a patch per project on each of the ovirt versions using experimanal flow
> i,e:
> run build_artifacts with a patch -> deploy to experimental -> run test job
> this is problematic since it actually deploys the build with the patch to the experimental repo which should only contain built pkg that are merged.
> We need to either close the flow or add param to the build artifacts that says 'create temp repo/test repo' so the built rpm won't be part of the official tested repo and the link to latest_tested won't be updated if this option is triggered.
--
This message was sent by Atlassian JIRA
(v1000.319.1#100012)
8 years, 2 months
[JIRA] (OVIRT-731) push experimental code to git/puppet
by eyal edri [Administrator] (oVirt JIRA)
eyal edri [Administrator] created OVIRT-731:
-----------------------------------------------
Summary: push experimental code to git/puppet
Key: OVIRT-731
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-731
Project: oVirt - virtualization made easy
Issue Type: Task
Reporter: eyal edri [Administrator]
Assignee: infra
Priority: Highest
Add to resources puppet code all the scripts under deploy-ovirt-experimental user.
--
This message was sent by Atlassian JIRA
(v1000.319.1#100012)
8 years, 2 months