• Igor Davydenko
• Python & React.js developer at Ezhome Inc.
• From Kyiv, Ukraine
• Loves Python 3, asyncio & aio stack
• Personal Site
• @ GitHub
• @ Twitter

• First CI experience: ~2009
• Pretty hard from developer perspective
• Have no idea on how to configure BuildBot yet
• But it's written on Python

• I understood what CI is in 2011
• Hudson, then Jenkins helped me run tests, deploy projects
• I wrote code, asked DevOps to integrate project to Jenkins
• I wrote Fabric commands, asked DevOps to integrate them in Jenkins
• What if something didn't work? Yeah, ask DevOps to fix

• Open Source projects require CI as well
• Travis CI was first CI easy to configure & use
• I wrote code & did changes to .travis.yml
• If something didn't work, I take care of problem, cause I know how
• A lot of open source projects run on Travis
• Infrastructure just didn't handle load well
• They fixed eventually, but I don't trust Travis anymore

• Drone.io – Written on Go, what else?
• TeamCity – CI by JetBrains. Mkay
• Bamboo – CI by Atlassian. They have JIRA, but that's it
• Shining Panda – Jenkins in cloud

• Start an instance
• Setup Python there
• Install Jenkins from JAR
• Configure it somehow
• …
• …
• …

• Then you need to specify how to run your tests in UI
• You will be able to setup post-job in UI as well
• …

• Completely Everything
• Everything, you can imagine for CI
• But you will have a very bad time, configuring Jenkins

• Quick Setup
  Signup. Add a Project to CircleCI. Start building and testing right away. It's that simple!
• Build
• Test
• Deploy

Configure Container (machine)

machine:
  environment:
    DATABASE_URL: ...
    DJANGO_SETTINGS_MODULE: ...
    ...: ...
  python:
    version: ...
  services:
    - postgresql
  timezone: Europe/Kiev

Build Dependencies

dependencies:
  cache_directories:
    - ...
  override:
    - pip install -U pip wheel
    - make

Run Tests

test:
  override:
    - TEST_ARGS=--with-xunit make test

  post:
    - "coveralls || :"
    - ...

Deploy Project

deployment:
  staging:
    branch: develop
    commands:
      - LEVEL=staging make deploy

  production:
    branch: master
    commands:
      - LEVEL=production make dump-db
      - LEVEL=production make deploy

• You need ~5-10 min to add new project to CircleCI

1. Copy circle.yml to repo
2. Edit necessary lines
3. Commit & push to GitHub
4. Press Build Project button on CircleCI

machine:
  environment:
    COVERALLS_REPO_TOKEN: ...
    LEVEL: development
  node:
    version: 4.4.3
  timezone:
    America/Los_Angeles

dependencies:
  cache_directories:
    - node_modules
    - webpack/.babel-cache
  override:
    - npm install -g npm@3.8.6
    - make

test:
  override:
    - make test
  post:
    - "npm run coveralls || :"
    - mkdir -p $CIRCLE_TEST_REPORTS/junit/
    - mv ./test-results.xml $CIRCLE_TEST_REPORTS/junit/test-results.xml

deployment:
  production:
    branch: master
    commands:
      - LEVEL=production make deploy

1. Push to GitHub
2. Tests ran OK
3. New build is deployed

• Chat Notifications
  
  • Slack
  • Hipchat
  • Flowdock/Campfire/IRC
• Webhooks

• Set PyPI/NPM credentials as env vars
• Deploy new package on new tag pushed to GitHub

deployment:
    release:
      tag: /v\d+.\d+.\d+.*/
      commands:
        - ./circle-npm-login.sh
        - make deploy
  

• CircleCI has an API to run builds from command line
• You able to configure deploying whole your stack with ease

general:
  artifacts:
    - "api_test_report.html"
    - "slow_tests.csv"

• Yes, you can use PostgreSQL, Redis and other services

machine:
  services:
    - mysql
    - postgresql
    - cassandra
    - elasticsearch
    - rabbitmq-server
    - redis
    - riak
    - beanstalkd
    - couchbase-server
    - neo4j
    - sphinxsearch

• It requires GitHub to work
• Sometimes GitHub does not work, as CircleCI