1406457 - set up oak for gradle testing

Status: RESOLVED FIXED

(Release Engineering :: General, enhancement)

Comment 1

[Aki Sasaki (not active)]

First pass: https://hg.mozilla.org/projects/oak/rev/9926f91389d8

Comment 2

[Aki Sasaki (not active)]

https://tools.taskcluster.net/hooks/project-releng/nightly-fennec%2Foak is the hook. :nalexander, do you have access to trigger it?

Comment 3

[Aki Sasaki (not active)]

I'm not entirely sure which I need to change to change from org.mozilla.fennec; ANDROID_PACKAGE_NAME in mobile/android/branding/nightly/configure.sh seems likely. However, if you change this, you may not be able to install over a real m-c nightly.

https://dxr.mozilla.org/mozilla-central/search?q=org.mozilla.fennec&redirect=true

Comment 4

[Nick Alexander :nalexander [he/him]]

(In reply to Aki Sasaki [:aki] from comment #2)
> https://tools.taskcluster.net/hooks/project-releng/nightly-fennec%2Foak is
> the hook. :nalexander, do you have access to trigger it?

No, but I just filed a Service Now request to get that access (for me and for Max).

(In reply to Aki Sasaki [:aki] from comment #3)
> I'm not entirely sure which I need to change to change from
> org.mozilla.fennec; ANDROID_PACKAGE_NAME in
> mobile/android/branding/nightly/configure.sh seems likely. However, if you
> change this, you may not be able to install over a real m-c nightly.
> 
> https://dxr.mozilla.org/mozilla-central/search?q=org.mozilla.
> fennec&redirect=true

I'd prefer to _not_ change the ANDROID_PACKAGE_NAME, if that's allowed.  Johan and I talked about this, and:

- we agreed that creating "non standard Nightlies" isn't a great idea, in general;
- if we don't change the package name, the push APK tasks might not fail out, which could lead to an oak Nightly making it to the Play Store.

If we're OK not changing the ANDROID_PACKAGE_NAME, it would be really nice not to -- for testing exactly the pave-over situation you highlight above.

Johan, can you comment further?

Comment 5

[Aki Sasaki (not active)]

I think not changing ANDROID_PACKAGE_NAME makes sense.
On date we edited mobile/android/branding/nightly/configure.sh to set MOZ_APP_DISPLAYNAME="Date Nightly"; you may want something similar to visually represent the different build.

As far as pushapk, as long as we don't edit the pushapk info in taskcluster/taskgraph/util/scriptworker.py, we won't trigger valid pushapk tasks. I think we're also protected by https://github.com/mozilla-releng/scriptworker/blob/master/scriptworker/constants.py#L222 and https://github.com/mozilla-releng/scriptworker/blob/master/scriptworker/constants.py#L252-L254 .

As far as permissions for the hook, I think Service Now is probably the wrong place. What error message did you get? You'll probably need the taskcluster team to grant you the correct scopes.

Comment 6

[Aki Sasaki (not active)]

Ah, bug 1406519 is in the right component :)

Comment 7

[Nick Alexander :nalexander [he/him]]

(In reply to Aki Sasaki [:aki] from comment #5)
> I think not changing ANDROID_PACKAGE_NAME makes sense.
> On date we edited mobile/android/branding/nightly/configure.sh to set
> MOZ_APP_DISPLAYNAME="Date Nightly"; you may want something similar to
> visually represent the different build.
> 
> As far as pushapk, as long as we don't edit the pushapk info in
> taskcluster/taskgraph/util/scriptworker.py, we won't trigger valid pushapk
> tasks. I think we're also protected by
> https://github.com/mozilla-releng/scriptworker/blob/master/scriptworker/
> constants.py#L222 and
> https://github.com/mozilla-releng/scriptworker/blob/master/scriptworker/
> constants.py#L252-L254 .

Beautifiul.  I'll clear the NI for jlorenzo then.

> As far as permissions for the hook, I think Service Now is probably the
> wrong place. What error message did you get? You'll probably need the
> taskcluster team to grant you the correct scopes.

Yep -- misinterpreted PMs with gardnt.  Thanks, aki!