mirror of
https://github.com/flatcar/scripts.git
synced 2025-09-24 15:11:19 +02:00
ed210b40ff
Have subsequent review for cbuildbot that calls this for the pfq. This module has 3 modes ... TOT, latest_release, sticky_release that describe the three different types of revs for chrome we will be supporting. For tot, we grab the latest svn revision # from the chrome src tree, and rev to the corresponding ebuild i.e. 9.0.553.0_alpha-r1 with CROS_SVN_COMMIT=svn revision number. For latest_release, we grab the latest release from the releases page, and create an ebuild (or rev a previously existing on with same version) and use the release candidate suffix _rc. For sticky_release, we use much of the same logic as latest_release, however, we specifically look to rev _rc's in the sticky branch. This change depends on http://codereview.chromium.org/5172003 for the cros_mark_as_stable changes. Change-Id: Idc1f4cd905cc1dcb4c44422f6104760077a24b8d BUG=chromium-os:8693 TEST=Ran cros_mark_as_stable with --packages="chromeos-base/chromeos-chrome" --chrome_version=0.8.65.0 --chrome_revision=67890 commit. Re-ran unit-tests as well (though thinking about adding another unit test for chrome revving) Review URL: http://codereview.chromium.org/4798001
Symbolic link
1 line
29 B
Plaintext
Symbolic link
1 line
29 B
Plaintext
cros_mark_chrome_as_stable.py |