BuildRelease Tool is flaky.

[GoogleCodeExporter]

When producing the last build I found the BuildRelease very flaky. Improve 
stability of BuildRelease.

Examples.
Does not work if there have not been any changes to any of the repos.
Is not re-runable on any given day.
First run of the day takes hours due to fresh fetch of all repos, this should 
be able to reuse repos.

Original issue reported on code.google.com by davidwat...@google.com on 4 Sep 2012 at 9:11

[GoogleCodeExporter]

I'll handle this one.

Original comment by davidwat...@google.com on 12 Sep 2012 at 10:28

• Changed state: Accepted

[GoogleCodeExporter]

I have addressed two of these issues so far, but I'm not happy yet so I will 
not close this issue. 

>Does not work if there have not been any changes to any of the repos.
Fixed.

>Is not re-runable on any given day.
Fixed.

>First run of the day takes hours due to fresh fetch of all repos, this should 
be able to reuse repos.
No work done yet.

I will take ownership again if I start working on this again.

Original comment by davidwat...@google.com on 13 Sep 2012 at 10:18

[GoogleCodeExporter]

Some notes on how to improve this.

Check that repositories have no outstanding modifications at the start of the 
process not the end (or both start and end).

The are you sure prompt currently only accepts "YES" if anything else is 
entered it exits. This should loop  while(commandline.prompt not in 
[YES,cancel]){;}

Loop over errors commiting to each repo

while(true) {
  try{
   repo.commit()
   break;
  } catch {
   if(commandline.prompt() == cancel)
     break;
  }
}

Original comment by davidwat...@google.com on 6 Dec 2012 at 3:24

[GoogleCodeExporter]

Old issue the Release Builder was changed significantly and doesn't contain 
this problem any more. 

Original comment by pele...@google.com on 28 Nov 2013 at 5:51

[GoogleCodeExporter]

Original comment by pele...@google.com on 28 Nov 2013 at 5:51

• Changed state: WontFix