The eXo Software Factory document describes eXo's development practices and tools used to improve quality and productivity. It outlines the software factory team, development rules and recommendations, methods and tools training, and support services. It then provides details on source control management with Git and GitHub, binaries management with Nexus, issue and task tracking with Jira, continuous integration with Jenkins, quality management with Sonar, acceptance testing, code reviews with Fisheye and Crucible, and links to these various tools.

1. eXo Software Factory
Harder, Better, Faster, Stronger

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 ?

5. SCM
Source configuration management

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

7. Nexus
Binaries management

8. Nexus

9. Nexus for productivity

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

11. Jira
Issues and tasks management

12. Jira

13. Jira with Jira Agile

14. Jira with Jira Capture

15. Jenkins
Automation and scheduling : Build,Tests, Deployment

16. Jenkins

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

19. Mobile developments - continuous
integration and deployment

20. Reporting and
dashboards
• Jenkins => Teams
• Emails (email-ext plugin)
• Teams => Jenkins
• Dashboard views
• Radiator views

21. Dashboards

22. Unstable Build
Notification

23. Build Failure
Notification

24. Radiator views

25. Sonar
Quality management

26. Sonar, a quality
dashboard

27. Sonar, analyze your
project

28. Sonar, Continuous
Improvement ?

29. Acceptance
Tests and validation platform

30. Acceptance
• Access to all test instances deployed each
night
• Monitor features branches statuses

31. Acceptance

32. Acceptance

33. Fisheye & Crucible
Sources browsing and code review

34. Fisheye/Crucible

35. Teams Code Reviews
Asynchronous, distributed discussions

36. Have fully threaded conversations
about source code with your others.

37. Simply click on some lines to add
comments.

38. Comments can be displayed inline or
next to the code they refer to.

39. Flag a comment as a defect to
highlight it.

40. Teams Code Reviews
Manage reviews

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.

42. Browsing changesets, searching for files,
or uploading a patch to add content

43. You can use the classic review roles Moderator,
Author and Reviewer or let anyone do anything.

44. Only a title and code are needed to
start a Snippet Review.

45. Use change set comments as a
catalyst for code discussions.

46. Reviews evolve as your code evolves

47. Live updates and notifications

48. Teams Code Reviews
Dashboard & Reports

49. Activity Stream

50. Who is holding up

51. Which issues are being held up by
reviews?

52. Teams Code Reviews
Jira Integration

53. Create Jira issues

54. Resolve subtasks from Crucible

55. Create reviews from Jira

56. Follow reviews attached to a jira
project

57. Conclusion

58. SWF links
Git :
https://github.com/exoplatform
https://github.com/exodev
https://github.com/exo-addons
Nexus :
https://repository.exoplatform.org
Jenkins :
https://ci.exoplatform.org
Jira :
https://jira.exoplatform.org
Fisheye/Crucible :
https://fisheye.exoplatform.org
Sonar :
https://sonar.exoplatform.org
Acceptance :
https://acceptance.exoplatform.org
Maven sites :
https://projects.exoplatform.org

59. Questions