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
>
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
>
[
https://ovirt-jira.atlassian.net/browse/OVIRT-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
eyal edri [Administrator] reassigned OVIRT-384:
---
Assignee: snaftaly (was: infra)
> DB upgrade jobs are not us
[
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 j
: Re: DB upgrade jobs are not using engine-setup
- virtualization made easy / OVIRT-384
DB upgrade jobs are not using engine-setup
- virtualization made easy / OVIRT-383
Re: DB upgrade jobs are not using engine-setup
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
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,
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
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
>
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
12 matches
Mail list logo