The document discusses team development and continuous integration on the Force.com platform. It recommends critical components for success like issue tracking, source control, code review, and continuous integration. It provides examples of tools that can be used for these components, such as JIRA for issue tracking, GitHub for source control, and Snap CI for continuous integration. Regularly deploying code changes to a staging sandbox and conducting code reviews allows teams to catch errors early and ensure high quality code.

1. Team Development and
Continuous Integration on
Force.com
Daniel Hoechst
Senior Manager, CRM Systems
@dhoechst
Instructure

2. THE INSTRUCTURE STORY
· Founded 2008
· Launched product in 2011
· Located in Salt Lake City
· 700+ employees
· ~1,600 clients
· 100% native SaaS

3. Every had a deployment like this?

4. Or Maybe This?

5. Team Development Challenges
•Collaboration
•Conflicts with developers working on the same object or class
•Change tracking
•Issue identification early in development process

6. Flosum
Currentstateofdeploymentflows
Dev1
Dev3
Dev2
Dev4
QA
UAT
Stage
Prod
Lackofvisibility Nocontrol orcoordination NoManageability

7. Critical Components for Success
•Bug/Feature Documentation and Tracking
•Multiple Sandboxes/Dev Orgs
•Source Control
•Code Review / Code Standards
•Continuous Integration

8. Tools of the Trade

9. Issue Tracking
•JIRA
•Agile Accelerator
•Github Issues
•Homegrown

10. Sandboxes
Developer
Sandbox for each
admin and
developer
Staging Sandbox
to receive
merged metadata
User Acceptance
Testing Sandbox

11. Sublime Text + MavensMate
•Retrieve Local Copy of Metadata
•Make Changes

12. Github
•All metadata stored in source control
•Pull Requests used for code review

13. SourceTree
•Git Client
•Easy to Visualize Changes

14. Snap CI
•Continuous Integration Tool
•Test Pull Requests
•Deploy changes to staging
sandbox
•Uses Force.com Migration Tool

15. Clayton
•Automated Code Review

16. Demo

17. Gotchas
•Destructive changes aren’t automated
•Not all changes can be pushed through metadata
•API version changes

18. Development Process
Log Issue
(Github)
Create
Branch
(SourceTree)
Develop
(Sublime +
MavensMate)
Commit and
Create Pull
Request
(SourceTree)
CI Validate
Changes
(Snap CI)
Code Review
and Merge
(Github)
Build to
Staging Org
(Snap CI)

19. Benefits
•Well understood process
•No developers overwriting code
•Track changes back to an issue and developer
•Easy to rollback
•Immediate feedback with build errors

20. Resources
•Sample repo: https://github.com/dhoechst/Team-Dev-Force-Dot-Com
•Team Development on Force.com
http://www.verticalcoder.com/2014/01/06/team-development-on-force-
com/
•Continuous Integration Using Drone.io
http://www.verticalcoder.com/2014/01/07/continuous-integration-using-
drone-io/
•MavensMate and Git for Non
Developershttps://tdd.instawiki.com/display/SF/Mavens+Mate+and+Git+fo
r+Non+Developers

21. Q&A

22. Thank you!