[
https://ovirt-jira.atlassian.net/browse/OVIRT-1002?page=com.atlassian.jir...
]
eyal edri [Administrator] updated OVIRT-1002:
---------------------------------------------
Resolution: Won't Do
Status: Done (was: To Do)
Sent email to infra explaining the purpose of these jobs and also renamed them.
We can't know the full changes that happen between each run and we don't need to
because we already have this info on experimental flow.
The jobs now will be used as extra verification on official / pre releases.
If we want, we might consider implementing some logic to know the diff in terms of RPM
versions that changed between each release/build - but that will require a server like
Katello or Pulp to manage the repositories
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)