Enterprise Source and ReleaseManagement Using StratoSourceBy Red Hat
Safe Harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contai...
Tiaan KrugerPrincipal Applications Engineer
What We Will Cover Common problems with large deployments Source & configuration backup and tracking Release Management
Force.com Development     Administrator                     DEV   Production      Developer
Enterprise Force.com Reality                           Administrator   Administrator    Administrator           Administra...
Issues Cloud has “one version of the truth” Code depends on configuration Code collisions   Parallel development touches ...
Part 1: Flow ManagementPartner CenterTeam                         PRM DEV                                       QA /Sales ...
Part 2: Change Management             Introducing StratoSource…               So why a custom tool?
Traditional Development            Push Code                                                                  Quality     ...
Traditional + Force.com Breaks Down                   Shared / Interdependent Configuration                               ...
StratoSource + Force.com                                                            Release          Release              ...
StratoSource Features Continuous Force.com backups   Includes code AND configuration Tracks changes   Identify pieces in...
StratoSource Components                                          Development                                            St...
StratoSource Installation Low overhead to install “Bolts on” to existing cloud environments   No change to current develo...
Jarrod ShumakerSenior Business Analyst
Demo of StratoSource
Key TakeawaysMaximize efficiency with flow managementSource backup, change detection & release management (withStratoSourc...
Tiaan Kruger              Jarrod ShumakerPrincipal Software Developer   Senior Business Analyst
Enterprise Source and Release Management Using StratoSource
Upcoming SlideShare
Loading in …5
×

Enterprise Source and Release Management Using StratoSource

757 views

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
757
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
13
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Enterprise Source and Release Management Using StratoSource

  1. 1. Enterprise Source and ReleaseManagement Using StratoSourceBy Red Hat
  2. 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. 3. Tiaan KrugerPrincipal Applications Engineer
  4. 4. What We Will Cover Common problems with large deployments Source & configuration backup and tracking Release Management
  5. 5. Force.com Development Administrator DEV Production Developer
  6. 6. Enterprise Force.com Reality Administrator Administrator Administrator Administrator DEV QA ProductionAdministrator Developer Developer
  7. 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. 8. Part 1: Flow ManagementPartner CenterTeam PRM DEV QA /Sales Force Automation Integration ProductionTeam SFA DEVApp MaintenanceExternal Contractor
  9. 9. Part 2: Change Management Introducing StratoSource… So why a custom tool?
  10. 10. Traditional Development Push Code Quality Fetch / Push Fetch Build Deploy Assurance Code Code MachineDeveloper Source Control Production
  11. 11. Traditional + Force.com Breaks Down Shared / Interdependent Configuration Quality Merge Assurance Code Deploy Source Control Developer AdministratorSandboxes Production + Code Untracked &Repositories Error Prone
  12. 12. StratoSource + Force.com Release Release Push Code Manifest PackageDeveloper Validate & Deploy Functional Test Quality Environment StratoSource META-Data Assurance META-Data Snapshots Snapshots ConfigureAdministrator GIT Production Source Control
  13. 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. 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. 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. 16. Jarrod ShumakerSenior Business Analyst
  17. 17. Demo of StratoSource
  18. 18. Key TakeawaysMaximize efficiency with flow managementSource backup, change detection & release management (withStratoSource)It is Open Source & FREE to use! Source & Installable versions available for download at: www.StratoSource.com
  19. 19. Tiaan Kruger Jarrod ShumakerPrincipal Software Developer Senior Business Analyst

×