Autobuilder changes and Milestone2

Autobuilder changes and Milestone2

[Flanagan, Elizabeth]

All,

This morning I stopped the autobuilder and fixed a few scripts that caused our first milestone build to not generate a source release tarball. I also removed a few unneeded sdk targets from milestone-internal and fixed the CURRENT linking issue. I'll have these all packaged up and ready to pull into the poky-autobuilder repo next week but I wanted to go through the changes before I left for the weekend (so I don't forget what I did :) )

The first change was with poky-autobuild-generate-sources-tarball. The tarball generation failed due to git trying to archive a hardcoded branch (master). This script now takes an optional third arg of $BRANCH. If the third arg isn't set, it defaults to 'master'. This should fix the source tarball generation. 

The second change was to poky-autobuild-generate-release. This script now takes an optional third arg of 'current', which causes it to just create a CURRENT symlink to the latest release directory. I want to remove this functionality from this script as issuing a 'current' doesn't actually generate a release and the functionality should be extracted and put in it's own script. It was just a convenient place to put it for now.

I also removed all the non-IA arch  sdk builds from milestone-internal. Building these happens on milestone-external and is not needed.

M2 build 2 is now running and judging from the last build, milestone-external should be done around 12 noon PST tomorrow and milestone-internal finished around 8am PST.

If you have any questions or concerns, I'll be checking email intermittently this weekend.

-b

Re: Autobuilder changes and Milestone2

[Zhang, Jessica]

[-- Attachment #1: Type: text/plain, Size: 276 bytes --]

 

I also removed all the non-IA arch  sdk builds from milestone-internal.
Building these happens on milestone-external and is not needed.

Beth, so all the non-IA arch sdk will be built for M2 but just will be built
on milestone-external, right?

Thanks,
Jessica


[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 8455 bytes --]

Re: Autobuilder changes and Milestone2

[Flanagan, Elizabeth]

That is correct. 

-b
________________________________________
From: Zhang, Jessica
Sent: Saturday, December 18, 2010 12:35 PM
To: Flanagan, Elizabeth; yocto@yoctoproject.org
Subject: RE: Autobuilder changes and Milestone2

I also removed all the non-IA arch  sdk builds from milestone-internal.
Building these happens on milestone-external and is not needed.

Beth, so all the non-IA arch sdk will be built for M2 but just will be built
on milestone-external, right?

Thanks,
Jessica

Re: Autobuilder changes and Milestone2

[Saul Wold]

On 12/18/2010 10:14 AM, Flanagan, Elizabeth wrote:
> All,
>
> This morning I stopped the autobuilder and fixed a few scripts that caused our first milestone build to not generate a source release tarball. I also removed a few unneeded sdk targets from milestone-internal and fixed the CURRENT linking issue. I'll have these all packaged up and ready to pull into the poky-autobuilder repo next week but I wanted to go through the changes before I left for the weekend (so I don't forget what I did :) )
>
> The first change was with poky-autobuild-generate-sources-tarball. The tarball generation failed due to git trying to archive a hardcoded branch (master). This script now takes an optional third arg of $BRANCH. If the third arg isn't set, it defaults to 'master'. This should fix the source tarball generation.
>
> The second change was to poky-autobuild-generate-release. This script now takes an optional third arg of 'current', which causes it to just create a CURRENT symlink to the latest release directory. I want to remove this functionality from this script as issuing a 'current' doesn't actually generate a release and the functionality should be extracted and put in it's own script. It was just a convenient place to put it for now.
>
> I also removed all the non-IA arch  sdk builds from milestone-internal. Building these happens on milestone-external and is not needed.
>
> M2 build 2 is now running and judging from the last build, milestone-external should be done around 12 noon PST tomorrow and milestone-internal finished around 8am PST.
>
> If you have any questions or concerns, I'll be checking email intermittently this weekend.
>
> -b
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
Beth,

Thanks for getting this kicked off over the weekend.

Sau!