Turning down omahaproxy.appspot.com on March 31, 2023

[Ben Mason]

Folks,

One of our longest running Google Cloud projects has seen its most useful days come and go. We will turn it down on March 31, 2023. There are still some endpoints who rely on JSON data from omahaproxy, so if you think anything you own relies on Omahaproxy (e.g. cs/ link), check out Chromium Dash instead. The following shows where the functionality of each tool in OmahaProxy can be found:

• Version Information -> branches

• Release Change Log -> releases

• Find Releases -> commits

• All versions (CSV) -> (Deprecated - if you’re using this, please reach out)

• All versions (JSON) -> Version History Chrome, All Channels, All Versions

• All info about release and DEPS -> Chromium DEPS by Release: https://chromium.googlesource.com/chromium/src.git/+/refs/tags/%s/DEPS?format=TEXT but you need to replace the %s

• Recent release history (CSV) -> (Deprecated - if you’re using this, please reach out)

• V8 version lookup (JSON) -> Possibly: https://chromium.googlesource.com/v8/v8.git/

• WK version lookup (JSON) -> Let us know if you have a dependency on this end point.

Most usage of Omahaproxy relies on /all.json. Here is an alternative source of the same data. 

Please file a bug using component=Tools>ChromiumDash if you have any concerns.

Thanks,

Ben Mason

[Reilly Grant]

Is there a replacement for the "Who" functionality for mapping @chromium.org accounts to @google.com accounts (and vice-a-versa)?

Reilly Grant | Software Engineer | rei...@chromium.org | Google Chrome

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CALovz5UBs3j_ZKTe%2B8sKnvmw3Qbg4FTH-SEhAv-ajAvAhH%3DH3g%40mail.gmail.com.

[K. Moon]

I think this has been broken for a while anyway.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAEmk%3DMYKMQg-sFff%2BhgJpxNFSKNpbB91z5ti1VOm%2BdmsgcSNKw%40mail.gmail.com.

[Matthew Blecker]

On Mon, Feb 6, 2023 at 10:37 AM Reilly Grant <rei...@chromium.org> wrote:

Is there a replacement for the "Who" functionality for mapping @chromium.org accounts to @google.com accounts (and vice-a-versa)?

Does that feature actually work today?  I just learned of it from this e-mail.  I tried the @chromium.org + @google.com e-mails of 3 people as a spot-check (including myself).  In all 6 cases the "Who Result" response was the exact e-mail I entered, without any mapping between the domains.

 

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org

View archives, change email options, or unsubscribe:

https://groups.google.com/a/chromium.org/group/chromium-os-dev

[Jakob Kummerow]

On Fri, Feb 3, 2023 at 11:17 PM 'Ben Mason' via Chromium-dev <chromi...@chromium.org> wrote:

Folks,

One of our longest running Google Cloud projects has seen its most useful days come and go. We will turn it down on March 31, 2023. There are still some endpoints who rely on JSON data from omahaproxy, so if you think anything you own relies on Omahaproxy (e.g. cs/ link), check out Chromium Dash instead. The following shows where the functionality of each tool in OmahaProxy can be found:

• Version Information -> branches

That's far from the same functionality. Filed crbug.com/1413680 (per the request at the bottom of this mail).

 

• Release Change Log -> releases

• Find Releases -> commits

• All versions (CSV) -> (Deprecated - if you’re using this, please reach out)

• All versions (JSON) -> Version History Chrome, All Channels, All Versions

• All info about release and DEPS -> Chromium DEPS by Release: https://chromium.googlesource.com/chromium/src.git/+/refs/tags/%s/DEPS?format=TEXT but you need to replace the %s 

• Recent release history (CSV) -> (Deprecated - if you’re using this, please reach out)

• V8 version lookup (JSON) -> Possibly: https://chromium.googlesource.com/v8/v8.git/

No. The V8 repository can show you the contents and history of a given V8 version (or commit), once you know which version you're interested in. When you're trying to find out which V8 version is in a given Chrome release, it can't help you.

