Sie sind auf Seite 1von 3

https://www.youtube.com/watch?

v=7z5CGnnTu-Y (What is Continuous Integration - Why


should we need this - Software Product Delivery)
CI Automates the process of building,testing and reporting.
https://www.youtube.com/watch?v=HnWuIjUw_Q8&list=PLYcy44QqzleK37bEsG5Jh9RQDmUaBoMra
(Continuous Integration/Delivery /Deployment101 (Part 1))
https://www.youtube.com/watch?v=buXwBr9H3VY (Intro to Continuous Integration (CI))
https://www.youtube.com/watch?v=h8mDVFp6UjU&t=3s (Continuous Integration - Why ?
What ? How ?)
https://www.youtube.com/watch?v=_zCyLT33moA (What is Continuous Integration?)
https://www.youtube.com/watch?v=xSv_m3KhUO8 (Professional Guides: Continuous
Integration Continuous Delivery)
https://www.youtube.com/watch?v=L5oesoeZ_iY&t=1s (DevOps Demo on CI, CD, CT &
Infrastructure as code - VirtusaPolaris)
https://www.youtube.com/watch?v=SzkyKpkGI6A (Automated Build System Part 4:
Scripting Jenkins)
https://www.youtube.com/watch?v=Ge7Mi4-lOVI (Continuous Delivery with Jenkins
Workflow and Docker Explained)
https://jenkins.io/doc/book/pipeline/multibranch/

http://scmquest.com/continuous-integration-vs-continuous-delivery-vs-continuous-
deployment/
Continuous Integration involves triggering a build when a change gets committed to
the source code repository by any developer. which includes, fetching the code from
source code repository, compiling code, running automated tests and creating build
out of it.This will help to detect any integration error at earliest and gives a
full visibility of the project code.
Continuous Integration creates build after running automated test for every commit.
Less frequent changes means troubleshooting will consume less time in case of any
issue.
CI’s biggest advantage is reduction of risk. All the issues can be easily
identified and fixed with each integration.CI definitely makes everyone’s life
easier by making software build rapidly and simple to find bugs which allow
developers to fix them promptly. It will helps users to save their money, time &
efforts.

Continuous delivery is a software engineering discipline that allows organizations


to consistently develop and release quality software at a rapid pace. It is
achieved by automating the software development lifecycle, enabling tasks such as
development, testing and release to occur concurrently and continuously.

Continuous integration is the practice of constantly merging development work with


a Master/Trunk/Mainline branch so that you can test changes and test that those
changes work with other changes. The idea here is to test your code as often as
possible so you can catch issues early on. In the continuous integration process,
most of the work is done by an automated tests technique, which requires a unit
test framework. It is best practice to have a build server designed specifically
for performing these tests so your development team can continue merging requests
even while tests are being performed.

In Agile software development the ultimate goal is to deploy working software to


end-users (customers) as quickly as possible, often in 2-week increments…
In today’s environment, there is the concept of a “build pipeline” which represents
the steps to move new code from development into production.
The basic steps in the build pipeline are:

1. Develop code
2. Unit test (test the code locally to ensure it works as expected)
3. Integrate (the new code into the existing code base)
4. Acceptance test (test the entire system to ensure it meets the users
expectations)
5. Deploy to production

Following the entire process – DevOps – ensures that developers can keep up with
the demands of the business to accelerate time to market

Continuous Integration is part of these workflows in that it’s the process that
your team uses to validate that the code base is in a healthy state by running your
automated testing suite. It’s the validation step when your developers add new
features and make updates to ensure they didn’t break existing functionality.
Regardless of your deployment strategy, this is the key ingredient to a healthy
software development recipe.

https://www.youtube.com/watch?v=1xo-0gCVhTU (Introduction to Microservices, Docker,


and Kubernetes)
https://www.youtube.com/watch?v=Zed6udTPGro (How to Design Microservices
Architecture? Uber Architecture - A Case Study | Tech Primers)
https://www.youtube.com/watch?v=WFtmCaqIjkA (Microservices vs APIs)
https://www.youtube.com/watch?v=rlS9eH5tEnY (Designing Microservices using Spring
Boot, Spring Cloud, Eureka and Zuul | # 1 | Tech Primers)
https://www.youtube.com/watch?v=ifBFwH59gGA (Designing Microservices using Spring
Boot, Spring Cloud, Eureka and Zuul | #2 | Tech Primers)
https://www.youtube.com/watch?v=g91lFo8OTDY (Spring Cloud Tutorial - Netflix Zuul +
Eureka Simple Example)
https://www.youtube.com/watch?v=Bcs-inRnLDc (Spring Boot Micro-services,
Containers, and Kubernetes - How To)

Chrome tabs 21 Feb


https://www.tektutorialshub.com/angular2-architecture-overview-concepts/
http://blog.mgechev.com/2016/04/10/scalable-javascript-single-page-app-angular2-
application-architecture/
https://en.wikipedia.org/wiki/Software_design_pattern
https://www.sitepoint.com/react-vs-angular/?utm_source=hashnode.com
https://www.google.co.in/search?
q=hudson+tutorial&oq=hudson&aqs=chrome.5.69i57j69i60l2j69i59j69i60j69i59.6236j0j7&s
ourceid=chrome&ie=UTF-8
https://www.google.co.in/search?
q=what+is+continuous+integration&oq=what+is+continous+i&aqs=chrome.1.69i57j0l5.5762
j0j7&sourceid=chrome&ie=UTF-8
https://www.google.co.in/search?
q=agile&stick=H4sIAAAAAAAAAONgFuLUz9U3MC0rK6xUAjONqjKS8rT4nPNzc_PzgjNTUssTK4sBpYryF
igAAAA&sa=X&ved=0ahUKEwiHr--NobHZAhUFm5QKHedmAbQQxA0IjwIwGw
https://stackify.com/continuous-delivery-vs-continuous-deployment-vs-continuous-
integration/
https://www.nwcadence.com/blog/continuousintegration-continuousdelivery
https://devops.com/continuous-integration-vs-continuous-delivery-theres-important-
difference/
https://www.quora.com/What-is-the-difference-between-continuous-integration-and-
continuous-deployment
http://scmquest.com/continuous-integration-vs-continuous-delivery-vs-continuous-
deployment/
http://blog.wercker.com/what-is-ci-and-cd
http://www.saviantconsulting.com/blog/difference-between-continuous-integration-
continuous-delivery-and-continuous-deployment.aspx
https://www.google.co.in/search?
q=continuous+integration&source=lnms&tbm=isch&sa=X&ved=0ahUKEwjh77PAs7HZAhVBjZQKHVy
ZAGcQ_AUICigB&biw=1366&bih=672
https://stackify.com/continuous-delivery-vs-continuous-deployment-vs-continuous-
integration/
https://www.youtube.com/results?search_query=continuous+integration
https://www.youtube.com/watch?v=hQ0recUXk9o
https://www.youtube.com/watch?v=Ijs55IA8DIk
https://www.youtube.com/watch?v=BLMs_NITgSw

Das könnte Ihnen auch gefallen