1509538 - Increase capacity for https://github.com/mozilla/android-components

Status: RESOLVED FIXED

(Taskcluster :: Operations and Service Requests, task)

Description

[Nick Alexander :nalexander [he/him]]

+++ This bug was initially created as a clone of Bug #1502108 +++

The Android Components team is using Taskcluster to build and release a very large suite of Kotlin components.  These components are a key piece of Mozilla's 2019 mobile strategy.

Right now, the build jobs (but not the release jobs) are running on the github-worker type (see https://github.com/mozilla-mobile/android-components/blob/2af68eb8966459fb179043464c871597a78e96d0/automation/taskcluster/decision_task.py#L39).

Let's run the playbook from Bug 1502108 and set up an a-c specific worker type.  Let's start by configuring it like `application-services-r`, although I think we actually need less compute and more memory.

Comment 1

[Nick Alexander :nalexander [he/him]]

owlish: can you drive this?

In the interim I think I can administer the `application-services-r` worker type; maybe I can let a-c use it.

Comment 2

[[:owlish] 🦉 PST]

I can create the new worker type. To make sure the name is consistent with our naming scheme... Can "android-components" be considered the analogue to "application services" or is the former part of the latter?

Also: can it wait till Monday?

Comment 3

[[:owlish] 🦉 PST]

(A later thought: I can do it today, actually. The name Q remains)

Comment 4

[Nick Alexander :nalexander [he/him]]

(In reply to Irene S [:owlish] from comment #2)
> I can create the new worker type. To make sure the name is consistent with
> our naming scheme... Can "android-components" be considered the analogue to
> "application services" or is the former part of the latter?

Yes, a-c is the analogue of a-s.  I think the "r" in "application-services-r" was actually for Rust, which isn't appropriate, so maybe just "android-components-g" (for general or Gradle)?

> Also: can it wait till Monday?

Yes.

Comment 5

[[:owlish] 🦉 PST]

> "android-components-g"
Sounds good to me!

Comment 6

[[:owlish] 🦉 PST]

Created worker type:
https://tools.taskcluster.net/aws-provisioner/android-components-g/

And scopes:
https://tools.taskcluster.net/auth/roles/project-admin%3Aandroid-components
https://tools.taskcluster.net/auth/roles/project%3Aandroid-components%3Agrants%2Fandroid-components-workers

Comment 7

[Nick Alexander :nalexander [he/him]]

owlish: could you add the create-task scopes like

queue:create-task:highest:aws-provisioner-v1/android-components-g
queue:create-task:very-high:aws-provisioner-v1/android-components-g
queue:create-task:high:aws-provisioner-v1/android-components-g
queue:create-task:medium:aws-provisioner-v1/android-components-g
queue:create-task:low:aws-provisioner-v1/android-components-g
queue:create-task:very-low:aws-provisioner-v1/android-components-g
queue:create-task:lowest:aws-provisioner-v1/android-components-g

to the roles

repo:github.com/mozilla-mobile/android-components:branch:master
repo:github.com/mozilla-mobile/android-components:pull-request
repo:github.com/mozilla-mobile/android-components:release

While you're there, can you create and add the scope

docker-worker:cache:android-components-*

for caching?  Many thanks!

Comment 8

[[:owlish] 🦉 PST]

I added the scopes to those roles. Have you tried adding those yourself? If you tried and failed, that would mean we set up something wrong. Can you please try adding 

docker-worker:cache:android-components-* 

scope to the roles

repo:github.com/mozilla-mobile/android-components:pull-request
repo:github.com/mozilla-mobile/android-components:release

so we could make sure everything is good?

Comment 9

[Nick Alexander :nalexander [he/him]]

(In reply to Irene S [:owlish] from comment #8)
> I added the scopes to those roles. Have you tried adding those yourself? If
> you tried and failed, that would mean we set up something wrong.

I tried and failed.  My belief is that I have "grant" rights for the "*create-task*" scopes, but not for the "repo:github.com/mozilla-mobile/android-components:*" roles.

 Can you
> please try adding 
> 
> docker-worker:cache:android-components-* 
> 
> scope to the roles
> 
> repo:github.com/mozilla-mobile/android-components:pull-request
> repo:github.com/mozilla-mobile/android-components:release
> 
> so we could make sure everything is good?

I will try, but I'm fairly sure I can't do this.  (I'm not part of mozilla-mobile; maybe I should be.)  And indeed, I cannot add the scope.

Comment 10

[[:owlish] 🦉 PST]

I see. I'll ask the team if the fact you don't have access to those roles means something is broken (but I think not... I think you're right - it's because you don't belong to mozilla-mobile)

I added all the scopes, so you should be all set now.

Comment 11

[[:owlish] 🦉 PST]

Yep, mozilla-mobile should grant you the access, since you're involved anyways

Comment 12

[Sebastian Kaspari (:sebastian; :pocmo)]

@owlish: Quick question about this role:

> project:android-components:grants/android-components-workers

Would it be possible to move that (or clone for now) to project:mobile? Reason for that is that we first started with separate projects (e.g. project/focus, project/android-components, project/fenix, ..), but then we noticed pretty fast that this doesn't scale well and we created project-mobile (not everything has been migrated yet) to avoid having to setup everything from scratch when creating a new mobile project.

> Yep, mozilla-mobile should grant you the access, since you're involved anyways

Yes, absolutely. I'll file something for that.

Comment 13

[[:owlish] 🦉 PST]

I created the new role https://tools.taskcluster.net/auth/roles/project%3Amobile%3Agrants%2Fandroid-components-workers

I probably can delete

> project:android-components:grants/android-components-workers

? It doesn't seem to be needed

Comment 14

[Sebastian Kaspari (:sebastian; :pocmo)]

Thank you! Yes, I think we can delete that one. :)

Comment 15

[[:owlish] 🦉 PST]

done :)