Thanks Alex. So IIUC,
1) create new folder "pixel_bender" under https://dist.apache.org/repos/dist/dev/flex/ SVN repo - will contain the zip files generated by the build below 2) add new project " flex-sdk_pixelbender" in "flex-utilities" GIT repo containing: - PBK sources for flex-sdk - build file for compiling pbk into pbj Output = pb.zip file containing pbj + pbk (similar structure to current pixelbender upstream Jenkins job) [Bonus] auto-commmit the zip file to dist/.../pixel_bender => build file must be run manually by "Release manager" 3) remove flex-sdk_pixelbender upstream job from b.a.o Jenkins (obsolete) 4) to include pbk+pbj in Flex SDK release there are two options a) modify build_release.sh (or equivalent) to checkout pb.zip from svn and unzip into dist b) add checkout+checkMD5+unzip step in flex sdk installer Is that correct? What option in 4) I think a) is the easiest, and it does not break any Apache rule. Maurice -----Message d'origine----- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : jeudi 12 décembre 2013 15:40 À : dev@flex.apache.org Objet : Re: PixelBender and Builds.a.o On 12/12/13 5:03 AM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote: >I am trying to understand the steps below: > >Where would the pbk => pbj compilation take place ? In the build script for this "project". > >Where would the pbj be stored after the build , if the build does not >occur on the CI? On the same servers we store our voted on releases. >Will the pbj be compiled by Jenkins ? or built manually and stored >somewhere ? All releases are compiled by someone running the build script and signing the artifacts. Apache even seems to not want to allow signing of Jenkins-built artifacts. -Alex
