A software development life cycle through Devops.where the process could consume lots of days is reduced into hours using automation

1. Presentation on:
SCALABLE CONTINUOUS INTEGRATION AND
CONTINUOUS DEPLOYMENT
BY
G R VISHAL
SUBRAMANYA DATTA SPOORNIMA Y O
HARSHITHA S

2. INTRODUCTION
CI-CD is an approach ensures every commit to the system is
releasable, increases delivery frequency and gets faster feedback to
developers on the code being delivered. CI-CD is the chain of scalable
events assures the quality, safety and security of the product.
Quality and Time-To-Market (TTM) are crucial factors for the
success of any software product. This can be achieved with
Continuous integration and Continuous deployment (CI-CD) by
using various ‘Development-Operations’ (DevOps) tools.

3. Literature Survey
TITLE YEAR AUTHOR REMARKS
DevOps, A new Approach to cloud
development and testing
2019 Prashant Agrawal DevOps with cloud computing projects
focuses on speed-to-delivery of
application development so that
business needs meet faster with
lowering the cost of development,
operations, testing and deployment.
Continuous and Integrated Software
Development using DevOps
2018 Aayush Agarwal Communication gap between Dev and
Ops for manual code review
Adopting Continuous Integration
and Continuous
Delivery for Small Teams
2019 Moutaman Kamal Aldeen
Abbass
Implementing CI/CD in small teams can
be difficult due to various problems. but
the most important problem is that it’s
time consuming for small tests, but with
the concept of micro-pipelines it can
reduce this time consumption
radically.

4. Software delivery process without Devops at place

5. Existing System
Task Time in days(per 1 resource)
Installing different software set on 100 different
machines.
2
Monitoring services and capacity of all servers 1
Checking the quality of the software
- Manual verification of the results.
1
Running the tests on 100 machines without auto scale 2
Get product statistics from various sources, collect all
test results, validate them and consolidate all this
information into one.
2
In practice, any human error leads to further delay, which is omitted from the above estimation chart.

6. Disadvantages of Existing System
Existing systems either did not adapted DevOps or not using DevOps framework to its full potential. Below
statistics leads to:
Delay in the Time To Market of the
product.
Product security.
VulnerabilitiesQuality of the product.
Prone to human errors

7. Proposed solution
Bringing 7 days of labor to 1 day is possible with the best use of various DevOps technologies and tools available in the industry
under one umbrella. Our ‘Scalable CI-CD using Devops addresses different stages of problem statement is described below:
Problem Statement Proposed solution
 Deliver the features developed into source archive, from
different teams across the globe.
 Use ‘Git’ as source archive, where teams across the globe can
deliver the changes at any time.
 Test the quality of the code via unit tests, integration and
automated tests. (Testability, maintainability, scalability and
security aspects to be covered).
 Use Nunit, Mstest, Jmeter to run unit/automated tests.
 Test across different environments (different Operating
systems, browsers and software set combination).
 Use Virtual machines (VMs) with AWS-cloud combination
to pull various operating systems to host different sets. This
technology is new to the industry. This is scalable on need
basis, can be programmatically created as many VM’s as
required to complete activities in stipulated time.
 Promote the software product to release state  Check the quality history of the product and automatically
push software to the repositories, from which user can
directly download it.

8. Software delivery with DevOps

9. Softwares used
PROGRAMMING
LANGUAGE & IDE
TESTING
FRAMEWORK
BUILD TOOL
VERSION CONTROL
SYSTEM
CLOUD COMPUTING
PLATFORM SCRIPTS USED
PACKAGE
MANAGER
AUTOMATION
SERVER

10. METHODOLOGYDevelopers
Version Control
BUILD
Test
Automation
Deploy

11. Implementation

12. Software flow in the pipeline
Pipeline broken when tests
are failed/skipped.
Pipeline broken when
build fails
Software published when
right quality is met

13. Screen Shots
1.GitHub Repository

14. 2. AWS Instances View

15. 3.Jenkins Nodes View

16. 4.Git Bash Terminal

17. 5. Jenkins Pipeline View

18. 6. Nodes created on
demand – Jenkins view

19. 7. Nodes created on
demand – AWS view

20. 8.Jenkins Console log

21. 9.Package Registry where software can
be downloaded by customers

22. Advantages
In abstract view the CI-CD pipeline setup with DevOps tools brings in below into the development practices.
Infrastructure as a code
Monitoring and Visibility
AutomationContinuous deployment

23.  A software industry without DevOps setup is unimaginable. Setting up CI-CD
pipeline is bringing in various heterogeneous tools together and getting the best
out of it to achieve the high-quality product with quickest possible time to the
market. Our proposed solution is generic in nature, address the core issues in
product development-delivery lifecycle and suits any organization at any scale.
 DevOps is the way to make both developers and customers happy.
Conclusion

24. Future Enhancement
Dashboard Emails via Jenkins

25. Use Of Docker
Containerization
Configuration
Management

26. Companies Using fully fledged DevOps

27. References
[1] https://dzone.com/articles/focus-on-cicd?fromrel=true
[2] https://cloudtweaks.com/2019/05/devops-secure-and-scalable-ci-cd-pipeline-with-aws/
[3] https://github.com
[4] https://signin.aws.amazon.com
[5] https://www.google.com/
[6] https://www.jenkins.io/
[7] https://github.com/features/packages
[8] https://visualstudio.microsoft.com/
GitHub Repository URL : https://github.com/vishalgr/DEVOPS_test.git