ģ) After the image is pushed, Drone will SSH into your EC2 container (where your application is hosted), pull your newly updated image, and stop, update and restart your web application. This time, after building and testing your application, drone will create a Docker image of your application and push this image to DockerHub. drone.yml, run any tests your project has before finally reporting back its status to Github.Ģ) After tests have passed and the new code has been merged in, the same webhook will queue up another build on the drone server. The basic outline of the pipeline is as follows:ġ) After opening a pull request on your Github repo, a webhook will queue up a drone build for a drone agent to pick up, build your specified environment outlined in your projects. I’m going to assume a basic understanding of Amazon Web Services, Docker, Gunicorn, Nginx and some familirity with Django. ![]() This tutorial is for anyone who is still somewhat new to web development and is looking for an excuse to set up a relatively simple continuous integration/delivery pipeline. ![]() In Part 1 we will set up some simple automated testing for a Django, Docker/Docker-Compose application. This is the first part of a multi-part tutorial covering a simple(ish) setup of a continuous integration/deployment pipeline using Drone.io.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |