Upgrade to Pro — share decks privately, control downloads, hide ads and more …

CIE as SaaS. Why is Apiary using CircleCI?

CIE as SaaS. Why is Apiary using CircleCI?

# What do you need from your CIE?

1. Fast
2. Reliable
3. Scalable
4. Maintenance costs
5. Monitoring

Ladislav Prskavec

January 09, 2019
Tweet

More Decks by Ladislav Prskavec

Other Decks in Technology

Transcript

  1. Timeline 4 2012 Started using CircleCI 4 2015 Parallel testing

    (initially 2, now 8 nodes) 4 2016 Docker 4 2017 CircleCI 2.0 (docker native) Ladislav Prskavec - HiveTalks, 9.1. 2019 3
  2. What do you need from your CIE? 1. Fast 2.

    Reliable 3. Scalable 4. Maintenance costs Ladislav Prskavec - HiveTalks, 9.1. 2019 5
  3. Fast 4 Do you know your time to deploy? 4

    Do you know how much time is spent in queue? 4 What is the maximum acceptable time for your build (5, 15, 30 min, 4h)? 4 Do you monitor those times or just guessing? Ladislav Prskavec - HiveTalks, 9.1. 2019 7
  4. 4 Awareness (dashboards, metrics) 4 Groups (master, nightly) 4 Parallelism

    (speedup tests) Ladislav Prskavec - HiveTalks, 9.1. 2019 10
  5. 4 Detect flaky tests (2 builds with 1 git hash)

    4 Awareness (dashboards, metrics) 4 Process 4 Consistency Ladislav Prskavec - HiveTalks, 9.1. 2019 17
  6. 1. Responsibility Every test and helper needs to be clearly

    assigned to some team so in case of issues the team can be reached. Ladislav Prskavec - HiveTalks, 9.1. 2019 21
  7. 2. Maintenance There's a team responsible for every test, so

    flaky and long running tests can and should be a part of the sprint work. Ladislav Prskavec - HiveTalks, 9.1. 2019 22
  8. 4 How long are people waiting for CI results? 4

    Can you run your tests in parallel? 4 Can you add 10 developers into team and time to deploy will stay the same? 4 How much does your build infrastructure cost? 4 Do you have budget for build/test infrastructure? Ladislav Prskavec - HiveTalks, 9.1. 2019 26
  9. Operations costs 4 SaaS (Circle, flat fee: $50 per container,

    dedicated support) 4 OnPremise (Jenkins master + workers) 4 Hybrid (Wercker, use managed K8S cluster for workers) 4 Combinations (JenkinsX, Gitlab, ...) Ladislav Prskavec - HiveTalks, 9.1. 2019 31
  10. Summary 1. Fast 2. Reliable 3. Scalable 4. Maintenance costs

    5. Monitoring Ladislav Prskavec - HiveTalks, 9.1. 2019 32