Closed Bug 1588425 Opened 6 years ago Closed 6 years ago

Autograph token and endpoint for Firefox Lite

Categories

(Cloud Services :: Operations: Autograph, task)

Unspecified
Android
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pliu, Assigned: u581815)

Details

Name

Pei Yun Liu (Daisy)

Email

pliu@mozilla.com

Product (ex: Firefox lite, Firefox for Android, etc)

Firefox Lite

Permissions (more info)

Permissions needed

Why

We have a new CI project for Firefox Lite so would need the same autograph token and endpoint again to deploy Firefox Lite on Playstore. Thanks !

Expiration date

2019/10/18
We are going to deploy it on 2019/10/18 (internal release ) as first Firefox Lite 2.0 release
Hopefully can get the token before 2019/10/16 so that we can configure release flow for our CI.

Vouch

Please needinfo the name of someone who has already access and could vouch for you

Flags: needinfo?(jvehent)

pliu: you just need the access tokens? If so, please provide the list of app you need to tokens for, and who they should be sent to.

Flags: needinfo?(jvehent) → needinfo?(pliu)

Julien: yes we just need autograph access token and autograph endpoint again for 1 app: Firefox LIte , as we have a new Bitrise CI project linking to Firefox Lite 2.0 private repo (https://github.com/mozilla-tw/mango) .
I am wondering if I get a new token from you for Firefox Lite 2.0 project , will the old token (which configured on Bitrise CI linking to Firefox Lite public repo https://github.com/mozilla-tw/FirefoxLite) for Firefox Lite get deprecated ?

Flags: needinfo?(pliu)

I don't think we need to change the token at this time. We should simply reuse the existing token into the new CI environment.
Do you have access to it, or should I send it again?

Good to know that. Please send to me again. I can access CI and help on the configuration. thank you!

Assignee: nobody → gguthe
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.