linaro-release team mailing list archive

[Paul Sokolovsky <744648@xxxxxxxxxxxxxxxxxx>]

We seem to doing well now, lowering priority.


** Changed in: linaro-android-build-tools
   Importance: High => Medium

-- 
You received this bug notification because you are a member of linaro-
infrastructure-drivers, which is the registrant for Linaro Android Build
Tools.
https://bugs.launchpad.net/bugs/744648

Title:
  linaro-cloud-buildd: current setup does not scale slave nodes

Status in Linaro Android Build Tools:
  New

Bug description:
  Waiting for an experimental build to start, I looked at the jenkins
  interface and saw five builds being queued up.

  My understanding was that in design we fire off an instance for each
  build and then shut it down (so not pooling, recycling) etc. And that
  we would set a cap of slaves.

  I remember I saw IRC discussion on this and that there is a work in
  progress to better identifying the slave instances in the cloud to
  better enforce a proper cap.

  Please use this bug to document the current status, and then track
  progress on this issue.

  A solution to get more build throughput and unleash the powers of
  cloud computing would be highly desirable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-android-build-tools/+bug/744648/+subscriptions