[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25066#comment-25066 ] Vojtech Szocs commented on OVIRT-973: ------------------------------------- bq. mburman reports this started on November 30. I'm not sure what changed. This is caused by [build-artifacts.sh patch|https://gerrit.ovirt.org/#/c/67269/], merged into master on Nov 29, which enabled the "minimal" GWT build (*Firefox only*, English only). See the related [oVirt devel thread|http://lists.ovirt.org/pipermail/devel/2016-September/028295.html]. I think it's more sensible (even though a bit more expensive CI-wise) to support Firefox *and* Chrome when doing Engine nightly builds.
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/...]: {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)