Add chrome revving module to crosutils

Add new chrome revving module to crosutils.

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)

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=ed210b4

[sosa, 2010-11-17 21:25:51]

If you're interested, this is getting close.  There is an issue with the EBuild
class I'm fixing for the "latest release" case but i thought you guys might
wanna take a first look.

[sosa, 2010-11-18 00:48:41]

PTAL

I have removed the cros_mark changes and put them in another CL and updated the
CL issue description appropriately with what this is supposed to do.

I am writing unit tests as we speak but I have tested each of the modes with the
current tree and have gone through gpylint etc to clean this code up for review.

[Chris Masone, 2010-11-18 02:23:07]

http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
File bin/cros_mark_chrome_as_stable.py (right):

http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
bin/cros_mark_chrome_as_stable.py:21: BASE_CHROME_SVN_URL =
'http://src.chromium.org/svn'
This is only for the public source.  That doesn't matter, though, right?

http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
bin/cros_mark_chrome_as_stable.py:55: return line.split(':')[1].strip()
I'm sad that we can't figure out a better way to do this :-/

[Mandeep Singh Baines, 2010-11-18 04:11:47]

http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
File bin/cros_mark_chrome_as_stable.py (right):

http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
bin/cros_mark_chrome_as_stable.py:55: return line.split(':')[1].strip()
On 2010/11/18 02:23:07, Chris Masone wrote:
> I'm sad that we can't figure out a better way to do this :-/

I've been archiving these emails for a while now but I have a filter which
routes any emails with the word sad directly to my inbox;)

How about:

re.search('\nRevision: (\d*)', svn_info).groups()[0]

Or if you want to get really fancy you could use 'svn info --xml' and use one of
python's xml parsing libraries.

[Mandeep Singh Baines, 2010-11-18 04:16:25]

On 2010/11/18 04:11:47, Mandeep Singh Baines wrote:
>
http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
> File bin/cros_mark_chrome_as_stable.py (right):
> 
>
http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
> bin/cros_mark_chrome_as_stable.py:55: return line.split(':')[1].strip()
> On 2010/11/18 02:23:07, Chris Masone wrote:
> > I'm sad that we can't figure out a better way to do this :-/
> 
> I've been archiving these emails for a while now but I have a filter which
> routes any emails with the word sad directly to my inbox;)
> 
> How about:
> 
> re.search('\nRevision: (\d*)', svn_info).groups()[0]
> 

This could actually be simplified to:

re.search('\nRevision: (\d*)', svn_info).group(1)

> Or if you want to get really fancy you could use 'svn info --xml' and use one
of
> python's xml parsing libraries.

[Mandeep Singh Baines, 2010-11-18 04:44:13]

Even better:

$ man 1 svnversion

$ svnversion
66511

msb@chromium.org (msb@chromium.org) wrote:
> On 2010/11/18 04:11:47, Mandeep Singh Baines wrote:
> 
>
http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
> >File bin/cros_mark_chrome_as_stable.py (right):
> 
> 
>
http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
> >bin/cros_mark_chrome_as_stable.py:55: return line.split(':')[1].strip()
> >On 2010/11/18 02:23:07, Chris Masone wrote:
> >> I'm sad that we can't figure out a better way to do this :-/
> 
> >I've been archiving these emails for a while now but I have a filter which
> >routes any emails with the word sad directly to my inbox;)
> 
> >How about:
> 
> >re.search('\nRevision: (\d*)', svn_info).groups()[0]
> 
> 
> This could actually be simplified to:
> 
> re.search('\nRevision: (\d*)', svn_info).group(1)
> 
> >Or if you want to get really fancy you could use 'svn info --xml'
> >and use one
> of
> >python's xml parsing libraries.
> 
> 
> 
> http://codereview.chromium.org/4798001/

[Chris Masone, 2010-11-18 17:31:02]

On 2010/11/18 04:44:13, Mandeep Singh Baines wrote:
> Even better:
> 
> $ man 1 svnversion
> 
> $ svnversion
> 66511
> 

The problem is that we aren't guaranteed to have a checkout in which to run
svnversion.  I haven't managed to figure out how to run it and point it at the
remote repo :-/  If one can, that'd be perfect.

> mailto:msb@chromium.org (mailto:msb@chromium.org) wrote:
> > On 2010/11/18 04:11:47, Mandeep Singh Baines wrote:
> > 
> >
>
http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
> > >File bin/cros_mark_chrome_as_stable.py (right):
> > 
> > 
> >
>
http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
> > >bin/cros_mark_chrome_as_stable.py:55: return line.split(':')[1].strip()
> > >On 2010/11/18 02:23:07, Chris Masone wrote:
> > >> I'm sad that we can't figure out a better way to do this :-/
> > 
> > >I've been archiving these emails for a while now but I have a filter which
> > >routes any emails with the word sad directly to my inbox;)
> > 
> > >How about:
> > 
> > >re.search('\nRevision: (\d*)', svn_info).groups()[0]
> > 
> > 
> > This could actually be simplified to:
> > 
> > re.search('\nRevision: (\d*)', svn_info).group(1)
> > 
> > >Or if you want to get really fancy you could use 'svn info --xml'
> > >and use one
> > of
> > >python's xml parsing libraries.
> > 
> > 
> > 
> > http://codereview.chromium.org/4798001/