[Raphael Kubo da Costa]

Op 03-02-2023 om 21:16 schreef 'Ben Mason' via Chromium-dev:

• All versions (CSV) -> (Deprecated - if you’re using this, please reach out)

The publish_tarball recipe uses the OmahaProxy recipe module, which fetches the CSV data from https://omahaproxy.appspot.com/history.

I've filed https://crbug.com/1413633 to track this.

[Mason Freed]

Forgive me if this exists somewhere, but I looked through the "translations" below and couldn't find the three features I use most often from Omahaproxy:

• Map from version number to chromium commit number. E.g. 109.0.5414.119 --> 1070088.
• Map from commit number to hash and version. E.g. 1070088 --> 4417ee59... and 109.0.5414.0
• List of latest Canary/Dev/Beta/Stable version numbers by platform. 

Do these exist somewhere on chromiumdash?

Thanks,

Mason

[Garrett Beaty]

I use the CSV viewer portion to check which major versions are actually pushing to what channel for each platform. I manage the Ci/CQ configurations and this allows me to turn down unnecessary testing for a platform once a particular version is no longer being pushed for the platform. How do I find that information on chromiumdash?

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/279e47d8-b503-4f13-88fc-b3a33b5429a5n%40chromium.org.

[Greg Thompson]

+1 on mapping a commit position to a version. The closest I could find maps a CL to what looks like a shipping release version, but this isn't the same thing. I very regularly want to know in which canary branch a CL first appeared.

[Peter Boström]

The best I got is: crrev.com/789456 => gives you gitiles so it gives you the hash.

Then search for the hash under commits:

https://chromiumdash.appspot.com/commits?commit=ba9d4204f0d5fd4797d805b2720ccf8d20742a9e&platform=Windows

Clicking on that commit gives:

Canary 86 86.0.4206.0 as the first Canary build that had this commit.

So https://chromium.googlesource.com/chromium/src.git/+log/refs/branch-heads/4206

Maybe there's a better way with fewer steps.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAKQnr0QnQE9vY%2BCa_Wt-QKk7KsqgFVH7_%3DcYHFiCEV-qvY2f9A%40mail.gmail.com.

[Sven Zheng]

There's a chrome extension called 'Chromium CL Finder', which will show the cl's landed version(both browser and chromeos) on gerrit. I think it's internal only now and hopefully the gerrit team can integrate it(they mentioned this).

Personally I found it very useful.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAGFX3sEgcjgLpz%3DRrNe245j0RHAtT8u%3DnFhY8S_TnLrpLxgPzA%40mail.gmail.com.

[Vladislav Kaznacheev]

I do have an internal tool that depends on https://storage.googleapis.com/chromium-find-releases-static

