On Tuesday, August 14, 2012, Alex Harui wrote: > > > > On 8/14/12 6:43 PM, "Justin Mclean" <jus...@classsoftware.com<javascript:;>> > wrote: > > > Hi, > > > > Just as an aside I did try to get the check in tests to work with > Jenkins but > > had no luck. If someone else want to give it a go: > > https://builds.apache.org/job/Flex_SDK_checkin_tests/ > > > > Currently the build is triggered once/hour after a checkin and at a > minimum of > > once/day. > > https://builds.apache.org/job/Flex_SDK_build/ > > > > (There's been 141 builds!) > > > > Currently infrastructure only has one windows box to run the build/tests > on, > > this box is not 100% reliable and has a reasonable load on it I can't > see it > > being used to run the full Mustella tests all at once, but perhaps we > could > > have multiple jobs that run each component/area once/day rather than > > once/check in? > > > > Thanks, > > Justin > > > I don't know anything about Jenkins. Is there any way to grab the > flashlog.txt when checkintests fails? > > It looks like it hung. Could be that trust files need to be set up to > allow > loading of images. > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui
You can add a build step to Jenkins that copies flashlog.txt to some location after each build, concatenate the date to the name and we can have it for us to inspect. You can set that up with ANT and we can add an ant target as a build step, or u can just add a shell script as a build step. -omar