[Mandeep Singh Baines, 2010-11-18 17:42:21]

cmasone@chromium.org (cmasone@chromium.org) wrote:
> On 2010/11/18 04:44:13, Mandeep Singh Baines wrote:
> >Even better:
> 
> >$ man 1 svnversion
> 
> >$ svnversion
> >66511
> 
> 
> The problem is that we aren't guaranteed to have a checkout in which to run
> svnversion.  I haven't managed to figure out how to run it and point
> it at the
> remote repo :-/  If one can, that'd be perfect.
> 

The docs are confusing but it appears that svnversion only works with
the working copy:

http://stackoverflow.com/questions/623378/get-revision-number-of-a-remote-rep...

> >mailto:msb@chromium.org (mailto:msb@chromium.org) wrote:
> >> On 2010/11/18 04:11:47, Mandeep Singh Baines wrote:
> >>
> >>
> 
>
http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
> >> >File bin/cros_mark_chrome_as_stable.py (right):
> >>
> >>
> >>
> 
>
http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
> >> >bin/cros_mark_chrome_as_stable.py:55: return line.split(':')[1].strip()
> >> >On 2010/11/18 02:23:07, Chris Masone wrote:
> >> >> I'm sad that we can't figure out a better way to do this :-/
> >>
> >> >I've been archiving these emails for a while now but I have a
> >filter which
> >> >routes any emails with the word sad directly to my inbox;)
> >>
> >> >How about:
> >>
> >> >re.search('\nRevision: (\d*)', svn_info).groups()[0]
> >>
> >>
> >> This could actually be simplified to:
> >>
> >> re.search('\nRevision: (\d*)', svn_info).group(1)
> >>
> >> >Or if you want to get really fancy you could use 'svn info --xml'
> >> >and use one
> >> of
> >> >python's xml parsing libraries.
> >>
> >>
> >>
> >> http://codereview.chromium.org/4798001/
> 
> 
> 
> http://codereview.chromium.org/4798001/

[sosa, 2010-11-18 18:33:41]

Yeah I looked at using svnversion before doing the svn info work.  The
consensus of my google searching was that svnversion could only be
used locally and well, that just won't really work for our use case at
the moment.  I think I'll take msb's first suggestion with the regex
as that looked good.

On Thu, Nov 18, 2010 at 9:42 AM, Mandeep Singh Baines <msb@chromium.org> wrote:
> cmasone@chromium.org (cmasone@chromium.org) wrote:
>> On 2010/11/18 04:44:13, Mandeep Singh Baines wrote:
>> >Even better:
>>
>> >$ man 1 svnversion
>>
>> >$ svnversion
>> >66511
>>
>>
>> The problem is that we aren't guaranteed to have a checkout in which to run
>> svnversion.  I haven't managed to figure out how to run it and point
>> it at the
>> remote repo :-/  If one can, that'd be perfect.
>>
>
> The docs are confusing but it appears that svnversion only works with
> the working copy:
>
>
http://stackoverflow.com/questions/623378/get-revision-number-of-a-remote-rep...
>
>> >mailto:msb@chromium.org (mailto:msb@chromium.org) wrote:
>> >> On 2010/11/18 04:11:47, Mandeep Singh Baines wrote:
>> >>
>> >>
>>
>>
http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
>> >> >File bin/cros_mark_chrome_as_stable.py (right):
>> >>
>> >>
>> >>
>>
>>
http://codereview.chromium.org/4798001/diff/14001/bin/cros_mark_chrome_as_sta...
>> >> >bin/cros_mark_chrome_as_stable.py:55: return line.split(':')[1].strip()
>> >> >On 2010/11/18 02:23:07, Chris Masone wrote:
>> >> >> I'm sad that we can't figure out a better way to do this :-/
>> >>
>> >> >I've been archiving these emails for a while now but I have a
>> >filter which
>> >> >routes any emails with the word sad directly to my inbox;)
>> >>
>> >> >How about:
>> >>
>> >> >re.search('\nRevision: (\d*)', svn_info).groups()[0]
>> >>
>> >>
>> >> This could actually be simplified to:
>> >>
>> >> re.search('\nRevision: (\d*)', svn_info).group(1)
>> >>
>> >> >Or if you want to get really fancy you could use 'svn info --xml'
>> >> >and use one
>> >> of
>> >> >python's xml parsing libraries.
>> >>
>> >>
>> >>
>> >> http://codereview.chromium.org/4798001/
>>
>>
>>
>> http://codereview.chromium.org/4798001/
>

[sosa, 2010-11-19 16:45:57]

PTAL.  Addressed svn revision and added unit tests.

[Chris Masone, 2010-11-19 18:48:59]

lgtm