[JIRA] (OVIRT-973) nightly ovirt-engine build is missing Chrome permutation

[Vojtech Szocs (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25095#comment-25095 ] 

Vojtech Szocs commented on OVIRT-973:
-------------------------------------

bq. How much time it will add if we'll add chrome to the permutations?
At least +50% GWT build time, I'd say.

bq. I wouldn't want to pay a constant time penalty just because a single manual test needed it.
Agreed. GWT Chrome build should be opt-in, only when needed.

bq. You can easily send a patch to build-artifacts with the permutations you want and then use the 'build-on-demand' job using 'ci please build' to build rpms using the new PARAMS.
Good point, but can we have a "long standing" (forever open) patch for this purpose?

Just to clarify, what I meant in my previous comment was this:
1, user gets a nightly Engine build (FF-only)
2, user decides he/she needs Chrome support for that particular build
3, user re-triggers the particular build and passes some param (defined in Jenkins job config and somehow passed to build script) to trigger Chrome GWT permutation

> nightly ovirt-engine build is missing Chrome permutation
> --------------------------------------------------------
>
>                 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
>
> 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-el7-x86_64/2068/consoleFull]:
> {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.621.5#100023)