Enterprise Source and Release Management Using StratoSource
2 likes783 views
This document describes Enterprise Source and Release Management using StratoSource. It discusses common problems with large Force.com deployments including lack of versioning, backups, and change control. It then introduces StratoSource as a custom tool to address these issues. Key features of StratoSource include continuous Force.com backups, tracking changes, scheduled tests, deployments, comparing environments, and integrating with source control like GIT. The presentation demonstrates StratoSource which is open source and installs on Linux to provide release and change management for Force.com environments.
Enterprise Source and Release Management Using StratoSource
- 1. Enterprise Source and Release Management Using StratoSource By Red Hat
- 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 intellectual property and other litigation, risks associated with 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-Q for the most recent fiscal quarter ended July 31, 2012. This 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. Tiaan Kruger Principal Applications Engineer
- 4. What We Will Cover Common problems with large deployments Source & configuration backup and tracking Release Management
- 5. Force.com Development Administrator DEV Production Developer
- 6. Enterprise Force.com Reality Administrator Administrator Administrator Administrator DEV QA Production Administrator Developer Developer
- 7. Issues Cloud has “one version of the truth” Code depends on configuration Code collisions Parallel development touches the same files No versioning, No backup No undo No change tracking No change control! “What’s in a release?”
- 8. Part 1: Flow Management Partner Center Team PRM DEV QA / Sales Force Automation Integration Production Team SFA DEV App Maintenance External Contractor
- 9. Part 2: Change Management Introducing StratoSource… So why a custom tool?
- 10. Traditional Development Push Code Quality Fetch / Push Fetch Build Deploy Assurance Code Code Machine Developer Source Control Production
- 11. Traditional + Force.com Breaks Down Shared / Interdependent Configuration Quality Merge Assurance Code Deploy Source Control Developer Administrator Sandboxes Production + Code Untracked & Repositories Error Prone
- 12. StratoSource + Force.com Release Release Push Code Manifest Package Developer Validate & Deploy Functional Test Quality Environment StratoSource META-Data Assurance META-Data Snapshots Snapshots Configure Administrator GIT Production Source Control
- 13. StratoSource Features Continuous Force.com backups Includes code AND configuration Tracks changes Identify pieces in a release Detect collisions Associate to requirements / Agile stories Scheduled Unit test runs Deployments Compare environments
- 14. StratoSource Components Development Stories CRON Timer Change Detection Script HTML MySQL Backup DB Process Django StratoSource Frontend Meta Data SOAP API GIT HTML Source Force.com Control CGIT Environments GIT Browser
- 15. StratoSource Installation Low overhead to install “Bolts on” to existing cloud environments No change to current development process All open source components Runs on out of the box Fedora Linux RPM install handles all dependencies Database setup script included Written in Python & Django Can be ported to other platforms
- 16. Jarrod Shumaker Senior Business Analyst
- 18. Key Takeaways Maximize efficiency with flow management Source backup, change detection & release management (with StratoSource) It is Open Source & FREE to use! Source & Installable versions available for download at: www.StratoSource.com
- 19. Tiaan Kruger Jarrod Shumaker Principal Software Developer Senior Business Analyst