From: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
To: "Xu, Jiajun" <jiajun.xu@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Changes to the autobuilder.
Date: Mon, 10 Jan 2011 09:27:12 -0800 [thread overview]
Message-ID: <4D2B4170.6080609@intel.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A31B0755D@shsmsx501.ccr.corp.intel.com>
I see that and I think I know what is going on. I should have a fix for
this today.
-b
On 01/09/2011 05:25 PM, Xu, Jiajun 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> 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.
>>
>
> Hi Beth,
> We found there is no kernel image for QEMU target with latest nightly, http://autobuilder.pokylinux.org/nightly/20110108-1/qemu/. Could you help to have a check? And nightly-internal does not start last week.
>
>> -b
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
> Best Regards,
> Jiajun
>
>
next prev parent reply other threads:[~2011-01-10 17:26 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-10 1:25 ` Xu, Jiajun
2011-01-10 17:27 ` Elizabeth Flanagan [this message]
2011-01-10 21:30 ` Elizabeth Flanagan
-- strict thread matches above, loose matches on Subject: below --
2011-01-08 23:21 Flanagan, Elizabeth
2011-01-12 23:49 ` Darren Hart
2011-01-13 0:10 ` 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=4D2B4170.6080609@intel.com \
--to=elizabeth.flanagan@intel.com \
--cc=jiajun.xu@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.