PkgForge-Registry

 view release on metacpan or  search on metacpan

doc/index.html  view on Meta::CPAN


<h2>Builders</h2>

<p>
  In the Package Forge Registry a uniquely named <em>builder</em>
  entry should exist for each build daemon. Typically, it is expected
  that there will be one builder per platform but there are no
  limits. It may well be that there is a period during which there are
  no builders and new tasks will just be queued as long as the
  platform is active. It is also possible to register extra builders
  for a platform which can be used during busy times. Note that having
  a builder registered does not necessarily mean it will take new
  jobs. The builder has to have the necessary permissions to be able
  to talk to the registry database and request new jobs, that must be
  managed separately (normally via the LCFG postgresql component).
</p>

<p>
  When a builder takes on a new task the ID is stored into
  the <em>current</em> field and an entry is added into the <em>build
  log</em>. Note that in some circumstances a builder is allowed to



( run in 1.478 second using v1.01-cache-2.11-cpan-3cd7ad12f66 )