Complete session on how to set up a continuous integration server for compiling and deploying Flex, Flash and AIR applications. The build process also include code quality check, code duplication check, compiler warning reporting, TODO and FIXME list reporting, and Unit testing.

1. Build Automation of Flash, Flex, and AIR apps Vipin Chandran Project Manager – Impelsys India http://twitter.com/flashchemist http://blog.flashchemist.com

3. Identify these?

4. Run – Builds a swf movie with debug information Debug – Run the swf in Debug Perspective Profiler – Run the swf in Profiler Perspective

5. Export Release Build What you do when you release a Flex/AIR application?

8. Change Config (A) Compile Copy, rename, upload etc. Change Config (B) Compile Copy, rename, upload etc. While development For Release

9. Build Automation or Release Engineering “ Release engineering is to software engineering as manufacturing is to an industrial process” “ It is often seen as a sign of organizational and developmental maturity”

11. On-Demand automation Simple command line Apache ANT Scripting languages like PERL, Python, PHP etc.. [DEMO] [DEMO -2] [DEMO]

12. Scheduled and Triggered automation Continuous Integration Server running scheduled builds (nightly build) Continuous Integration Server running build on every svn commit (any kind of trigger)

13. What is Continuous Integration Server? Build runs here... Source code repository. (SVN, CVS etc.) Individual developers commit the code to this server Notify

14. Continuous Integration is a software development practice where members of a team integrate their work frequently, leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. What is Continuous Integration Server?

16. What it will do? Pre compile tasks – Configuration settings, environment settings, checkout code from repos, copy or create certain files Compilation Post compilation tasks - Testing, Code quality analysis Documentation, Build deployment etc.. Single Process

17. Few examples Hudson CI

18. Cruise Control Few examples

19. Demo of a sample Hudson Job

20. Tools used for this job MXMLC COMPC Compilers ADT AIR Packager Flex SDK FlexPMD FlexCPD FlexUnit Open source tools from Adobe

21. Reports generated by Hudson

22. Cons Initial setup time required. well-developed test-suite required to achieve automated testing advantages large-scale refactoring can be troublesome due to continuously changing code base hardware costs for build machines can be significant

23. Questions?? twitter.com/flashchemist http://blog.flashchemist.com