It is used in the pipeline that powers the ChromeOS UI Stability Triage dashboard (https://data.corp.google.com/sites/cros-ui-stability-triage). 

Among other things, the dashboard shows CLs linked to bugs, linked to crash signatures. It can even flag crashes that continue being reported after a (purported) fix has landed.

(source: https://screenshot.googleplex.com/5cAxSLQF9oRz4ts)

This automation saves us (ChromeOS UI Stability Triage rotation) a lot of time, and it would be a pity to lose it.

A few months ago I asked about a clean way to access this data here, and got pointed to https://chrome-internal.googlesource.com/infra/infra_internal/+/HEAD/doc/troopers/playbooks/workflow.md#Find-Releases, which says that the data lives in a local Python pickle file somewhere. I ended up writing my own Python script that (very gently) scrapes https://storage.googleapis.com/chromium-find-releases-static.

I wonder if this deprecation would create a strong enough reason to export this data (specifically, a mapping from a commit hash to a Chrome version) into a Plx table?

Thanks,

  Vlad

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CALcsKzgBg0scX-s1EA1wbW8uwjGQ_rAtsmF8We2%2BpmcS6Z6aUg%40mail.gmail.com.

[K. Moon]

Just a reminder that we shouldn't be posting links to or screenshots of internal tools on a public mailing list.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CA%2Br_xQQdyzL3thpKGNUAkvvgehdZtTSHC%2B_%3D_C08CKqcXR%2B%2BQA%40mail.gmail.com.

[Ken Rockot]

On Tue, Feb 7, 2023 at 9:11 AM Mason Freed <mas...@chromium.org> wrote:

Forgive me if this exists somewhere, but I looked through the "translations" below and couldn't find the three features I use most often from Omahaproxy:

• Map from version number to chromium commit number. E.g. 109.0.5414.119 --> 1070088.
• Map from commit number to hash and version. E.g. 1070088 --> 4417ee59... and 109.0.5414.0
• List of latest Canary/Dev/Beta/Stable version numbers by platform. 

Do these exist somewhere on chromiumdash?

+1 I use omahaproxy almost every day for these same tasks. It would be pretty sad to no longer have such a tool available.

I filed https://crbug.com/1415499 to track the request for Chromium Dash, though maybe there should be separate feature requests for each one.

Thanks,

Mason

On Friday, February 3, 2023 at 2:17:41 PM UTC-8 benm...@google.com wrote:

Folks,

One of our longest running Google Cloud projects has seen its most useful days come and go. We will turn it down on March 31, 2023. There are still some endpoints who rely on JSON data from omahaproxy, so if you think anything you own relies on Omahaproxy (e.g. cs/ link), check out Chromium Dash instead. The following shows where the functionality of each tool in OmahaProxy can be found:

• Version Information -> branches

• Release Change Log -> releases

• Find Releases -> commits

• All versions (CSV) -> (Deprecated - if you’re using this, please reach out)

• All versions (JSON) -> Version History Chrome, All Channels, All Versions

• All info about release and DEPS -> Chromium DEPS by Release: https://chromium.googlesource.com/chromium/src.git/+/refs/tags/%s/DEPS?format=TEXT but you need to replace the %s

• Recent release history (CSV) -> (Deprecated - if you’re using this, please reach out)

• V8 version lookup (JSON) -> Possibly: https://chromium.googlesource.com/v8/v8.git/

• WK version lookup (JSON) -> Let us know if you have a dependency on this end point.

Most usage of Omahaproxy relies on /all.json. Here is an alternative source of the same data. 

Please file a bug using component=Tools>ChromiumDash if you have any concerns.

Thanks,

Ben Mason

[Colin Blundell]

On Mon, Feb 13, 2023 at 10:34 PM 'Ken Rockot' via Chromium-dev <chromi...@chromium.org> wrote:

On Tue, Feb 7, 2023 at 9:11 AM Mason Freed <mas...@chromium.org> wrote:

Forgive me if this exists somewhere, but I looked through the "translations" below and couldn't find the three features I use most often from Omahaproxy:

• Map from version number to chromium commit number. E.g. 109.0.5414.119 --> 1070088.
• Map from commit number to hash and version. E.g. 1070088 --> 4417ee59... and 109.0.5414.0
• List of latest Canary/Dev/Beta/Stable version numbers by platform. 

Do these exist somewhere on chromiumdash?

+1 I use omahaproxy almost every day for these same tasks. It would be pretty sad to no longer have such a tool available.

+1, I do as well.

 

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CA%2BapAgFPKZZut9TgCaWXUHKjH9q%2Bs6e%3DDe6WE2F2psc0_C22rA%40mail.gmail.com.

[avm99963]

+1. Could you make https://crbug.com/1415499 public, please? I'd also be interested in following its status.

(I'm currently using omahaproxy's list of latest versions by platform here (live page))

[Adrià Vilanova Martínez]

Thanks wfh@! :)

[Alex Rudenko]

Hi, 

Puppeteer project is using https://omahaproxy.appspot.com/all.json to find the latest released revision (branch_base_position). Is there a new API on ChromiumDash that returns the revision information?
It looks like endpoints like https://versionhistory.googleapis.com/v1/chrome/platforms/all/channels/all/versions/ only return versions.

Best regards,
Alex

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/18de54a2-eec8-4bd3-8390-543bd383c93en%40chromium.org.

--

Alex Rudenko

Software Engineer

alexr...@google.com

Google Germany GmbH

Erika-Mann-Straße 33

80636 München

Geschäftsführer: Paul Manicle, Liana Sebastian

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen, dass die E-Mail an die falsche Person gesendet wurde. 

     

This e-mail is confidential. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person.

[Ben Mason]

Thanks to everyone for your responses. I am working my way through them and will get back to you all in due course.

[Geoffrey Thomas]

Can you please add a note/banner to omahaproxy directing people to chromiumdash or to this thread?

Also, I noticed today a few uses from Google sites:

- The JavaScript on https://chromeenterprise.google/browser/download/ uses /all.json, at least for display.

- https://developer.chrome.com/docs/web-platform/chrome-release-channels/ links to omahaproxy and should probably link to https://chromiumdash.appspot.com/releases instead. I think a few other pages on developer.chrome.com also link to omahaproxy.

[Caleb Raitto]

+1 -- I'd appreciate if the omahaproxy site would redirect to this thread after the deprecation.

-Caleb

[Vladislav Kaznacheev]

I was able to write my own script borrowing the crucial 10 lines of code from find_releases, so my pipeline's needs a fully satisfied.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/8cc7028f-c5bf-481c-9086-445903250b0fn%40chromium.org.

[Ben Mason]

There is https://chromiumdash.appspot.com/fetch_releases?num=1 which will show details of currently released builds and https://chromiumdash.appspot.com/fetch_version?version=110.0.5481.61 (swap out the version code) which will give you information about a version. Do those help?

On Thu, 4 May 2023 at 18:15, Tim Sullivan <tsul...@elastic.co> wrote:

I would love an answer to Alex's question as well. I am looking for a way to access the Chromium revision number from the release version.

I hope this makes sense!

[Tim Sullivan]

I would love an answer to Alex's question as well. I am looking for a way to access the Chromium revision number from the release version.

I hope this makes sense!

On Tuesday, February 21, 2023 at 1:01:08 PM UTC-7 Alex Rudenko wrote:

[Tim Sullivan]

Yes, this resource is very helpful. Thank you, Ben!

[Will Harris]

What is the nearest/easiest equivalent to e.g. https://omahaproxy.appspot.com/history?channel=stable&os=win what I am looking for is a simple list of all releases I can eyeball to e.g. know what release was out on a particular day, and also know when a particular milestone was released, with UTC timestamp, and being easily able to filter by channel and OS.

I found e.g. https://chromiumdash.appspot.com/releases?platform=Windows but I have to click 'load more' over and over to get more e.g. to get back to releases from > 1 year ago, and it does also not show UTC timestamp.

Will

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/73cdf780-8b26-4919-bdce-d73e53fd2896n%40chromium.org.

[Alexei Svitkine]

One advantage of OmahaProxy is the fact that it had all these tools in one place without needing to remember N different tools to use.

Are there any plans to make a doc or page that's a "cheatsheet" with all the links to the replacements?

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CA%2BFVm4vAJAV3gS6_EZ9nXUL6C_guHmfFHktFmndhjiy1orF3fA%40mail.gmail.com.

[Mason Freed]

Resurrecting this thread because I recently got fooled by the still-operating https://omahaproxy.appspot.com/ site. You can happily type revision numbers into the "Find Releases" blank, and while old revisions will report information, new revisions will just (forever) tell you that they haven't landed yet.

Would it be possible to remove any parts of that site that are now turned down?

Thanks,

Mason

You received this message because you are subscribed to a topic in the Google Groups "Chromium-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/chromium-dev/uH-nFrOLWtE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAKFU2SB1gRSVr4dTXfYBGAwN8yZW%2Be12UHV9xg92C_xgOVhPWw%40mail.gmail.com.