DDEV DDEV-Live Tutorials, 10 Jun 2020

Previous Meeting

⏯

youtube image

►

From YouTube: Connecting Your CI/CD Pipeline with Jenkins and DDEV-Live

Description

Unlike other CMS hosting solutions, connecting a CI/CD pipeline with DDEV-Live is a simple six-step process. This example shows how to create a user acceptance testing (UAT) environment using Jenkins — allowing you to quickly share projects with clients.

Even if your client is already locked into a hosting provider, you can simply set up previews of their projects by automatically deploying a test site via Jenkins onto DDEV-Live — skipping the hassle of going all the way to production before review.

While the above tutorial uses Drupal 8 as an example, DDEV-Live is for far more than just Drupal hosting and supports a wide array of PHP applications and CMSs.

More info on simplifying your end-to-end workflows: https://bit.ly/2MYN2ot
Ready to get rolling? Read the docs: https://bit.ly/3sndxUW

A

This demo I'm going to show you how to create UAT environments in side of data of live using the Jenkins, CI CD tool. So on my local host running indie, devs local I'm running just a very generic Drupal 8 site, you can see it's running eight point, nine point X and looks pretty basic I'm going to go, create a feature, branch and name it after the ticket number that I'm working on so we're gonna, say just kind of hit some numbers here and now.

A

For the purposes of this demo, I could be creating a module like changing the themes. Color. Just some kind of you know normal everyday work that you may be doing. I'm just gonna create a commit and.

A

Then I'm going to push the repository up to my. For course you do the branch up to my fork.

A

Jenkins I will show you how this site is configured a little bit. I've got some credentials inside of Jenkins that basically links my Jenkins and my idea of live API token. So you can see here the first group global credentials for that, and then I've also got a build job configured to basically build any branch that is feature star.

A

So it's hooked up to my fork. It's enabled github SCM pulling so I've got a web hook installed and the github side and then I've bound my correct Mike secret X credential, to this token variable, as you can see here, as for what this command is doing, its setting up the home guru because d/deaf live isn't installed. It's homebrew in this case I am configuring a site name, so I'm pre fixing my eyesight with the port staging it'll, have a branch name and then the the Jenkins build job next thing.

A

I'm doing here is authenticating with the data of live clients, so I'm passing that token variable from above here and passing default Oregon's my organization called David, then, as I would normally I'm creating a site. So I've got the basic same thing: you do on the command line, just passing in some environmental variables for Jenkins, so creating a site based on that site. Name: here's my repository, here's, the Jenkins passed in branch that is being built and then I'm also because this is a Drupal.

A

It's a time running composer install the next few lines here are basically for checking the site status so is to sign up and healthy. Is there a business site accessible and the preview URL is provided, and then the next few lines are examples of kind of the next steps.

A

I would suggest so I could do a a deed of life, exact to the site name and pass in the draw command, since all sites or I could push kind of a precede a database into my data of live site, name from Jenkins or from s3, or something like that. In the background, if this builds sleep this alone, this build has been going on since it got put my book and let's go check out. The output.

A

So, as you can see basic output here, here's my cute message: there's some setup you're seeing for homebrew, so a bunch of path stuff in the next line. Here's my branch and my site name configured with my branch in my I Jenkins build, did have live off to the authentic 8 and that's successful and then here's my site builds happening in real time. So this is now waiting for the site to come up and be live and then once it is I'll click. The link and I'll show you what's happening on that site.

A

So now my sites become available and it should just bring me to a generic Drupal install page, because I haven't done anything there with it. I could then pass this URL to my client. Who could you you, eighty on it and then prove it for production deployment? I could potentially now run the hat tests against my site or any any tests.

A

You require a live site for so like visual regression, that kind of thing and then, as a final step, once you know kind of the approvals done, you can then either programmatically inside of Jenkins or man line you could go and you would see that line delete sites.

A

And the leta say thanks for watching I hope you found this video informative and if you need more information, please visit our documentation site as seen on your screen right now. Thanks again.