Linaro Android Frontend

Merge lp://qastaging/~pfalcon/linaro-android-frontend/no-weekend-builds into lp://qastaging/linaro-android-frontend

  1. no-weekend-builds
  2. Merge into trunk
Proposed by Paul Sokolovsky
Status: Merged
Approved by: Deepti B. Kalakeri
Approved revision: 270
Merged at revision: 270
Proposed branch: lp://qastaging/~pfalcon/linaro-android-frontend/no-weekend-builds
Merge into: lp://qastaging/linaro-android-frontend
Diff against target: 11 lines (+1/-1)
1 file modified
android_build/frontend/api.py (+1/-1)
To merge this branch: bzr merge lp://qastaging/~pfalcon/linaro-android-frontend/no-weekend-builds
Reviewer Review Type Date Requested Status
Deepti B. Kalakeri (community) Approve
Review via email: mp+104707@code.qastaging.launchpad.net

Description of the change

Per https://blueprints.launchpad.net/linaro-android-infrastructure/+spec/optimize-ec2-usage , don't do daily builds on weekend (Saturdays), as EC2 usage optimization.

To post a comment you must log in.
Revision history for this message
James Tunnicliffe (dooferlad) wrote :

On 4 May 2012 11:09, Paul Sokolovsky <email address hidden> wrote:
> Paul Sokolovsky has proposed merging lp:~pfalcon/linaro-android-frontend/no-weekend-builds into lp:linaro-android-frontend.
>
> Requested reviews:
>  Linaro Infrastructure (linaro-infrastructure)
>
> For more details, see:
> https://code.launchpad.net/~pfalcon/linaro-android-frontend/no-weekend-builds/+merge/104707

Wouldn't this be a problem for people working a weekend to get an
important feature done? I assume that we don't re-test revisions that
have already been tested, so if nobody is checking in, there shouldn't
be any new builds anyway.

--
James Tunnicliffe

Revision history for this message
Deepti B. Kalakeri (deeptik) wrote :

+1.

review: Approve
Revision history for this message
Paul Sokolovsky (pfalcon) wrote :

>Wouldn't this be a problem for people working a weekend to get an
important feature done?

No, they can rebuild it explicitly any time.

> I assume that we don't re-test revisions that
have already been tested, so if nobody is checking in, there shouldn't
be any new builds anyway.

No, we build by cron schedule, so we spend lot of cycles needlessly and need to optimize that by all means.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches