[JIRA] (OVIRT-973) add support for custom build params on build-on-demand jobs
[
https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira...
]
Greg Sheremeta commented on OVIRT-973:
--------------------------------------
[~bkorren(a)redhat.com] For the reporter of the issue, the goal is to have an entirely-built
engine, all 3 GWT permutations [*]. I assume to save resources (?), we stopped building
the Chrome permutation. The builds now only do 1 permutation for Firefox.
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)