My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 150860: Integrate Chrome for Android channels into http://omahaproxy.appspot.com/viewer
21 people starred this issue and may be notified of changes. Back to list
 
Project Member Reported by srika...@chromium.org, Sep 19, 2012
Application Version (from "Chrome Settings > About Chrome"): 
Android Build Number (from "Android Settings > About Phone/Tablet"): 
Device: 

Steps to reproduce: 

Observed behavior: 

Expected behavior: 

Frequency: 
<number of times you were able to reproduce> 

Additional comments: 

Sep 19, 2012
#1 srika...@chromium.org
Oops..hit enter too soon - please feel free to delete the null comment above

Need to start publishing our releases in a manner that we can track what is on which channel (and ensure downstream dashboard etc like https://uma.googleplex.com/stability/ etc pick it up).

kerz@ / laforge@ - pointers on what needs to happen for this?
Summary: Integrate Chrome for Android channels into http://omahaproxy.appspot.com/viewer
Cc: vino...@chromium.org lafo...@chromium.org
Labels: -Pri-3 Pri-2 Type-Feature Build-Infrastructure Mstone-24 ReleaseBlock-Dev
Sep 19, 2012
#2 kerz@google.com
I'll look into this in the coming weeks.  Shouldn't be too hard.
Oct 1, 2012
#3 sulli...@chromium.org
We use the version data in the UMA timeline dashboard, it would be really great to have for Android.
Cc: sulli...@chromium.org simonjam@chromium.org tony@chromium.org
Oct 1, 2012
#4 lafo...@google.com
Unfortunately there is no public source of data (that I'm aware of) that contains the current version information for OmahaProxy to poll.  The reason that we are able to do it w/ the iOS builds is that the team publishes Omaha config changes when they do a push (and I can simply ask Omaha).  If there is something similar for Android releases, I'd be happy to add that Android builds to OmahaProxy as well.
Oct 1, 2012
#5 sulli...@chromium.org
(No comment was entered for this change.)
Cc: -tony@chromium.org tonyg@chromium.org
Oct 1, 2012
#6 sulli...@chromium.org
Thanks for the update, laforge! kerz, are you the right assignee for this or does something need to be added to Android releases before you can help?
Oct 1, 2012
#7 kerz@google.com
This is on the list to be done, we still have to figure out how.
Oct 9, 2012
#8 srika...@chromium.org
(No comment was entered for this change.)
Labels: Area-Build
Oct 31, 2012
#9 srika...@chromium.org
 Issue 158729  has been merged into this issue.
Oct 31, 2012
#10 peter@chromium.org
 Issue 158729  has been merged into this issue.
Oct 31, 2012
#11 srika...@chromium.org
Opening up the bug as this is relevant to integrating with Chromium in general
Labels: -Restrict-View-Google
Nov 8, 2012
#12 srika...@chromium.org
(No comment was entered for this change.)
Blockedon: chromium:159476
Nov 13, 2012
#13 vino...@google.com
(No comment was entered for this change.)
Labels: -Mstone-24 Mstone-25
Nov 24, 2012
#14 srika...@chromium.org
In addition to the listing public channels when we get to it, would be great to see if we can get the  canary channel (internal only from Clankium trunk) available on this dashboard as well. Feasible? 
Nov 27, 2012
#15 lafo...@google.com
(No comment was entered for this change.)
Labels: Project-Refresh
Nov 28, 2012
#16 srika...@chromium.org
(No comment was entered for this change.)
Labels: -Pri-2 Pri-1
Nov 28, 2012
#17 kerz@google.com
Likely not feasible for Canary unless we figure out the automation.  These values are all hand pushed, and will likely have to be for Clank as well.  I'll set up the initial configs to start based on the iOS ones, and we'll go from there.
Dec 3, 2012
#18 vino...@chromium.org
(No comment was entered for this change.)
Labels: -ReleaseBlock-Dev
Dec 3, 2012
#19 srika...@chromium.org
(No comment was entered for this change.)
Labels: ReleaseBlock-Beta
Dec 5, 2012
#20 srika...@chromium.org
(No comment was entered for this change.)
Blocking: chromium:158400
Dec 5, 2012
#21 srika...@chromium.org
(No comment was entered for this change.)
Blocking: chromium:164456
Jan 3, 2013
#22 srika...@chromium.org
(No comment was entered for this change.)
Labels: -Type-Feature -Project-Refresh Type-Cleanup
Jan 8, 2013
#23 kerz@google.com
(No comment was entered for this change.)
Labels: -ReleaseBlock-Beta ReleaseBlock-Stable
Jan 9, 2013
#24 bugdro...@chromium.org
The following revision refers to this bug:
    http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=32319

------------------------------------------------------------------------
r32319 | kerz@google.com | 2013-01-09T17:27:25.645590Z

------------------------------------------------------------------------
Jan 9, 2013
#25 bugdro...@chromium.org
The following revision refers to this bug:
    http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=32320

------------------------------------------------------------------------
r32320 | kerz@google.com | 2013-01-09T17:27:32.078408Z

------------------------------------------------------------------------
Jan 28, 2013
#26 vino...@chromium.org
(No comment was entered for this change.)
Labels: -Mstone-25 -ReleaseBlock-Stable Mstone-26 MovedFrom-25
Feb 5, 2013
#27 bugdro...@chromium.org
The following revision refers to this bug:
    http://goto.ext.google.com/viewvc/chrome-internal?view=rev&revision=33292

------------------------------------------------------------------------
r33292 | kerz@google.com | 2013-02-05T20:55:49.723984Z

------------------------------------------------------------------------
Feb 5, 2013
#28 bugdro...@chromium.org
Project: .../internal/apps
Branch : master
Author : Jason Kersey <kerz@google.com>
Commit : e5fbebc8b38440debe3d1a91ca22acc987eae86b

Code Review +2: Isaac Levy
Verified    +1: Jason Kersey
Change-Id     : Ieae56c30b65a9c36628ea5bf5205e6d5bd982934
Reviewed-at   : https://gerrit-int.chromium.org/32085
Feb 6, 2013
#29 kerz@google.com
Fixed.
Status: Fixed
Feb 14, 2013
#30 mar...@minimum.se
kerz, the blog ([1]) posted a 25.0.1364.84 beta release 16 hours ago but nothing yet on omaha? Is there some delay by design or did someone forget to press some button somewhere?

[1] http://googlechromereleases.blogspot.com/2013/02/beta-channel-update_13.html
Feb 14, 2013
#31 kerz@google.com
We did not release for android.
Mar 9, 2013
#32 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Pri-1 -Type-Cleanup -Area-Build -Mstone-26 Build M-26 Type-Bug Pri-3
Jul 1, 2013
#33 benhe...@google.com
(No comment was entered for this change.)
Labels: -Build-Infrastructure Infra
Sign in to add a comment

Powered by Google Project Hosting