2. • Software Factory Team
• Development rules and recommendations
• Methods and Tools
• To improve quality and productivity
• Teams training
• To improve ours skills
• Support & Services
• About tools, methods, processes, and technical
Software Factory Team
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
4. • Documentations
• http://int.exoplatform.org/portal/g/:spaces:development_standards/
development_standards
• http://developer.exoplatform.org (should be the place to go)
• https://wiki-int.exoplatform.org/display/exoSoftwareFactory/Home
(deprecated but but not moved in intranet)
• Activity/Requests tracked in Jira :
• https://jira.exoplatform.org/browse/SWF
• Contact us :
• Email : exo-swf@exoplatform.com
• Skype : aheritier
How are we working ?
6. Git on GitHub
• https://github.com/exoplatform/
• Blessed repositories
• Rights limited per profiles/roles
• https://github.com/exodev/
• Development repositories
• Pull/Push rights for all eXoers
• https://github.com/exo-addons/
• Platform Add-ons
10. Nexus for
collaboration
Deploy 3rd Party Artifacts
Collaborate with Internal
Repositories
Distribute to the community with
Public Repositories
Distribute to customers with
Private Repositories
17. Continuous
Integration
Build,Test and Deploy ASAP
using Maven 2/3
from sources (SVN,GIT
googlecode, jboss, exo, github
repos) to Maven repositories
managed by Nexus (if build/tests
are passing)
18. Reporting
*-sonar jobs are loading data into
sonar to provide code analysis.
*-site are generating Maven site on
projects.exoplatform.org
They are launched once a day if
the codebase change otherwise
once per WE
41. 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.