Automating the Impossible: End to End Team Development for ISVs (October 14, 2014)
0 likes858 views
This document discusses automating the development process for managed packages on the Salesforce platform. It describes how the Nonprofit Starter Pack team uses automation tools like GitHub, Jenkins, CumulusCI and Ant to implement version control, continuous integration, and frequent releases. Key benefits of this approach include improved team productivity, reduced errors, and savings of over 4,500 development hours per year. Local unmanaged packages allow development entirely in metadata and help address challenges of developing managed packages in unmanaged orgs.
Automating the Impossible: End to End Team Development for ISVs (October 14, 2014)
- 1. Automating the Impossible: End to End Team Development for ISVs Jason Lantz Lead Release Operations Engineer Salesforce.com Foundation
- 2. Safe Harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
- 3. Jason Lantz Lead Release Operations Engineer
- 4. Background
- 5. 1% Product Equity Time 680,000+ Hours Service $68M+ Grants 23,000+ Nonprofit + Higher Education Organizations 1-1-1 Model Adopted by
- 6. Icons made by Elegant Themes, Freepik from www.flaticon.com licensed under CC BY 3.0 Scrum Team Refactor Community Contributions Frequent Releases
- 7. "LargeTribarGotschuchenAustria" by Samo Kupper - Own photography, owner: Verein Treffpunkt Physik, Samo Kupper, Science Center Gotschuchen, http://www.expi.at. Licensed under Public domain via Wikimedia Commons Challenges
- 8. Results
- 9. Team Metrics (in last year) 513 Issues Closed 313 Feature Branches Merged 2,123 Commits 2,000 Installations in 5 months 18 Production Releases in 5 months 213 Beta Releases in 10 months
- 10. Nonprofit Starter Pack 3.0 Team David Habib Senior Force.com Developer Jason Lantz Lead Release Operations Engineer Carlos Ramirez Martinez-Eiroa Senior Force.com Developer Jon Varese Lead Technical Writer Nicolas Campbell Force.com Developer Kevin Bromer Director, Product Management
- 11. How is this possible?
- 12. Automation Metrics (in last year) 785 Master branch builds 345 Master -> Feature Merges 2,549 Feature branch builds 296 Automated Beta Releases
- 13. Automation Metrics 4,690 Dev Hours Saved
- 14. Automation Metrics 117 Dev Weeks Saved
- 15. Best Practices Version Control Team Productivity Frequent Releases Reduce Human Error • Repeatable builds… “it works in my org” • Prevent unintentional inclusion/exclusion of package metadata • Always be ready to cut a new release • Isolate all work in feature branches • Make betas available ASAP to maximize feedback • Automate test execution • Notify developers of errors ASAP • Automate common developer tasks • Know who, what, when, and why • Version Control as master • Don’t develop in packaging org! Icons made by Elegant Themes, Freepik from www.flaticon.com licensed under CC BY 3.0
- 16. Unmanaged Development of Managed Packages
- 17. Challenges with Unmanaged Metadata • Scenario 1: Developer creates list views in their org for debugging – Unintentional inclusion of package metadata • Scenario 2: Developer wants to clean their DE org – Cleaning orgs is hard to do • Scenario 3: Release manager deploys to packaging – Packaging constraints prevent deployment of some metadata – Must manually add/remove package components
- 18. Local Unmanaged Packages Unmanaged Metadata Cumulus Managed Metadata npe01 npo02 npe03 npe4 npe5 • Normal deployments go into Unpackaged • In package.xml: <fullName>Cumulus</fullName> • Creates unmanaged package Cumulus • Deploys metadata into the package • Ant retrieve all unmanaged: <sf:bulkRetrieve /> • Ant retrieve Cumulus: <sf:bulkRetrieve packageNames=“Cumulus” />
- 19. Advantages of Local Unmanaged Packages • Scenario 1: Developer creates list views in their org for debugging – Inclusion in retrieves is explicit rather than implicit – Retrieved objects are clean (only metadata from package) • Scenario 2: Developer wants to clean their DE org – ant uninstall • Scenario 3: Release manager deploys to packaging – Developers experience packaging constraints in DE org – Metadata automatically added to managed package – CumulusCI deletes metadata automatically
- 20. Build & Automation Tools
- 21. Automation Tools • Developer Edition Orgs
- 22. Automation Tools • Developer Edition Orgs • GitHub
- 23. Automation Tools • Developer Edition Orgs • GitHub • Force.com Ant Migration Tool
- 24. Automation Tools • Developer Edition Orgs • GitHub • Force.com Ant Migration Tool • Jenkins
- 25. Automation Tools • Developer Edition Orgs • GitHub • Force.com Ant Migration Tool • Jenkins • CumulusCI
- 26. Automation Tools • Developer Edition Orgs • GitHub • Force.com Ant Migration Tool • Jenkins • CumulusCI • mrbelvedere
- 27. Workflow Diagram
- 28. Getting Started Automation Build Scripts Version Control Automate the execution of build scripts when changes are pushed to GitHub Setup CumulusCI build scripts in repository for DE org and packaging org deployments Retrieve package metadata from packaging org and check into GitHub
- 29. The Zen of Package Version Control Package = Metadata Metadata = Files Files can be version controlled!
- 30. Check out the new Partner Community https://partners.salesforce.com/
- 31. Connect with Partners in the Partner Zone The Westin Hotel, Market Street 2nd Floor – Metropolitan Ballroom INNOVATE with the leading technology • Demos of new Salesforce technology CONNECT with members of the partner community • Partner Community Theater • Networking areas • Welcome reception and daily lunch service GROW your business with resources • 70+ partner-specific sessions • ‘Ask the Experts’ consultation stations
- 32. AppBash 2014 on Wednesday Night!