<p>I would recommend to create an issue about CD in the ticket system of salesforce. I have googled a little bit and this seems to be <a href="https://success.salesforce.com/issues_index" rel="nofollow noreferrer">their issue tracker</a>.</p>

<p>I would prevent to implement CD in salesforce as that will be very cumbersome and will take a lot of time. In my opinion this issue should be solved by SalesForce itself.</p>

CC BY-SA 3.0
2017-11-26T11:24:52.967Z
2017-11-26T11:24:52.967Z
030
<p>In an organization with a hundred developers, and several thousand salespeople using SalesForce to create their application. Given the restrictions of SalesForce environment and deployment options.</p>

<p>What would be the process and which tools to use to reach a delivery pipeline where changes can be delivered to production many times per day?</p>

<p>The basic flow is:</p>

<ol>
<li>salespeople think of ideas for improving their flow (bugs, new dev).</li>
<li>product managers distill the requirements and pass onto developers.</li>
<li>developers write code and create configuration changes in git.</li>
<li>magic happens (currently takes about 3-4 months).</li>
<li>new changes are in production and salespeople can use it.</li>
</ol>

CC BY-SA 3.0
2017-06-25T15:53:57.013Z
SalesForce offers afaik a complex mix of products. For a use case, you could list the tools and check for APIs available.
Ta Mu
CC BY-SA 3.0
2017-06-25T15:56:07.573Z
The list of APIs at https://developer.salesforce.com/ is even larger, and most of these do not support continuous delivery really. Would be interested in learning from practical experience of developers working with the SF platform now they can shorten lead time.
Evgeny Zislis
<continuous-delivery>
Delivery in a SalesForce environment
Evgeny Zislis
# Delivery in a SalesForce environment

(Asked by: username_0 on 2017-06-25)

In an organization with a hundred developers, and several thousand salespeople using SalesForce to create their application. Given the restrictions of SalesForce environment and deployment options.

What would be the process and which tools to use to reach a delivery pipeline where changes can be delivered to production many times per day?

The basic flow is:

1. salespeople think of ideas for improving their flow (bugs, new dev).
2. product managers distill the requirements and pass onto developers.
3. developers write code and create configuration changes in git.
4. magic happens (currently takes about 3-4 months).
5. new changes are in production and salespeople can use it.

**Tags:** continuous-delivery

> **Comments:**
> **username_1**: SalesForce offers afaik a complex mix of products. For a use case, you could list the tools and check for APIs available.  
> **username_0**: The list of APIs at https://developer.salesforce.com/ is even larger, and most of these do not support continuous delivery really. Would be interested in learning from practical experience of developers working with the SF platform now they can shorten lead time.  

---

## 1 answers

### Answer by username_2 on 2017-11-26. Score: 1

I would recommend to create an issue about CD in the ticket system of salesforce. I have googled a little bit and this seems to be [their issue tracker](https://success.salesforce.com/issues_index).

I would prevent to implement CD in salesforce as that will be very cumbersome and will take a lot of time. In my opinion this issue should be solved by SalesForce itself.


---

