[ https://ovirt-jira.atlassian.net/browse/OVIRT-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28913#comment-28913 ] eyal edri [Administrator] commented on OVIRT-973: ------------------------------------------------- We need to find a solution for allowing builds with non default params to be triggered as part of build-on-demand, which we don't want to run all the time in CI. This makes sense for many reasons, especially now that these jobs are used for OST manual testing, for e.g: * Build all permutations to verify a UI bug * Build with DEBUG mode on, to have more logs So we need to find a generic way to support this in standard CI.

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: Improvement 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-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.824.3#100035)