540ab87aab7f387cad4503c1824b0b8c5233b4c8: Bug 1407672 - Pre: Include rsync in android-build image for l10n repacks. r=Callek draft
Nick Alexander <nalexander@mozilla.com> - Tue, 10 Oct 2017 16:39:39 -0700 - rev 678609
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1407672 - Pre: Include rsync in android-build image for l10n repacks. r=Callek MozReview-Commit-ID: 7Oc0G7SQDEI
214cb4c994863674814819f88ce57e479a7e2dc2: Try to work around Gradle crashes. draft
Nick Alexander <nalexander@mozilla.com> - Tue, 10 Oct 2017 11:41:04 -0700 - rev 678608
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Try to work around Gradle crashes. MozReview-Commit-ID: 2KIAYQVXM10
c70bc69868885ae3a89169bd97f470866b278fc0: log around aapt draft
Nick Alexander <nalexander@mozilla.com> - Tue, 10 Oct 2017 15:17:33 -0700 - rev 678607
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
log around aapt MozReview-Commit-ID: 6SRCHmJzxnf
0e4e5d68f87c29ed06f08d5da4c1f4bb1d975475: Try to work around Python/Gradle buffering incompatibilities. draft
Nick Alexander <nalexander@mozilla.com> - Fri, 06 Oct 2017 16:34:17 -0700 - rev 678606
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Try to work around Python/Gradle buffering incompatibilities. MozReview-Commit-ID: FcMylfg6bqx
e8ccaceb49c43b4735e8c5aa24d710fcdb233d09: Looks like Gradle lint output location changed. draft
Nick Alexander <nalexander@mozilla.com> - Wed, 23 Aug 2017 08:49:09 -0700 - rev 678605
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Looks like Gradle lint output location changed. MozReview-Commit-ID: FYWusxWhfJp
d019a936a03d1c706ca19f487ffd73f06decf804: Bug 1366644 - Update Android build-tools (25.0.3), Gradle (3.4.1), Android-Gradle (2.3.3). r=maliu draft
Nick Alexander <nalexander@mozilla.com> - Wed, 21 Jun 2017 10:55:27 -0700 - rev 678604
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1366644 - Update Android build-tools (25.0.3), Gradle (3.4.1), Android-Gradle (2.3.3). r=maliu The goal is to use a newer Android-Gradle build plugin version (2.3.3 is latest stable). That requires a modern Gradle (anything 3.3+, but 3.4.1 is the default from my Android Studio), and also a newer build-tools (25.0.3 is latest stable). MozReview-Commit-ID: IJoqDaJs0sw
a79ce6276f4a5a8278ff75847303adaf1963533b: Bug 1352015 - Part 1: Work around new deprecation warnings from Android SDK 25/26. r=maliu draft
Nick Alexander <nalexander@mozilla.com> - Wed, 21 Jun 2017 10:11:03 -0700 - rev 678603
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1352015 - Part 1: Work around new deprecation warnings from Android SDK 25/26. r=maliu MozReview-Commit-ID: CDDGqQBQHDS
9c2110acb75c643dc049c1c4a67a4125ce1725e9: Bug 1352015 - Pre: Avoid deprecated Gradle features. r=maliu draft
Nick Alexander <nalexander@mozilla.com> - Tue, 20 Jun 2017 16:50:12 -0700 - rev 678602
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1352015 - Pre: Avoid deprecated Gradle features. r=maliu MozReview-Commit-ID: LZ9clAsEUkd
98440d11720b2f0b67d7ad512f3ba9ac5d84fd9a: Bug 1370119 - Pre: Bump Gradle JVM heap to allow in-process dex. r=sebastian draft
Nick Alexander <nalexander@mozilla.com> - Tue, 18 Jul 2017 17:59:57 -0700 - rev 678601
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1370119 - Pre: Bump Gradle JVM heap to allow in-process dex. r=sebastian In-process dex is a slight performance win. This also upgrades `dexcount-gradle-plugin` to 0.7.1. MozReview-Commit-ID: 2Bg5qX41pHB
6e4397f157108081ad90de7bad6432c583f9ff5f: Bug 1405413 - Migrate Gradle dependency fetching to toolchain dependencies. r=dustin draft
Nick Alexander <nalexander@mozilla.com> - Tue, 03 Oct 2017 13:09:49 -0700 - rev 678600
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1405413 - Migrate Gradle dependency fetching to toolchain dependencies. r=dustin MozReview-Commit-ID: I9i29g6C2CS
97e3f1b1ed36c00b9033fc92ec15e7e50a897820: Bug 1405413 - Pre: Work around sparse checkouts in taskgraph. r=dustin draft
Nick Alexander <nalexander@mozilla.com> - Thu, 05 Oct 2017 17:23:00 -0700 - rev 678599
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1405413 - Pre: Work around sparse checkouts in taskgraph. r=dustin MozReview-Commit-ID: 3GKDG50i7ql
1d80c1457cceb56eb2001a0ebb4a556daec1633d: Bug 1405412 - Post: Remove JDK repackaging script. r=dustin draft
Nick Alexander <nalexander@mozilla.com> - Thu, 05 Oct 2017 16:57:40 -0700 - rev 678598
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1405412 - Post: Remove JDK repackaging script. r=dustin I don't think (the output of) this script is used anywhere. MozReview-Commit-ID: DwMFtpozjNL
8643cdc03d78300dee7033838bb3e0d302f75972: Bug 1405412 - Migrate Android SDK to android-sdk-linux toolchain task. r=dustin draft
Nick Alexander <nalexander@mozilla.com> - Tue, 03 Oct 2017 11:45:27 -0700 - rev 678597
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1405412 - Migrate Android SDK to android-sdk-linux toolchain task. r=dustin The only tricky piece here is that the resulting toolchain archive is private, and uses a newly allocated Task Cluster scope (queue:get-artifact:project/gecko/android-sdk/*) to restrict access to the archive. All SCM levels (1, 2, 3) have been given the new scope: see https://tools.taskcluster.net/auth/roles/moz-tree:level:1 and friends. MozReview-Commit-ID: CcDqDOHODpe
f414ec8651c8ba73faa8e04728572595e4a6e990: Bug 1405412 - Pre: Allow toolchain task images to not cache tc-vcs. r=dustin draft
Nick Alexander <nalexander@mozilla.com> - Thu, 05 Oct 2017 15:55:23 -0700 - rev 678596
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1405412 - Pre: Allow toolchain task images to not cache tc-vcs. r=dustin Not all Docker images are configured for tc-vcs caches: in particular, android-build is not configured. Until we fully remove tc-vcs, this will let toolchain tasks use non-tc-vcs caching images. MozReview-Commit-ID: CYSdn2kpF3S
9cfcdb425b91d4b82808bd1977a8f53a834a144f: Bug 1405408 - Post: Use taskcluster-proxy /bewit endpoint to download private toolchains. r=dustin draft
Nick Alexander <nalexander@mozilla.com> - Thu, 05 Oct 2017 16:17:58 -0700 - rev 678595
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1405408 - Post: Use taskcluster-proxy /bewit endpoint to download private toolchains. r=dustin This is a work-around until Bug 1405889 is deployed. Using the /bewit endpoint does have the advantage of avoiding another issue in taskcluster-proxy, namely that the /bewit approach streams. Fetching through the proxy does not stream from the upstream resource; the upstream resource is fetched and stored in taskcluster-proxy's memory, increasing operational costs. MozReview-Commit-ID: 8yS7zKLALhd
d0c38c932aab2e2732cea7c9f3337edfaac2e59a: Bug 1405408 - Part 2: Add taskcluster-proxy and scopes to tasks consuming non-public/ toolchains. r=dustin draft
Nick Alexander <nalexander@mozilla.com> - Thu, 05 Oct 2017 16:41:43 -0700 - rev 678594
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1405408 - Part 2: Add taskcluster-proxy and scopes to tasks consuming non-public/ toolchains. r=dustin MozReview-Commit-ID: BIGjLXmTSli
b89485a567e06f9b9e7aad488df8f0dd0d1c86a7: Bug 1405408 - Part 1: Use Task Cluster proxy to download non-public artifacts. r=dustin draft
Nick Alexander <nalexander@mozilla.com> - Wed, 04 Oct 2017 13:24:41 -0700 - rev 678593
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1405408 - Part 1: Use Task Cluster proxy to download non-public artifacts. r=dustin MozReview-Commit-ID: L6VfQuAmHLC
181fcf2b76554b825626b7a85a775d21595b9b04: Bug 1405408 - Part 0: Let toolchain tasks create non-public/build artifacts. r=dustin draft
Nick Alexander <nalexander@mozilla.com> - Thu, 05 Oct 2017 16:02:20 -0700 - rev 678592
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1405408 - Part 0: Let toolchain tasks create non-public/build artifacts. r=dustin There's code that carefully uses `setdefault('artifacts', [])` in the same file, but then stomps on 'artifacts' before that's invoked. This allows tasks to change where public/build is sourced from, and to add additional artifact locations (including private locations). MozReview-Commit-ID: JqyHew5bGv5
b7662fbc748f03f066406cc99f38ec17099559fe: Bug 1405408 - Pre: Handle query string and fragments in URL parameters. r=dustin draft
Nick Alexander <nalexander@mozilla.com> - Thu, 05 Oct 2017 13:30:21 -0700 - rev 678591
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1405408 - Pre: Handle query string and fragments in URL parameters. r=dustin This was simply oversight before. I ran into this using the taskcluster-proxy /bewit interface, which returns a URL of the form https://domain.net/short/path/to.file?bewit="several thousand characters", which leads to an IOError due to the long path. Let's assume that such query strings and fragments are transient; we should drop these parts of the fetched URLs when writing to disk. MozReview-Commit-ID: FMJHMp7a3rA
f29d309fd2888134a9a97ebb22adf50c6e923bad: Bug 1406196 - Move GRADLE_USER_HOME in tree. r=maliu draft
Nick Alexander <nalexander@mozilla.com> - Thu, 05 Oct 2017 14:59:26 -0700 - rev 678590
Push 83975 by nalexander@mozilla.com at Wed, 11 Oct 2017 16:10:55 +0000
Bug 1406196 - Move GRADLE_USER_HOME in tree. r=maliu The goal of this approach is to tell Gradle to not connect (or allow it to connect) to the network when fetching dependencies. No Android automation tasks should fetch from the network, except the toolchain tasks (which are specially intended to do so). It's difficult to arrange this without including the `--offline` flag everywhere. It _should_ be possible to set offline using an environment variable -- which would allow us to get rid of these dotgradle-* files -- but offline isn't an option in https://docs.gradle.org/4.2.1/userguide/build_environment.html#sec:gradle_configuration_properties (and certainly not in earlier versions either). Therefore, environment variable that points to an init.gradle file in automation. Before this patch, the files telling Gradle whether to start offline were fetched from tooltool. That's just a layer that doesn't need to be there. None of this impacts local developers. MozReview-Commit-ID: LAXktbBu1Az
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip