blob: 97c2fd3f2ec264fb4ea132e35017f4bf55661650 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
|
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
---
loader: taskgraph.loader.single_dep:loader
transforms:
- taskgraph.transforms.name_sanity:transforms
- taskgraph.transforms.beetmover_geckoview:transforms
- taskgraph.transforms.task:transforms
kind-dependencies:
- build-signing
only-for-attributes:
- nightly
- shippable
not-for-build-platforms:
- linux-shippable/opt
- linux64-shippable/opt
- macosx64-shippable/opt
- win32-shippable/opt
- win64-shippable/opt
- win64-aarch64-shippable/opt
- linux-devedition/opt
- linux64-devedition/opt
- macosx64-devedition/opt
- win32-devedition/opt
- win64-devedition/opt
- win64-aarch64-devedition/opt
- linux64-asan-reporter-shippable/opt
- win64-asan-reporter-shippable/opt
job-template:
attributes:
artifact_map: taskcluster/taskgraph/manifests/fennec_geckoview.yml
run-on-projects: ['mozilla-release']
run-on-hg-branches:
by-project:
mozilla-release:
- '^GECKOVIEW_\d+_RELBRANCH$'
default:
- 'all'
shipping-phase:
by-project:
# Beetmoving geckoview makes it available to the official maven repo.
# As of December 2019, we have automated betas shipped without being
# blocked on QA, hence we can upload geckoview as part of the
# `push` phase of the release graphs.
# So we want beetmover to act only when the release is greenlit. That
# is to say:
# 1. (to be changed soon to be as part of the nightly graph) right after nightly builds on mozilla-central
# 2. as part of Firefox push graphs on both mozilla-beta and mozilla-release
# 3. as part of ship-rc graphs on Firefox RC
# 4. at every patch uplifted on the GECKOVIEW_XX_RELBRANCH on mozilla-release
# Reminder: There is no Android/geckoview build on ESR.
#
# The logic of point 2 and 3 is handled in target_tasks directly because it's mixing and
# matching 2 different shipping-products
mozilla-release: build
default: push
bucket-scope:
by-release-level:
production: 'project:releng:beetmover:bucket:maven-production'
staging: 'project:releng:beetmover:bucket:maven-staging'
|
