Date
1 - 4 of 4
Changes to the autobuilder.
Flanagan, Elizabeth <elizabeth.flanagan@...>
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.
-b
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.
-b
Xu, Jiajun <jiajun.xu@...>
I've made a few changes to the autobuilder that people should know about.Hi Beth,
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.
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.
-bBest Regards,
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
Jiajun
Elizabeth Flanagan <elizabeth.flanagan@...>
I see that and I think I know what is going on. I should have a fix for
this today.
-b
toggle quoted message
Show quoted text
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.Hi Beth,
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.
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.-bBest Regards,
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
Jiajun
Elizabeth Flanagan <elizabeth.flanagan@...>
The answer to this, is that the nightly-*-incrementals were copying
their output to the webserver nightly (which updated CURRENT). As there
was a change to the incrementals on Friday that broke kernel deploy, the
kernel didn't get copied. That is now fixed.
You should look at: http://autobuilder.pokylinux.org/nightly/20110107-1
as this is the actual nightly. I'm fixing the incrementals right now, so
that they won't copy over their output and so they do a bitbake
virtual/kernel -f -c deploy, which will fix the incremental sanity test
breakage.
-b
That is corrected.
toggle quoted message
Show quoted text
their output to the webserver nightly (which updated CURRENT). As there
was a change to the incrementals on Friday that broke kernel deploy, the
kernel didn't get copied. That is now fixed.
You should look at: http://autobuilder.pokylinux.org/nightly/20110107-1
as this is the actual nightly. I'm fixing the incrementals right now, so
that they won't copy over their output and so they do a bitbake
virtual/kernel -f -c deploy, which will fix the incremental sanity test
breakage.
-b
That is corrected.
On 01/10/2011 09:27 AM, Elizabeth Flanagan wrote:
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.Hi Beth,
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.
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.-bBest Regards,
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto
Jiajun
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto