Probably because no one has done it.
I don't so much how things are organized at asf for those things, may
someone can basicly enlight me and / or direct me on the good documention.
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.
If it's done only once a day, how to link a failed build with a particular
commit ?
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.
Yes it's more complicated for the test suite as it takes so much time, but
as the last point, doing it once a week, we can't link a failed test with a
particular commit.
Finally, for the test suite may be for those technical reasons, it still
better for each committer run the test suite by himself for each commit as I
guess it happens today.
- Fred.
-----Message d'origine-----
From: Carol Frampton
Sent: Friday, December 07, 2012 7:43 PM
To: flex-dev@incubator.apache.org
Subject: Re: Release build - another TLF issue
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
