Guru-Campinas - Continuous integration

2,870 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,870
On SlideShare
0
From Embeds
0
Number of Embeds
1,594
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \n
  • a development methodology \nof daily developer integrations \nverified by automated builds\n
  • nightly builds \ndeveloper branches \nscheduled Integration Points\nbuilding via IDEs\n
  • \n
  • - Arrumar bugs no futuro eh mais caro\n- Code base isn`t up-to-date\n- qualidade do codigo - se demorar fazer integracao, pode ter codigo duplicado\n- dificuldades de merge\n-mais rapido (teste em paralelo, o tempo todo e nao apenas no final, nao precisa esperar aquele CARA da build, q demora 2dias para fazer uma build ), mais barato(encontre bugs mais cedo)\n
  • deixar para depois sai caro e $ eh jogaado no lixo\n
  • \n
  • encontrar bugs antes eh mais barato\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • quem nunca trabalhou em um projeto onde o chefe sempre pede um demo e qd vc vai fazer o deploy para o servidor de testes, td pára!?\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Nao dependa de IDE para fazer a build\nuse bash, ant , ferramentas q ajudam a escrever scripts para deploy\nnao use cron para rodar suas builds, poll tds os commts\n
  • Guru-Campinas - Continuous integration

    1. 1. Continuous IntegrationIm prove you r so ft wa re q ua li ty a n d re duce ri sk s
    2. 2. WHAT IS CI?
    3. 3. WHAT IS NOT CI?
    4. 4. ContinuousCompilation !=ContinuousIntegration
    5. 5. WHY?
    6. 6. http://www.the-vibe.co.uk/2010/07/14/our-money-why-we-deserve-to-know-how-much-mark-elms-earns/ http://laborunionreport.blogspot.com/2009/11/as-union-bosses-spend-money-its-members.html
    7. 7. Merge may hurt http://martinfowler.com/bliki/FeatureBranch.html
    8. 8. http://www.flickr.com/photos/alexanderamatosi/3307101812/sizes/l/
    9. 9. WHAT IS BUILD?
    10. 10. Build is...Database integrationCompilationTest executionCode inspectionAutomated deployment
    11. 11. Build Types
    12. 12. Programmer
    13. 13. Teamhttp://www.flickr.com/photos/atomicshed/161716498/sizes/l/
    14. 14. Customerhttp://www.flickr.com/photos/jeff-bauche/2230236391/sizes/z/
    15. 15. Improving quality
    16. 16. Automated testsAutomated builds
    17. 17. https://bethelnet.bethel.edu/security-safety/safety/procedures-fire
    18. 18. Reducing Riskshttp://www.flickr.com/photos/lesec/449700279/sizes/o/
    19. 19. Commit early,Commit often
    20. 20. Never Commit broken code
    21. 21. Fix build failures immediately
    22. 22. Fail Fast
    23. 23. Create artifactsfrom every build
    24. 24. do NOT forget...
    25. 25. keep buildsin the green
    26. 26. Continuous Integration #ft w
    27. 27. Obrigado :-)
    28. 28. @albertolealalbertonb@gmail.comwww.albertoleal.eti.br

    ×