[JIRA] (OVIRT-383) Re: DB upgrade jobs are not using engine-setup
[ https://ovirt-jira.atlassian.net/browse/OVIRT-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-383: Resolution: Done Status: Closed (was: New) db upgrade jobs moved into standard ci. if needed, please update code in check-patch.sh > Re: DB upgrade jobs are not using engine-setup > -- > > Key: OVIRT-383 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-383 > Project: oVirt - virtualization made easy > Issue Type: Sub-task >Reporter: eyal edri [Administrator] >Assignee: snaftaly > > Also replacing support-infra with infra-support which is the right email to > open a ticket. > e. > On Wed, Jan 13, 2016 at 4:49 PM, Eyal Edri wrote: > > Hi, > > > > The scripts used to run the job can be found here [1]. > > Specifically: > > > > ovirt-engine_upgrade-db.cleanup.sh > > ovirt-engine_upgrade-db.sh > > > > If you can submit a patch to replace the logic to use engine-setup > > instead, the jobs will update automatically via yaml to use the new logic. > > infra team can help with verification if needed. > > > > Eyal. > > > > [1] > > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs/shell-scripts;h=a919553fd30c2da2c145ed70f25d1c3000144501;hb=refs/heads/master > > > > On Wed, Jan 13, 2016 at 4:36 PM, Eli Mesika wrote: > > > >> Hi > >> > >> Currently DB upgrade jobs are using schema.sh script and not engine-setup > >> This may cause CI upgrade tests to be successful while they are actually > >> failed when running from engine-setup > >> Since we are using engine-setup to upgrade the database, CI tests must > >> use the same exact method in order to be reliable > >> I had faced this week 2 different cases when my patches passed CI but > >> failed actually engine-setup causing a loose of time to me and to other > >> that already rebased on a problematic patch. > >> > >> > >> Thanks > >> Eli Mesika > >> > >> ___ > >> Infra mailing list > >> Infra@ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/infra > >> > >> > >> > > > > > > -- > > Eyal Edri > > Associate Manager > > EMEA ENG Virtualization R&D > > Red Hat Israel > > > > phone: +972-9-7692018 > > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > > -- > Eyal Edri > Associate Manager > 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.5.0#72002) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-383) Re: DB upgrade jobs are not using engine-setup
[ https://ovirt-jira.atlassian.net/browse/OVIRT-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-383: Issue Type: Sub-task (was: By-EMAIL) Parent: OVIRT-384 > Re: DB upgrade jobs are not using engine-setup > -- > > Key: OVIRT-383 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-383 > Project: oVirt - virtualization made easy > Issue Type: Sub-task >Reporter: eyal edri [Administrator] >Assignee: snaftaly > > Also replacing support-infra with infra-support which is the right email to > open a ticket. > e. > On Wed, Jan 13, 2016 at 4:49 PM, Eyal Edri wrote: > > Hi, > > > > The scripts used to run the job can be found here [1]. > > Specifically: > > > > ovirt-engine_upgrade-db.cleanup.sh > > ovirt-engine_upgrade-db.sh > > > > If you can submit a patch to replace the logic to use engine-setup > > instead, the jobs will update automatically via yaml to use the new logic. > > infra team can help with verification if needed. > > > > Eyal. > > > > [1] > > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs/shell-scripts;h=a919553fd30c2da2c145ed70f25d1c3000144501;hb=refs/heads/master > > > > On Wed, Jan 13, 2016 at 4:36 PM, Eli Mesika wrote: > > > >> Hi > >> > >> Currently DB upgrade jobs are using schema.sh script and not engine-setup > >> This may cause CI upgrade tests to be successful while they are actually > >> failed when running from engine-setup > >> Since we are using engine-setup to upgrade the database, CI tests must > >> use the same exact method in order to be reliable > >> I had faced this week 2 different cases when my patches passed CI but > >> failed actually engine-setup causing a loose of time to me and to other > >> that already rebased on a problematic patch. > >> > >> > >> Thanks > >> Eli Mesika > >> > >> ___ > >> Infra mailing list > >> Infra@ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/infra > >> > >> > >> > > > > > > -- > > Eyal Edri > > Associate Manager > > EMEA ENG Virtualization R&D > > Red Hat Israel > > > > phone: +972-9-7692018 > > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > > -- > Eyal Edri > Associate Manager > 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 (v7.2.0-OD-03-014#72000) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-383) Re: DB upgrade jobs are not using engine-setup
[ https://ovirt-jira.atlassian.net/browse/OVIRT-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] reassigned OVIRT-383: --- Assignee: snaftaly (was: infra) > Re: DB upgrade jobs are not using engine-setup > -- > > Key: OVIRT-383 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-383 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL >Reporter: eyal edri [Administrator] >Assignee: snaftaly > > Also replacing support-infra with infra-support which is the right email to > open a ticket. > e. > On Wed, Jan 13, 2016 at 4:49 PM, Eyal Edri wrote: > > Hi, > > > > The scripts used to run the job can be found here [1]. > > Specifically: > > > > ovirt-engine_upgrade-db.cleanup.sh > > ovirt-engine_upgrade-db.sh > > > > If you can submit a patch to replace the logic to use engine-setup > > instead, the jobs will update automatically via yaml to use the new logic. > > infra team can help with verification if needed. > > > > Eyal. > > > > [1] > > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs/shell-scripts;h=a919553fd30c2da2c145ed70f25d1c3000144501;hb=refs/heads/master > > > > On Wed, Jan 13, 2016 at 4:36 PM, Eli Mesika wrote: > > > >> Hi > >> > >> Currently DB upgrade jobs are using schema.sh script and not engine-setup > >> This may cause CI upgrade tests to be successful while they are actually > >> failed when running from engine-setup > >> Since we are using engine-setup to upgrade the database, CI tests must > >> use the same exact method in order to be reliable > >> I had faced this week 2 different cases when my patches passed CI but > >> failed actually engine-setup causing a loose of time to me and to other > >> that already rebased on a problematic patch. > >> > >> > >> Thanks > >> Eli Mesika > >> > >> ___ > >> Infra mailing list > >> Infra@ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/infra > >> > >> > >> > > > > > > -- > > Eyal Edri > > Associate Manager > > EMEA ENG Virtualization R&D > > Red Hat Israel > > > > phone: +972-9-7692018 > > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > > -- > Eyal Edri > Associate Manager > 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 (v7.2.0-OD-03-014#72000) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-383) Re: DB upgrade jobs are not using engine-setup
Title: Message Title eyal edri [Administrator] created an issue oVirt - virtualization made easy / OVIRT-383 Re: DB upgrade jobs are not using engine-setup Issue Type: By-EMAIL Assignee: infra Created: 07/Feb/16 1:44 PM Priority: Medium Reporter: eyal edri [Administrator] Also replacing support-infra with infra-support which is the right email to open a ticket. e. On Wed, Jan 13, 2016 at 4:49 PM, Eyal Edri wrote: > Hi, > > The scripts used to run the job can be found here [1]. > Specifically: > > ovirt-engine_upgrade-db.cleanup.sh > ovirt-engine_upgrade-db.sh > > If you can submit a patch to replace the logic to use engine-setup > instead, the jobs will update automatically via yaml to use the new logic. > infra team can help with verification if needed. > > Eyal. > > [1] > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs/shell-scripts;h=a919553fd30c2da2c145ed70f25d1c3000144501;hb=refs/heads/master > > On Wed, Jan 13, 2016 at 4:36 PM, Eli Mesika wrote: > >> Hi >> >> Currently DB upgrade jobs are using schema.sh script and not engine-setup >> This may cause CI upgrade tests to be successful while they are actually >> failed when running from engine-setup >> Since we are using engine-setup to upgrade the database, CI tests must >> use the same exact method in order to be reliable >> I had faced this week 2 different cases when my patches passed CI but >> failed actually engine-setup causing a loose of time to me and to other >> that already rebased on a problematic patch. >> >> >> Thanks >> Eli Mesika >> >> ___ >> Infra mailing list >> Infra@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/infra >> >> >> > > > – > Eyal Edri > Associate Manager > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) > – Eyal Edri Associate Manager EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
[JIRA] (OVIRT-383) Re: DB upgrade jobs are not using engine-setup
Title: Message Title bkorren commented on OVIRT-383 Re: Re: DB upgrade jobs are not using engine-setup I wonder if the upgrade jobs could somehow be converted into standard-CI. Are they running on every merge atm? On 13 January 2016 at 16:52, Eyal Edri wrote: > Also replacing support-infra with infra-support which is the right email to > open a ticket. > > e. > > On Wed, Jan 13, 2016 at 4:49 PM, Eyal Edri wrote: >> >> Hi, >> >> The scripts used to run the job can be found here [1]. >> Specifically: >> >> ovirt-engine_upgrade-db.cleanup.sh >> ovirt-engine_upgrade-db.sh >> >> If you can submit a patch to replace the logic to use engine-setup >> instead, the jobs will update automatically via yaml to use the new logic. >> infra team can help with verification if needed. >> >> Eyal. >> >> [1] >> https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs/shell-scripts;h=a919553fd30c2da2c145ed70f25d1c3000144501;hb=refs/heads/master >> >> On Wed, Jan 13, 2016 at 4:36 PM, Eli Mesika wrote: >>> >>> Hi >>> >>> Currently DB upgrade jobs are using schema.sh script and not engine-setup >>> This may cause CI upgrade tests to be successful while they are actually >>> failed when running from engine-setup >>> Since we are using engine-setup to upgrade the database, CI tests must >>> use the same exact method in order to be reliable >>> I had faced this week 2 different cases when my patches passed CI but >>> failed actually engine-setup causing a loose of time to me and to other that >>> already rebased on a problematic patch. >>> >>> >>> Thanks >>> Eli Mesika >>> >>> ___ >>> Infra mailing list >>> Infra@ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/infra >>> >>> >> >> >> >> – >> Eyal Edri >> Associate Manager >> EMEA ENG Virtualization R&D >> Red Hat Israel >> >> phone: +972-9-7692018 >> irc: eedri (on #tlv #rhev-dev #rhev-integ) > > > > > – > Eyal Edri > Associate Manager > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > ___ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > – Barak Korren bkor...@redhat.com RHEV-CI Team Add Comment
