Salesforce Deployment Managed by Continuous Delivery
Salesforce Deployments can be a bit tricky with one-off scripts. We have customers using DeployHub who want to include updates to Salesforce as part of their continuous deployment, driven by continuous delivery.
Salesforce provides an Ant Toolkit that helps you call the deployment process. We use their Ant Jar as part of the solution. Our DeployHub process allows the deployment to adapt across the pipeline. No static references to environments are kept in the script.
The Salesforce Ant Jar should be copied into the Ant Library directory so the salesforce task is picked up. The following properties are required: User Name, Password, Server URL and Test Level.
<property="sf.username" value="myusername" /> <property="sf.password" value="mypassword" /> <property="sf.serverurl" value="https://test.salesforce.com" /> <property="sf.testlevel" value="RunLocalTests" />DeployHub enables this deployment to be extended across the Continuous Delivery Pipeline without the need to create another build.xml or a build.properties.
DeployHub’s Key Features
- Blueprint your application’s logical view
- Publish and Catalog Microservices
- Version Microservice Configurations
- Release and Track Microservices
- Manage Database Deployments
- Continuous Deployment Blogs
- Understanding a Microservice Pipeline
- Microservice Continuous Integration – Where’s the Build?
- Working with Helm for your Microservices Releases
- Kubernetes Pipeline Challenges
- Managing Embedded Configurations
- Questions and Answers on managing a K8s Pipeline
- Running Safe Blue / Green Deployments
- The DeployHub Jenkins Plug-in
- Setting Up the Jenkins Plug-in
- The DeployHub CircleCI Orb
- Creating a Continuous Feedback Loop
- Release Agents – the Enemy of Continuous Deployments
- DeployHubs Release Architecture
- Why we need Application Packages for CD
- Agentless Deployments with DeployHub’s Engine
- Version Jumps and Tracking
- Blogs on Microservice Configuration Management