[
https://ovirt-jira.atlassian.net/browse/OVIRT-2664?page=com.atlassian.jir...
]
Eyal Edri commented on OVIRT-2664:
----------------------------------
I'm not sure I agree with the reason for not finding regressions due to the job, the
failure was reported on rhev-devel list, with specific relevant people in the 'to'
field, including you Nir, on the 23/1.
Also, developers are often capable and mindful people and should be aware which version
they are testing, regardless of the default values.
The default is usually set for the last stable release, hence it was 4.2, I agree it
should be the master if its much more common now ( probably 4.3 more relevant once its out
).
I sent a patch to update the default to 'master'
https://gerrit.ovirt.org/#/c/97451/1/jobs/confs/yaml/parmeters/ost-versio...
OST runs engine 4.2 by default, misleading developers
-----------------------------------------------------
Key: OVIRT-2664
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-2664
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Nir Soffer
Assignee: infra
When creating OST manual job, the UI select engine version 4.2 by default:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/build?delay=0sec
A developer that want to test engine master must change the version
manually.
I you forget to change the version, or just do not notice that there is
engine
version to choose, your job may succeed when it actually fail with engine
master.
Watching other developers start OST jobs, they do not notice that engine
version must be selected, and treat it as the other options that most people
do not care about.
This is probably the reason why OST was broken for a week, and nobody
complained about it, since default build used engine 4.2.
How to fix:
- The UI must be changed to require engine version selection. You cannot
have default for this.
The UI should show something like:
ENGINE_VERSION: [select version] *required
- The "Build" button must be disabled if no version was selected.
Nir
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)