Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of omuppi1@gmail.com designates
 74.125.82.175 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
In-Reply-To: 
 <CACK5iZd1mwsuaUQm2wPUCLzksRGr-ZumBvFmivJjCeHxptmqiQ@mail.gmail.com>
References: <CCEE37B2.49ED0%aharui@adobe.com>
 <CCEE399A.49ED7%aharui@adobe.com>
 <CACK5iZd1mwsuaUQm2wPUCLzksRGr-ZumBvFmivJjCeHxptmqiQ@mail.gmail.com>
From: Om <bigosmallm@gmail.com>
Date: Wed, 12 Dec 2012 20:22:41 -0800
Message-ID: 
 <CACK5iZfmrq9j-LQgTorf5tNCcdkBWCpf5t3hx61ZoAu09px2Rw@mail.gmail.com>
Subject: Re: Release target and Jenekins
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=90e6ba211f07ddfe4304d0b44558

--90e6ba211f07ddfe4304d0b44558
Content-Type: text/plain; charset=ISO-8859-1

Okay, here is the problem.

sdk/build.xml -checkintests calls sdk/mustella/makemustella.swc before it
can run the tests.  In order to make the mustella.swc, the flex sdk should
be built first.  Right now, it is not and hence mustella.swc cannot be
built.

I am testing a fix on my local jenkins that builds the sdk before calling
checkintests.

The other option is to modify the Flex_SDK_Build job to run checkintests
after building.

Which would be preferable?


On Wed, Dec 12, 2012 at 2:28 PM, Om <bigosmallm@gmail.com> wrote:

> Good news.  I ran the same job locally on my instance of Jenkins and I am
> getting the same exact error .  Will debug it on my machine by this
> evening.
>
> Thanks,
> Om
>
>
> On Wed, Dec 12, 2012 at 1:39 PM, Alex Harui <aharui@adobe.com> wrote:
>
>> BTW, the flashplayer trust folder might be in
>> %systemroot%\syswow64\macromed
>>
>>
>>
>> On 12/12/12 1:31 PM, "Alex Harui" <aharui@adobe.com> wrote:
>>
>> >
>> >
>> >
>> > On 12/12/12 1:23 PM, "Justin Mclean" <justin@classsoftware.com> wrote:
>> >
>> >> Hi,
>> >>
>> >>> {sdk_folder}/build.xml - checkintests task
>> >> I'd give that a go first, but either is probably fine. Any automated
>> testing
>> >> we have is far better than none.
>> > Yes, the one from the top level build.xml.  It might call into
>> sub-folder
>> > targets, but the true test is getting it to work from the top-level.
>> >>
>> >> Thanks,
>> >> Justin
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>

--90e6ba211f07ddfe4304d0b44558--