Hi Om,
Ok, I see, the addition of a socket server is a good idea (I guess you had
to change something in the suite to make you server be listened, hadn't you
?).
I'm pretty much doing the same thing[1] on my side except that I started the
from the other side, as I already explained, the goal for me, is a tool able
to allow the user to create a project based on the develop branch, choose
which version of AIR and FP and with wich options it will be compiled
against and then tested, I want to give the same possibilities that we've
got with the command line but graphically.
Basicly, the tool should download the sdk, execute all the things described
in the readme to setup (a bit like does the Installer too) and build the sdk
and the same for the tests with the options the user passed thru the UI.
I want the user able to mavenize the sdk too and later why not debug the
tests with FPD but graphicly.
- Fred.
[1]
http://svn.apache.org/viewvc/incubator/flex/whiteboard/fthomas/developerToolSuite/trunk/
-----Message d'origine-----
From: Om
Sent: Friday, December 07, 2012 8:14 PM
To: flex-dev@incubator.apache.org
Subject: OneClickMustella
Here is my work in progress:
https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/develop/mustella/utilities/OneClickMustella
So far, I have the directory paths inputs (persists across sessions)
working. The app also starts a server and will serve up assets from the
mustella/tests folder. This works fine with mini_run running from cygwin.
The next steps that I am planning on working on are:
1. Invoke mini_run via a nativeprocess from within the air app.
2. Bring in the code from MustellaDependencyDB and MustellaTestChooser and
integrate it with the app
3. Hook the app up to talk to SVN.
The final goal is to do all this with one button click:
1. Check changed files in the given sdk folder
2. Find corresponding tests to run
3. Run the said tests
4. Publish the test results.
Through all this, if we manage to make the AIR app run via commandline, we
can try to hook this up on the CI server.
I can think of more fancy features, but that can be done for the next
version.
Thanks,
Om
On Fri, Dec 7, 2012 at 11:03 AM, Frédéric THOMAS
<webdoubl...@hotmail.com>wrote:
Hi Om,
Is there a place where I can look at what you did already, it would be
nice ? (even if I won't have time tonight)
- Fred.
-----Message d'origine----- From: Om
Sent: Friday, December 07, 2012 7:49 PM
To: flex-dev@incubator.apache.org
Subject: Re: Release build - another TLF issue
I have started working on these two issues in an attempt to get to what
you
are talking about. If someone has time, they are welcome to help out.
FLEX-33266
<https://issues.apache.org/**jira/browse/FLEX-33266<https://issues.apache.org/jira/browse/FLEX-33266>
>
Make it easy for developers to do a targetted Mustella test run that
doesnt
take hours
<https://issues.apache.org/**jira/browse/FLEX-33266<https://issues.apache.org/jira/browse/FLEX-33266>
>
FLEX-33265
<https://issues.apache.org/**jira/browse/FLEX-33265<https://issues.apache.org/jira/browse/FLEX-33265>
>
Enable Mustella on CI server
(jenkins)<https://issues.**apache.org/jira/browse/FLEX-**33265<https://issues.apache.org/jira/browse/FLEX-33265>
>
Thanks,
Om
On Fri, Dec 7, 2012 at 10:43 AM, Carol Frampton <cfram...@adobe.com>
wrote:
On 12/7/12 1 :37PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:
>Hi,
>
>I don't know if it has been discussed already but what about having
>Jenkins
>jobs (for the main target and other.locales) at commit time, is it
>possible
>to set up our CI ?
Probably because no one has done it. I don't think a whole kit has to be
built for every checkin but once a day would be nice.
>(And for the tests it would be nice to have something too).
I'm not even sure the test can be run but if they can I think they take
way to long to run to be tied to checkins.
Carol
>
>Why it's not like that yet, has it been discusses already ?
>
>
>-Fred.
>
>-----Message d'origine-----
>From: Justin Mclean
>Sent: Friday, December 07, 2012 7:12 PM
>To: flex-dev@incubator.apache.org
>Subject: Re: Release build - another TLF issue
>
>OK think it would huge best if we set up a Jenkins job to run the
>release
>targets that way we hopefully know when there's an issue with the
>release
>build.
>
>Thanks,
>Justin
>
