Arnaud Héritier, Apache Maven Evangelist and eXo Software Factory Manager is giving a quick overview of our software Factory. For more details read his blog post series on http://blog.exoplatform.com
2. • Software Factory Team
• Development rules and recommendations
• Methods and Tools
• To improve quality and productivity
• Teams training
• To improve ours skills
• Support & Accompaniment
• About tools, methods, processes, and technical
Software Factory Team
Friday, January 27, 12
3. • Development practices
• Unit tests, integration tests, functional
tests, web tests, performances tests
• Code quality
• Java/JEE & Production Architecture
• Development tools
• Build, Packaging, IDE ..
Skills Catalog
Friday, January 27, 12
4. • Documentations are in ours WIKIs
• http://wiki-int.exoplatform.org/display/
exoSoftwareFactory/Home
• Activity is tracked in Jira :
• http://jira.exoplatform.org/browse/SWF
• Contact us :
• Email : exo-swf@exoplatform.com
• Skype : aheritier
How are we working ?
Friday, January 27, 12
13. Nexus for
collaboration
Deploy 3rd Party Artifacts
Collaborate with Internal
Repositories
Distribute to the community with
Public Repositories
Distribute to customers with
Private Repositories
Friday, January 27, 12
20. Continuous
Integration
Build,Test and Deploy ASAP
Using Maven 2/3
From sources in SVN or GIT
googlecode, jboss, exo, github
repos
To Maven repositories
>100 jobs
Friday, January 27, 12
21. Packaging
Generate the full packaging of our
products
Ready for demo or tests
Use upstream constraints and a large
quiet period to not launch them to often
Use priority sorter plugin with a
reduced priority
~15 jobs
Friday, January 27, 12
28. Quality management
• Sonar reports everyday if the code had changed
(polling)
• ~90 jobs
• Continuous deployment and integration or
performances tests
• Jmeter
• Selenium
• JMXTrans / Graphite / Zabbix for monitoring
Friday, January 27, 12
43. Features
• Pre-commit: reviewing content that is not under version control. Upload a
piece of code, a file or cut-and-paste from your IDE.
• Post-commit: reviews after the code is committed to the repository.
• Moderated: reviews can have a moderator responsible for a review;
creating, approving, and determining when a review is finished.
• Un-moderated: a streamlined process where the review author is the sole
person who starts and stops the review is a simple default.
• Snippet: a pastebin service meets peer review - you can simply paste some
code and start discussing it with the team, without the need for any formal
code review workflow.
• Changeset discussions: commit messages allow a developer to provide
information with a commit. Provide free form comments on commit
messages.
Friday, January 27, 12