[
https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira...
]
Greg Sheremeta commented on OVIRT-973:
--------------------------------------
Alternatively, provide a way to retrigger the nightly build with some
parameter enabling the Chrome GWT permutation.
+1. That seems like the best way.
[~eedri] [~bkorren(a)redhat.com] What is the proper way to do this in Jenkins? I can try to
take a stab at it.
Will every engine job need to be updated to have this parameter added? I think (for this
use case) we could get away with only needing master on EL7 compiled for both browsers.
That's what mburman is using.
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.2#100035)