[
https://ovirt-jira.atlassian.net/browse/OVIRT-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25731#comment-25731
]
eyal edri [Administrator] commented on OVIRT-1002:
--------------------------------------------------
The current system jobs which are not experimental are not functioning anymore
as "CI" jobs in a sense that they need to find new regressions.
the reason for that is they are missing the ability to be triggered per change,
like the experimental is doing and currently are running on static 'snapshot
repo', so in fact they don't provide much value.
However, instead of removing them completely in favor of experimental, we
decided to leverage them to run nightly on stable/pre releases and give us
indication that official RPMs which usually are built in a different flow than
the normal CI also pass OST.
patches are in progress to address this:
https://gerrit.ovirt.org/#/c/70425/ - changing 4.0 to run on stable latest
release ( we might want to change it to pre when RC build is in progress )
https://gerrit.ovirt.org/#/c/70424/ - renaming the jobs to reflect the real
repos they are using.
> OST jobs don't contains information about patches
> --------------------------------------------------
>
> Key: OVIRT-1002
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1002
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Pavel Zhukov
> Assignee: infra
> Labels: ost
>
> Currently OST job's "changes" link contains only changes made in OST
> repo itself as well as in jenkins repo which doesn't help to investigate
> which change(-s) in product's code brought the problem.
> Example: http://jenkins.ovirt.org/job/ovirt_4.1_system-tests/28/changes
> --
> Pavel Zhukov
> Software Engineer
> RHEV Devops
> IRC: landgraf
--
This message was sent by Atlassian JIRA
(v1000.695.1#100025)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
