[
https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira...
]
Barak Korren commented on OVIRT-973:
------------------------------------
[~gshereme(a)redhat.com] I'm kind of opposed to adding parameters to the Standard-CI
process. The whole point of it is that one can just run "{{mock-runner.sh}}"
from a project directory without knowing anything and get results.
We need to think what is the goal we want to achieve, and then see how to fit it in the
existing framework. I will have to read the discussion here and think about this.
add support for custom build params on build-on-demand jobs
-----------------------------------------------------------
Key: OVIRT-973
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-973
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: Jenkins
Reporter: Greg Sheremeta
Assignee: infra
Labels: standard-ci
mburman [
reports|https://bugzilla.redhat.com/show_bug.cgi?id=1400010] that the nightly
ovirt-engine build is missing the Chrome permutation.
From the
[
build|http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el...]:
{noformat}
21:13:24 [INFO] Compiling 1 permutation
21:13:24 [INFO] Compiling permutation 0...
21:16:54 [INFO] Compile of permutations succeeded
{noformat}
That should compile 2 if we want Firefox and Chrome, or 3 if we also want IE.
mburman reports this started on November 30. I'm not sure what changed.
Adding build flags will fix:
DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=safari,gecko1_8"
--
This message was sent by Atlassian JIRA
(v1000.824.3#100035)