[ https://ovirt-jira.atlassian.net/browse/OVIRT-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19205#comment-19205 ] eyal edri [Administrator] commented on OVIRT-627: ------------------------------------------------- Instead of adding a manual job, we just need to clone the current build-artifacts flow with the deploy script and experimental test job. the build artifacts can be lighter and not include all permutations.

add per patch testing flow to experimental to ovirt-engine ----------------------------------------------------------

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.217.1#100008)