[haiku-commits] Re: haiku: hrev46704 - build/jam
- From: Matt Madia <mattmadia@xxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Sat, 18 Jan 2014 15:48:56 -0500
On 1/18/14, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> On 01/18/2014 08:45 PM, Matt Madia wrote:
>> On Jan 18, 2014 10:09 AM, <ingo_weinhold@xxxxxx> wrote:
>>> 495b360: Add support for explicitly preventing rebuilding packages
>>> The respective
>>> build
>>> order should be:
>>>
>>> 1. Build repository.
>>> 2. Without cleaning the generated directory, build different image
>>> types
>>> with HAIKU_DONT_REBUILD_PACKAGES defined.
>>
>> Hrmm, the nightly images are built completely independent of buildbot. I
>> really don't plan on moving that functionality into buildbot.
>
> My understanding of that infrastructure is a bit fuzzy. How are the
> nightlies built and how is the repository built?
The nightlies are built by a simple bash script, regulated by cron. It
is an all-or-nothing operation that depends on x86_gcc2, x86 and
x86_64 to be built properly. No repositories are uploaded from this
script.
Buildbot will create and upload the repositories as part of the
x86_gcc2, x86, and x86_64 compilation-test builds.
At the time it was set up, I thought it was better to have
repositories for as many revisions as possible (as opposed to just one
per successful nightly image).
One of my concerns with having the nightly upload as part of Buildbot
is that anyone with web access would be able to trigger a build for
the nightly images. (Learning more of Buildbot's functionality is on
the perpetual TODO list.)
--mmadia
Other related posts:
