All of lore.kernel.org
 help / color / mirror / Atom feed
From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Changes to the autobuilder.
Date: Wed, 12 Jan 2011 16:10:57 -0800	[thread overview]
Message-ID: <4D2E4311.6070800@intel.com> (raw)
In-Reply-To: <4D2E3E15.2070305@linux.intel.com>

On 01/12/2011 03:49 PM, Darren Hart wrote:
> On 01/08/2011 03:21 PM, Flanagan, Elizabeth wrote:
>> I've made a few changes to the autobuilder that people should know
>> about. Currently, we've been utilizing the milestone builders to split
>> the nightly to both the internal and external builders in order to
>> speed things up. I've renamed them to nightly-internal* and
>> nightly-external*. They were putting their build output to the
>> milestone directory on the webserver. This was incorrect behavior.
>> I've changed this to make the build output go out to the nightly
>> directory of the webserver: http://autobuilder.pokylinux.org/nightly.
>>
>> The big change is to how we deal with emenlow, atom-pc, beagleboard,
>> etc. These are now found under the machines/<machine_name>/<arch>
> 
> once you've descended into machine_name, "arch" seems superfluous. Won't
> it be the only directory? Would it make more sense as:
> 
> machines/arch/machine_name ?
> 
> machines
>    x86
>      qemux86
>      atom-pc
>    x86_64
>      qemux86-64
>    arm
>      beagleboard
>      beagleboard_xm
> 
> Something like that?
> 

I agree, it does seem odd, but since there was a standard already in
place (for historical reasons, I'm sure) with emenlow and atom-pc of
<machine>/<arch>/ I wanted to make sure I didn't mess up anyone's
expectations of where they should find something. I agree though, your
directory structure makes more sense we can and should definitely
revisit it. I just wanted to get the new boards out of /qemu.

-b

> --
> Darren
> 
>> directory in the build output web directory. I'll need to eventually
>> refactor some of the autobuilder scripts to deal with BSPs a little
>> more elegantly, but it's functional for now and we have a standard to
>> adhere to.
>>
>> Also, be aware that we now have a functional CURRENT link, so if you
>> go to the autobuilder/nightly/CURRENT directory this will point to the
>> last thing the autobuilder built. Keep in mind, it will create that
>> link even if the build is broken.  I'll have a commit with all of this
>> in it when I finish up the upgrade to 0.8.3.
>>
>> If you have any questions, feel free to ask.
>>
>> -b
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> 



  reply	other threads:[~2011-01-13  0:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08 23:21 Changes to the autobuilder Flanagan, Elizabeth
2011-01-12 23:49 ` Darren Hart
2011-01-13  0:10   ` Elizabeth Flanagan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-01-08 23:21 Flanagan, Elizabeth
2011-01-10  1:25 ` Xu, Jiajun
2011-01-10 17:27   ` Elizabeth Flanagan
2011-01-10 21:30     ` Elizabeth Flanagan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D2E4311.6070800@intel.com \
    --to=elizabeth.flanagan@intel.com \
    --cc=dvhart@linux.intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.