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

Building a Jenkins Continuous Integration Pipel...

Building a Jenkins Continuous Integration Pipeline with Docker

Alexandru Zbarcea

October 19, 2016
Tweet

More Decks by Alexandru Zbarcea

Other Decks in Technology

Transcript

  1. Automated Service Operations App App Vault Nexus Internal on-premise services

    Customer facing services github Continuous Integration Pipeline
  2. rhel tomcat java app Another Distro One package manager -

    automated patches Reuse Isolated app. One hierarchy security Conf. Mngt.
  3. Artifacts .jar .war .npm .pip .apk .deb .rpm .docker .-box.tar.gz

    .git - Chef - Ansible - .docker compositions - Pods .wiki .swagger.json apps/libs OS node config. docs .docker .docker compositions .rancher compositions only markdown (text) artifacts are allowed
  4. Pipeline Challanges - everybody sees and understands the pipeline -

    optimize for the global scope - inventory of INs and OUTs - artifact warehouse management - containerize everything
  5. - Not all image can be build in docker-in-docker (dind)

    - Caching artifacts (e.g.: /.m2/repository folder) - Use data containers Docker Challanges
  6. Operations Challenges - FAIL is good. Trust the upgrade button

    - complexity - generates: lack of trust - difficult to investigate - .git/social becomes a core system - emergent properties - focus is on scaling - deployments as a non-event