18 Lecture Flashcards
What is continuous integration
- Continuously integrate
- Continuously build
- Continuously test changes to find regression
What is continuous delivery
- Continuously release
- Continuously beta test application with customer
- Quickly obtain feedback -> short development feedback cycles
What is release management?
workflows activities and best practices how and when to create releases
What is the goal of release management?
To automate as many steps as possible
What is continuous deployment
every change that passes the automated tests is deployed automatically
What is continuous software engineering?
develop, release and learn from software in short cycles
What are the responsibilities of a release manager?
Facilitator:
- a connection between different business units
- promotes smooth and timely delivery of products
Coordinator:
- coordinates source trees, projects, teams and components
What is DevOps
When development and operations are working together
What is the difference between continuous deployment and continuous delivery
In continuous deployment the step deploy to production is automated
What are the benefits of continuous delivery
+ Faster time to market
+ Helps to build the right product
+ Improves productivity and efficiency
+ Reduces risk of a release failure
What are the challenges of continuous delivery
- Varying interests in different departments of an organization
- Traditional processes hinder continuous integration
- Maintainability of the source code & tailorable delivery workflows for heterogeneous project environments
What are the tasks of the continuous delivery server?
- Distributes software to customers
- Obtains user feedback
- Collects crash reports
- Stores feedback and crash reports in an issue tracker
What are the release notes?
Release notes describe the most important changes of the product since the last release
Name 3 management issues with continuous delivery
- How often do you deliver your application
- How do you handle customers that do not react to releases
- How do you handle feedback within the sprint
- How many releases can a customer / user handle
What is best practice for build and release management?
- The process must be repeatable and reliable
- Every step of the process should be automated
- Release early and often to obtain feedback
- React to crashes and user feedback
=> Improve continuously
