Team Development & Release Management for ISVs

Andrew Albert, salesforce.com Jordan Baucke, BracketLabs Eric Wilcox, FinancialForce

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.

Andrew Albert Director, ISV Technical Enablement

aalbert@salesforce.com

Jordan Baucke Developer/Architect

@jordanbaucke @bracketlabs @readytalkgeeks

Eric Wilcox Senior Developer/Architect

roc.wilcox@gmail.com

How to setup a new developer

Developer Toolset

Force.com IDE

salesforce Dev & Test Environments

Source Control

Force.com Migration Tool

2

1 3

4

Force.com IDE Force.com Migration Tool git

Partner Developer Edition

Source Code Repository

1 Configure & Run Ant Script 2 git clone git@github/Project

3 Repository downloaded to machine

4 Deploy to Server

5 git add

Setup environment & Check in

Setting up a new environment Demo

Compare & Contrast

Tip: API versioning

Continuous Builds & QA

FinancialForce’s Continuous Build Process

Testing Org

Source Code Repository

Hudson Server Force.com Migration Tool

Run undeploy script 2

Checkout build 1

Deploy to Server 3

Packaging Org

Deploy to Server (with Check Only) 4

Teardown – How to dynamically clean an org

Target Org

Ant Retrieve

Clean Std Obj Layouts

Build Package

Build Destructive Changes

Deploy

Deploy Layouts

1

2

3

4

5

6

Undeploy Script Demo

BracketLab’s QA Process

Partner Test Edition (EE)

Source Code Repository Jenkins Server

Force.com Migration Tool

Checkout build 1

Run Migration tool & deploy to all editions 2

Professional Edition Group Edition

Handling different editions and features? Group Edition Professional Edition Enterprise Edition

Know which edition-specific features your app requires: Record Types, Workflow, etc Know which org-specific features your app requires: Chatter, Multi-Currency, Sharing, Profiles, etc

TIP: Test your app in the different editions!!!

Release Management

How to release an app (unmanaged -> managed)

Hudson Server Force.com Migration Tool

Packaging DE org

2 Run Namespacing script Run Test Methods Verify components Run Code Scanners

Install and Test Editions & Browsers

Source Code Repository

1 Get Build

3

4 Create Managed-Beta

5 6

Create Managed-Release

Namespace conversion script

•  Javascript references to 'Web Service' methods o  Javascript Remoting, VF Ajax Toolkit, APEX REST

Endpoints •  Dynamic SOQL •  VF Pages referenced in custom buttons

Solved with Ruby script (basically glorified find and replace) Find & Replace: /*NS*/-MyNamespace.

https://github.com/jordanbaucke/sfdc-namespace-prefix

Don’t Forget to….

Update Appexchange Listing 1

Update Appexchange Test Drive 2

Update Release Notes 3

Update Installation Guide 4

Update Trialforce Source orgs 5

How do you schedule your releases?

How do you test your app w/ each salesforce release?

Partner Portal: http://p.force.com/releases Twitter: @partnerforce

Takeaways

Undeploy Script to Clean out a test org: https://github.com/financialforcedev/df12-deployment-tools

2

Find/Replace Ruby script to prepend namespace: https://github.com/jordanbaucke/sfdc-namespace-prefix 3

Use the DF12 Session Chatter Group to collaborate 4

Team Development articles on developer.force.com 5

Setting up a new Developer demo: https://github.com/BracketLabs/AppExchange-Team-Development-on-Force.com-Platform-Demo

1

Andrew Albert

salesforce.com ISV Technical Enablement

Jordan Baucke

BracketLabs Developer/Architect

Eric Wilcox

FinancialForce Senior Developer/Architect