Integração Contínua com containers Docker. Fabricio

Transcrição

1 Integração Contínua com containers Docker Fabricio

2 Agenda Stacks Continuous Integration Docker Dockerize Continuous Integration Docker + Jenkins

3 Devtools

4 Stacks

5 Stacks

6 Stacks

7 Stacks

8 Stacks

9 Stacks

10 Stacks

11 Stacks

12 Stacks

13 Stacks

14 Continuous Integration Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. -- Martin Fowler

15 Continuous Integration Maintain a code repository Automate the build Make the build self-testing Everyone commits to the baseline every day Every commit (to baseline) should be built Test in a clone of the production environment Make it easy to get the latest deliverables Everyone can see the results of the latest build Keep the build fast Automate deployment

16 Continuous Integration Maintain a code repository Automate the build Make the build self-testing Everyone commits to the baseline every day Every commit (to baseline) should be built Test in a clone of the production environment Make it easy to get the latest deliverables Everyone can see the results of the latest build Keep the build fast Automate deployment

17 Continuous Integration Maintain a code repository Automate the build Make the build self-testing Everyone commits to the baseline every day Every commit (to baseline) should be built Test in a clone of the production environment Make it easy to get the latest deliverables Everyone can see the results of the latest build Keep the build fast Automate deployment

18 Continuous Integration Maintain a code repository Automate the build Make the build self-testing Everyone commits to the baseline every day Every commit (to baseline) should be built Test in a clone of the production environment Make it easy to get the latest deliverables Everyone can see the results of the latest build Keep the build fast Automate deployment

19 Continuous Integration Maintain a code repository Automate the build Make the build self-testing Everyone commits to the baseline every day Every commit (to baseline) should be built Test in a clone of the production environment Make it easy to get the latest deliverables Everyone can see the results of the latest build Keep the build fast Automate deployment

20 Continuous Integration Maintain a code repository Automate the build Make the build self-testing Everyone commits to the baseline every day Every commit (to baseline) should be built Test in a clone of the production environment Make it easy to get the latest deliverables Everyone can see the results of the latest build Keep the build fast Automate deployment

21 Continuous Integration Maintain a code repository Automate the build Make the build self-testing Everyone commits to the baseline every day Every commit (to baseline) should be built Test in a clone of the production environment Make it easy to get the latest deliverables Everyone can see the results of the latest build Keep the build fast Automate deployment

22 Continuous Integration

23 Continuous Integration

24 Continuous Integration

25 Continuous Integration

26 Continuous Integration

27 Continuous Integration

28 Continuous Integration

29 Continuous Integration

30

31 Docker

32 Docker

33 Docker

34 Docker PRODUCTION READY??

35 Docker

36 Docker

37 Docker

38 Dockerize Continuous Integration

39 Dockerize Continuous Integration

40 Dockerize Continuous Integration

41 Dockerize Continuous Integration

42 Dockerize Continuous Integration

43 Dockerize Continuous Integration

44 Dockerize Continuous Integration

45 Dockerize Continuous Integration

46 Dockerize Continuous Integration

47

48

49 empacotamento de aplicações Docker + Jenkins = Amor build.sh $FPM_OPTS FPM

50 empacotamento de aplicações Docker + Jenkins = Amor Especialmente útil para linguagens que sem facilidades para empacotar Desacoplamento entre a aplicação e o ambiente Script de empacotamento no controle de versão Container precisa de acesso ao workspace Nem sempre é a melhor solução Cuidado com a arquitetura em que ocorre o empacotamento Sem conflito entre dependências

51 Docker + Jenkins = Amor teste e análise uniformes

52 Docker + Jenkins = Amor teste e análise uniformes Ideal para ambientes de CI com mutas necessidades diferentes Liberdade na escolha da sua pilha de testes Ambiente de integração contínua organizado Fácil reprodução e manutenção do ambiente de testes Container precisa de acesso ao workspace CI Server precisa ter permissão pra manipular artefatos É uma caixa preta se os devs não conhecerem Docker Manutenção do Docker host Código de execução dos testes no controle de versão

53 Jenkins slaves com containers Docker + Jenkins = Amor

54 Jenkins slaves com containers Docker + Jenkins = Amor Funciona bem para casos onde não há ambiente sob demanda Mais rápido do que usar VMs Escala facilmente com muito jobs Permite usar containers como artefatos de build Documentação escassa Cada job necessita de uma imagem cadastrada Volumes para os caches de dependências Container precisa de acesso ao workspace CI Server/Container precisa ter permissão pra manipular artefatos

55 Docker + Jenkins = Amor testes de integração

56 Docker + Jenkins = Amor integração contínua de cookbooks driver_plugin: docker driver_config: socket: tcp://docke.host:5000 dockerfile: test/dockerfile

57

58 @lonefreak