Finding revisions for archived prebuilts / bisect-builds

[Jesse Gunsch]

I'm trying to understand archived build revisions since the SVN-->Git migration, both for bisect-builds.py and browsing archived builds [1]. The bisect-builds.py docs [2] don't provide much insight.

How would I best find, for example, the revision of the Chrome 41 release to use for pulling down archived prebuilts?

[1] http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html

[2] https://www.chromium.org/developers/bisect-builds-py

[Paweł Hajdan, Jr.]

+infra-dev

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Rob Wu]

I think that builds are archived as follows:

- svn: by revision number

- svn-git migration: by git hash (for a few days/weeks)

- git: by commit position

If you have a specific version number, just use the "Position lookup" box at https://omahaproxy.appspot.com/ to get the svn revision/position number for the given Chrome version.

If you want to page through all revisions in order, then you have to fetch all revisions, use git to find the commit position from the logs for the given hashes, and sort the result. This is what bisect-builds.py does. And if you cache the full list of changes, then subsequent updates only need to start paging starting at the last known revision, which significantly decreases the time needed to find a revision. This logic was added to bisect-builds.py in https://chromium.googlesource.com/chromium/src/+/724c9069b207b3578d59e7e6662c35e02a01e961%5E%21/.

Kind regards,

 Rob

 https://robwu.nl

+infra-dev

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.