Common' ... JS ... seriously? What exactly would you be expecting from a CI build for a JS project? Of course they aren't mainly thinking of CI builds ... I'm talking about normal Software development. Every customer I work for uses CI servers to ensure the quality of their software.
I actually want to use it to make sure everything builds correctly, automatically produce up to date maven snapshots of the parts that belong to us and in general untangle the inter dependencies in our build. I am used to working with complex builds and if I am having trouble working out our current one, I bet most people wanting to contribute will be having at least the same trouble. Most of them probably giving up. I want to change that. I want to lower the barrier for new contributions and the main thing we need to address here is the build. Currently it feels as if only 2-3 people are contributing to FlexJS as all ... I bet this could be a lot more, if we reached out to the others. I know that you guys, sort of working on this full time, don't see the problem, but at Apache it's "community over code", so we have to get the community involved again. Chris ________________________________________ Von: Tom Chiverton <t...@extravision.com> Gesendet: Freitag, 2. Oktober 2015 11:13 An: dev@flex.apache.org Betreff: Re: Test Failures when building flex-falcon On 02/10/15 09:50, Justin Mclean wrote: > Just about everyone who produces software uses continues integration *At a certain level*. There are *a lot* of people building small to medium apps that don't want to take on the overhead and don't need the reassurance; more so in agencies where after a month (or days!) the project is done and unchanging. It's under half at our local monthly JS meeting who do CI (and we have a broad mix from the one excellent man, through the 10-30 people SME's and on to AutoTrader). If you are producing a framework though, like we are, then CI is a must because people are trusting us to not break. Tom
