Continuous Delivery for Python Developers PyCon 8, 2017

Transcription

1 Continuous Delivery for Python Developers PyCon 8, 2017 live tinyurl.com/pycon8-cd

2 Peter Bittner Developer (of people, companies, code) Co-founder Painless behave-django codeship-yaml django-apptemplates djangocms-maps sentrylogs

3 Hypes are hype!... and hype means crazy.

4 Our lives, our pain.

5 Agenda 1. What is CD? 2. Why do it? 3. How do it? 4. Put it into practice 5. Demo, Q&A, workshop

6 What is ontinuous Delivery?

7 Continuous Delivery?. As a coach you do: Hands-on coding (infrastructure) 30% Start filling in backlogs (PO) Start doing meetings (SM) 20% 15% Show how PRs/MRs work (pairing) 5% Work with PM + management 10% Internal communication, 15% discussions (change mgmt) 5%

8 What Is It? (C-level management) hype Replacement for Scrum+Kanban? 1st principle of Agile Manifesto All automatic, just push code! TDD, BDD, Selenium, Docker Deployment button for business

9 Definition... a set of practices and principles... building, testing, and releasing software, faster and more frequently Text... put release schedule in the hands of the business - not IT Source:

10 It's Agile (Ever Since) Satisfy the customer! Source:

11 TDD, BDD, Selenium Tests are fundamental for build pipeline.!! risk!! No automated verification w/o tests No safeguarding against regression No safety net against deployments that would take the site down TDD good practice BDD helpful for acceptance Selenium / performance

12 Containers (Docker) Containers make process easier. Feature parity across environments Develop, Staging, Production identical Simplify deployments, no builds on hosts Simplify rollbacks Optional, but makes it easier Container images built by pipeline Push complete system

13 Why ontinuous Delivery after all?

14 Does It Solve My Problems? On-boarding developers takes days "Works on my machine" Not releasing enough features Only a few can trigger deployment "Never deploy on a Friday!" Move to a different hoster (cloud?)

15 The Definition Said Build features faster + more frequently Test changes faster + more frequently Release changes faster + more frequently Everyone (even the client) can release... and Docker said Environment parity (production = staging = dev machine) Definition:

16 That's the Plan So, in future, we will: 1. Clone a repo + run a project locally 2. Make, test + push changes 3. Get feedback from build server 4. Have changes reviewed + released All in a matter of minutes No fear to break anything Happy devs + clients

17 How do we make ontinuous Delivery happen?

18 What Do We Need? Version control Feature branching - maybe Code review, PRs / MRs A test runner, task runner Build server, CI server, pipeline Artifact storage, image registry Hosting Monitoring

19 Development Process feature branch Someone needs to ship it. production system push code open PR/MR approve build server review system

20 What to Look at Someone needs to maintain it. Infrastructure as code Agent-less deployment Stick to standard procedures + popular tools (best practices) Make it work for everyone * Self-explanatory procedures Don't break conventions Make developers love it!

21 Build Servers + Registries Someone needs to build it. Pipeline will build, push and deploy Pick a solution or combo you love to work with (GitHub+Travis+DockerHub, GitLab,...) Hosted may be cheaper than self-hosted (TCO) Build speed, pleasant UI + workflow may pay off more than a smaller price CI Services: Registries:

22 Docker Hosting Someone needs to serve it. Decent Docker hosting supports `docker machine` drivers Regular (dedicated) hosting with `docker` and `docker-compose` also works Avoid manual setup (transient servers) Shortlist:

23 Monitoring Someone needs to babysit it. Screen resource utilization after deployment Some issues are only discovered in production Capture stack traces, identify bottlenecks Get user feedback, communicate w/ users Collect historical data Monitoring: Transparency:

24 Now let's do ontinuous Delivery with Python!

25 Pythonic Choices Tox w/ pytest, Flake8, Pylint, behave uwsgi, Nginx, Compose README.rst, no docs Unit and BDD tests prepared GitHub+Travis CI / GitLab / Bitbucket Run project: `docker-compose up` `manage.py runserver` works too Run tests: `tox` or `pytest`

26 .travis.yml language: python python: 3.5 env: matrix: - TOXENV=flake8 - TOXENV=py27 - TOXENV=py35 install: pip install tox script: tox deploy: # magic stuff here

27 tox.ini [tox] envlist = flake8,py27,py35 skipsdist = true [flake8] exclude =.cache,.git,.tox,build max-line-length = 80 [pytest] addopts = --junitxml=unittests.xml --strict

28 docker-compose.yml version: "2" services: webserver: build:./config/webserver application: build: context:. dockerfile:./config/application/dockerfile user: application database: image: postgres

29 uwsgi.ini [uwsgi] cheaper = 2 chmod-socket = 660 chown-socket = application:application enable-threads = True master = True processes = 16 python-autoreload = 1 socket = /run/project/uwsgi.sock wsgi-file = /opt/project/application/wsgi.py

30 nginx.conf server { location / { include uwsgi_params; uwsgi_pass unix:///run/project/uwsgi.sock; } location /media { root /opt/project } location /static { root /opt/project; } }

31 README.rst Project Name ============ Awesome demo website for PyCon 8. Getting Started To start developing on this project simply bring up the Docker setup:.. code-block:: bash docker-compose up --build -d docker-compose logs -f

32 Don't Create Those Files! 1. Create a project skeleton (cookiecutter) 2. Use existing cookiecutters 3. Contribute to the one you love best! 4. Do the hard stuff in public (it will pay off) Run `cookiecutter gh:painless-software/ painless-continuous-delivery` Then start working immediately!

33 Grandpa nailed it, once again. I'll tell our developers. Just awesome.

34

35 One More Thing...

36

37 Demo Time!

38 Thank you! for your precious time Painless Software Less pain, more fun.