Big Bang Integrations

• We represent a company called as lt infotech. This organization is building a food delivery application
• We have different teams who are working in isolation
• Approach
  • Each team will work in isolation for 8 months and finish development
  • On the first day of 9th month we will start integrating and test the application
• This approach is called as Big Bang integration
• This almost fails all the time
• Generally to fix issues most of the teams go for workarounds

Continuous Integration

• We represent a company called as lt infotech. This organization is building a food delivery application
• Approach:
  • From day 1 all the teams need to integrate their work
  • Accept failures and plan for proper fixes rather than technical debts
• Integration was majorly done manually, so this needs to be replaced with automated tools
• Integration approach:
  • Whenever a new change is done in any part of the system
  • build the code
  • test the integration with automated tests
  • publish the results
• Developer will have the feedback of his changes
• To work with continuous integration we need
  • A tool which builds the code
  • A tool which runs the tests
  • A tool which which notifies the users via email or … about failures and success.
• tools ():
  • Cruise Control for CI
  • Makefile for building the code

Version Control Systems

• Version Control System is a software for maintaining Code. It is basically a source code repository
• Generations:
  • Single System Version Control
  • Client Server Version Control
    
  • Distributed Version Control

Terms

• Repository
  • Source Code Repository
    • Git
  • Artifact Repository
    • Jfrog
• Artifact
• Quality Gate
• Promotion