[JIRA] (OVIRT-1427) Dependencies between ovirt-engine and
vdsm-jsonrpc-java
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1427?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1427:
--------------------------------
Epic Link: OVIRT-2184 (was: OVIRT-400)
> Dependencies between ovirt-engine and vdsm-jsonrpc-java
> -------------------------------------------------------
>
> Key: OVIRT-1427
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1427
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Piotr Kliczewski
> Assignee: infra
>
> Recently we had and issue that newer version of vdsm-jsonrpc-java was
> available but engine spec was not updated yet. Engine patch contained spec
> and module.xml changes which provided dependencies required by new version
> of jsonrpc. CI used the new version of jsonrpc without engine patch being
> merged which caused several issues.
> This ticket is open to track how we could mitigate similar issues in the
> future.
> Thanks,
> Piotr
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-1427) Dependencies between ovirt-engine and
vdsm-jsonrpc-java
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1427?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1427:
--------------------------------
Epic Link: OVIRT-2184 (was: OVIRT-400)
> Dependencies between ovirt-engine and vdsm-jsonrpc-java
> -------------------------------------------------------
>
> Key: OVIRT-1427
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1427
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Reporter: Piotr Kliczewski
> Assignee: infra
>
> Recently we had and issue that newer version of vdsm-jsonrpc-java was
> available but engine spec was not updated yet. Engine patch contained spec
> and module.xml changes which provided dependencies required by new version
> of jsonrpc. CI used the new version of jsonrpc without engine patch being
> merged which caused several issues.
> This ticket is open to track how we could mitigate similar issues in the
> future.
> Thanks,
> Piotr
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2184) Full change isulation for CQ/OST
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-2184:
-----------------------------------
Summary: Full change isulation for CQ/OST
Key: OVIRT-2184
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2184
Project: oVirt - virtualization made easy
Issue Type: Epic
Components: Change Queue
Reporter: Barak Korren
Assignee: infra
As an ovirt developer i want to know that failures in OST can be narrowed down to a single change regardless of the source this change came from.
h3. Acceptance Criteria
# All change sources that can affect OST outcome are monitored and can be isolated by CQ including:
## Patches to oVirt packages
## Patches to OST
## Changes to Lago
## Changes to platform (non-oVirt) packages
## Changes to the CI infrastructure
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months