Closed Bug 1201222 Opened 9 years ago Closed 9 years ago

Add releng build file containing GCM SenderID private token

Categories

(Firefox Build System :: Android Studio and Gradle Integration, defect)

defect
Not set
normal

Tracking

(firefox43 affected)

RESOLVED INVALID
Tracking Status
firefox43 --- affected

People

(Reporter: nalexander, Unassigned)

References

Details

This is just like Bug 1152871, but for a new GCM SenderID token.  (Or whatever it ends up being called.)

The work for to use this is already in Bug 1179015; I'm going to land that bit under this ticket number shortly.
jrconlin: can you, or your delegate provision and provide the appropriate token file?  (It's private, so not on this ticket!)  Should these tokens be specific to a particular release channel, or is one for all versions of Fennec sufficient?

coop: who should jrconlin interact with?
Flags: needinfo?(jrconlin)
Flags: needinfo?(coop)
nalexander: The token to use for the SenderID is the Google Developer Console ProjectID for the application that will be accepting the push messages. I presume it would be whatever the ProjectID us for Fennec. 

It is possible that all release channels could go across the same GCM conduit since GCM divides things appropriately based on recipient token, however it might make sense to divvy things up if we are worried about load.
Flags: needinfo?(jrconlin)
(In reply to Nick Alexander :nalexander from comment #1) 
> coop: who should jrconlin interact with?

Redirecting to Sylvestre because relman just took over ownership of the dev console and releng doesn't necessarily have access any longer (I know I don't).

If Sylvestre can get me the ProjectID/SenderID, I can get the new token added to our CI systems.
Flags: needinfo?(coop) → needinfo?(sledru)
I tried to find it in the google play interface but I could not. Any ideas where I could find this?
Flags: needinfo?(sledru)
No longer blocks: 1179015
Depends on: fennecgcm
Folks, after reading the documentation more clearly, the Sender ID *does not need to be private*.  See the following answer, which spells things out clearly: http://stackoverflow.com/a/18216063.

It's worth recording that we can have multiple APK names (like org.mozilla.firefox and org.mozilla.fennec) register with the same Sender ID: see http://stackoverflow.com/a/11587181.
Closing this; we don't need releng involvement here.  The ID will be baked into the build publicly in Bug 1207708.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Product: Firefox for Android → Firefox Build System
You need to log in before you can comment on or make changes to this bug.