How to identify valid revision hash to use with https://chrome-devtools-frontend.appspot.com for devtools frontend

[lan...@vewd.com]

Hi,
I wonder how I can identify a valid chromium commit hash to use with the appspot hosted devtools frontend. Seems that most of the hashes work, just testing "random" ones for a year back but not all unfortunately.
I essentially want to map a version of Google Chrome to a valid hash.
What I have been trying to do is to use the Chrome tagged release commit but that fails for current stable (62.0.3202.94) for instance. However the commit that is mentioned as "Revision" in chrome://version (which is the commit that updates the chrome/VERSION file) gives me a frontend.

So this works: https://chrome-devtools-frontend.appspot.com/serve_rev/@4fd852a98d66564c88736c017b0a0b0478e885ad/inspector.html
This gives a 404: https://chrome-devtools-frontend.appspot.com/serve_rev/@937db09514e061d7983e90e0c448cfa61680f605/inspector.html

Thanks,
David

[lan...@vewd.com]

Anyone has info on this? This is essentially a question on how the mapping from commit hash to a devtools frontend is done on the appspot server.

/David

[Will Chen]

In theory, the uploader should upload all of the Chromium commits because it iterates through master and all release branches. In practice, certain commits, such as the automated publishing commit that you linked to, aren't uploaded because they aren't part of a branch due to an idiosyncrasy of Chromium's build process. As you mentioned, chrome://version is a simple way of grabbing a version, but you should also be able to use any commit hash from master (https://chromium.googlesource.com/chromium/src/+/master) as long as it's trailing by a few hours (our uploader has a delay).

Can you describe what your end goal is here?

- Will 

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/c86104bb-fd58-4669-83c7-0e593dda6c37%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[lan...@vewd.com]

Thanks a lot for the information. The end goal is essentially to give easy to follow instructions to users of our chromium base product on how to get a working frontend for the client they are using. I think I have all the information I need now.

/David