testing/mozharness/configs/builds/releng_sub_android_configs/64_api_16_gradle.py
author Nick Alexander <nalexander@mozilla.com>
Fri, 13 Oct 2017 13:46:58 -0700
changeset 386851 1a0e10b4ea13fbae7603428de081b159378147c5
parent 377542 e3c7045f22a712f062e45ab45642c55fca0e48f7
child 389928 b4ea55eece0f8624d9bb598f1a63a5856ea7564b
permissions -rw-r--r--
Bug 1366644 - Pre: Work around mach/mozharness/mozprocess output issue. r=maliu It's unfortunate, but somehow the run-task > mozharness > mach build > mach gradle > Gradle causes Gradle to hang with no output. We avoid the bug by avoiding the `max_build_output_timeout > 0` branch in mozharness. (These tasks are all in Task Cluster, so they'll be killed eventually and it's not a huge issue to remove the output timeout.) MozReview-Commit-ID: 9wiLWS7kRQ9

config = {
    'base_name': 'Android armv7 api-16+ %(branch)s Gradle',
    'stage_platform': 'android-api-16-gradle',
    'build_type': 'api-16-gradle',
    'src_mozconfig': 'mobile/android/config/mozconfigs/android-api-16-gradle/nightly',
    'multi_locale_config_platform': 'android',
    # It's not obvious, but postflight_build is after packaging, so the Gecko
    # binaries are in the object directory, ready to be packaged into the
    # GeckoView AAR.
    'postflight_build_mach_commands': [
        ['gradle',
         'geckoview:assembleWithGeckoBinaries',
         'geckoview_example:assembleWithGeckoBinaries',
         'uploadArchives',
        ],
    ],
    'artifact_flag_build_variant_in_try': 'api-16-gradle-artifact',
    'max_build_output_timeout': 0,
}