<p>What you've listed is actually two different things, continuous delivery and continuous integration.  When people talk about CI they typically are only referring to the testing part; automated unit, function, and integration testing with some sort of version bump or code promotion at the end.  Looks like the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Drupal+Development" rel="nofollow noreferrer">Jenkins wiki</a> has some specific pointers about Drupal.</p>

<p>As far as environment promotion, you're getting into continuous delivery which Jenkins can also be used for.  Consider looking at the more modern <a href="https://jenkins.io/solutions/pipeline/" rel="nofollow noreferrer">Jenkins Pipelines</a> for CD pipelines.</p>

CC BY-SA 3.0
2017-03-11T17:42:03.270Z
2017-03-11T17:42:03.270Z
Travis Thompson
<p>Assume you want to implement <a href="/questions/tagged/continuous-integration" class="post-tag" title="show questions tagged &#39;continuous-integration&#39;" rel="tag">continuous-integration</a> (= CI) and <a href="/questions/tagged/continuous-deployment" class="post-tag" title="show questions tagged &#39;continuous-deployment&#39;" rel="tag">continuous-deployment</a> (= CD) for building and maintaining websites using <a href="https://www.drupal.org/project/drupal" rel="nofollow noreferrer">Drupal</a> (let's assume for Drupal Version 7). Often times Jenkins seems to be recommended as one of the most appropriate solutions for doing so.</p>

<p>But what kind of CI/CD related functionality can I actually use it for? Here are some of things I'm thinking of, but I'm not sure if I'm correct on that, and/or if these are the only things:</p>

<ul>
<li>CI related: Automated testing.</li>
<li>CD related: Migrating custom module development between dev / staging / QA environments.</li>
</ul>

CC BY-SA 3.0
2017-03-12T01:43:28.033Z
In my job we are trying to use Ansible + DrupalVM + Jenkins in our environment.
Adrian Cid Almaguer
CC BY-SA 3.0
2017-03-13T10:19:02.803Z
@AdrianCidAlmaguer maybe you should post an answer to (briefly) explain each of those 3 things?
Pierre.Vriens
CC BY-SA 3.0
2017-03-13T13:30:09.000Z
I'm not the expert in this topic, but I will ask for some information about how this worls.
Adrian Cid Almaguer
<jenkins><continuous-integration><continuous-deployment><drupal>
How can Jenkins help to implement CI/CD for Drupal?
Pierre.Vriens
# How can Jenkins help to implement CI/CD for Drupal?

(Asked by: username_0 on 2017-03-11)

Assume you want to implement [continuous-integration](/questions/tagged/continuous-integration "show questions tagged 'continuous-integration'") (= CI) and [continuous-deployment](/questions/tagged/continuous-deployment "show questions tagged 'continuous-deployment'") (= CD) for building and maintaining websites using [Drupal](https://www.drupal.org/project/drupal) (let's assume for Drupal Version 7). Often times Jenkins seems to be recommended as one of the most appropriate solutions for doing so.

But what kind of CI/CD related functionality can I actually use it for? Here are some of things I'm thinking of, but I'm not sure if I'm correct on that, and/or if these are the only things:

* CI related: Automated testing.
* CD related: Migrating custom module development between dev / staging / QA environments.

**Tags:** jenkins, continuous-integration, continuous-deployment, drupal

> **Comments:**
> **username_1**: In my job we are trying to use Ansible + DrupalVM + Jenkins in our environment.  
> **username_0**: @AdrianCidAlmaguer maybe you should post an answer to (briefly) explain each of those 3 things?  
> **username_1**: I'm not the expert in this topic, but I will ask for some information about how this worls.  

---

## 1 answers

### Answer by username_2 on 2017-03-11. Score: 4 | Accepted answer

What you've listed is actually two different things, continuous delivery and continuous integration. When people talk about CI they typically are only referring to the testing part; automated unit, function, and integration testing with some sort of version bump or code promotion at the end. Looks like the [Jenkins wiki](https://wiki.jenkins-ci.org/display/JENKINS/Drupal+Development) has some specific pointers about Drupal.

As far as environment promotion, you're getting into continuous delivery which Jenkins can also be used for. Consider looking at the more modern [Jenkins Pipelines](https://jenkins.io/solutions/pipeline/) for CD pipelines.


---

