CS314 Software Engineering Continuous Delivery - Colorado State University

20d ago
13 Views
0 Downloads
1.31 MB
7 Pages
Last View : Today
Last Download : n/a
Upload by : Milo Davies
Transcription

11/15/18 CS314 Software Engineering Continuous Delivery Dave Matthews How long does it take your team to deploy a change that involves a single line of code? And do this on a reliable, repeatable basis? Continuous Delivery: , Jez Humble and David Farley, 2011 1

11/15/18 Cycle Time is the key metric Time from deciding that you need to make a change to having it in production Years? Months? Weeks? Days? Some teams achieve a cycle time of hours or minutes Continuous Delivery: , Jez Humble and David Farley, 2011 Continuous Delivery Agile - deliver early and continuously. First release is the just the beginning and contains the minimum amount of functionality Majority of cost occurs after first release in the form of maintenance, support, new features and defect fixes Continuous Delivery: , Jez Humble and David Farley, 2011 2

11/15/18 Continuous Delivery Build - Deploy - Test - Release Releases become routine – Ideas rapidly turn into delivered code – Deliver more frequently with less stress Adds the last mile to Continuous Integration – turn integrated code into production software – more automation, done quickly without error – involves separate Dev Ops teams Continuous Delivery: , Jez Humble and David Farley, 2011 Continuous Delivery Principles Create a repeatable, reliable process for releasing software Automate almost everything Keep everything in version control If it hurts, do it more frequently, and bring the pain forward Build quality in Done means released Everybody is responsible for the delivery process Continuous Improvement 3

11/15/18 Deployment Pipeline Every change creates a new instance of the pipeline. Every change is a release candidate. Done means released. No alpha - beta- . - gold Continuous Delivery: , Jez Humble and David Farley, 2011 Configuration Management Keep absolutely everything in version control Check in regularly to master Use meaningful commit messages Manage external libraries Manage components Manage application configuration Manage your environments Continuous Delivery: , Jez Humble and David Farley, 2011 4

11/15/18 Testing Strategy Continuous Delivery: , Jez Humble and David Farley, 2011 Continuous Integration Don't check in on a broken build Always run all commit tests locally before committing, or get your CI server to do it for you Wait for commit tests to pass before moving on Never go home on a broken build Always be prepared to revert to the previous version Time box fixing before reverting Don’t comment out failing tests Take responsibility for all breakages resulting from your changes Test-Driven Development Continuous Delivery: , Jez Humble and David Farley, 2011 5

11/15/18 Continuous Improvement Optimize the whole process, not just the parts – – – – – – Configuration Management Automated Testing Continuous Integration and Deployment Data Management Environment Management Release Management Increase feedback and improve collaboration between development, testing, and dev ops teams Continuous Delivery: , Jez Humble and David Farley, 2011 Other Metrics as Diagnostics Automated test coverage Codebase properties - complexity, duplication, coupling, Number of defects Velocity Number of commits, builds, build failures per day Duration of builds, automated tests Continuous Delivery: , Jez Humble and David Farley, 2011 6

11/15/18 Theory of Constraints Identify the limiting constraint in your process (bottleneck) Exploit the constraint (maximize the throughput for that part of the process - 100% utilization) Subordinate all other processes to the constraint (less emphasis on other parts of the process) Elevate the constraint (increase resources, investment) Find the next constraint and repeat Continuous Delivery: , Jez Humble and David Farley, 2011 7

Continuous Delivery: , Jez Humble and David Farley, 2011 Continuous Delivery Agile -deliver early and continuously. First release is the just the beginning and contains the minimum amount of functionality Majority of cost occurs after first release in the form of maintenance, support, new features and defect fixes

Related Documents:

Agile and Continuous Delivery Oracle Confidential – Restricted Continuous Delivery: frequent releases of new software through the use of automated testing and continuous integration. Continuous integration continuous delivery continuous deployment code label branch(es) p

continuous integration and continuous delivery of the software was achieved as shown in fig 4. ACKNOWLEDGEMENT. I would like to express our gratitude to our guide for guiding us in each step Sowmya Nag Kof project. CONCLUSIONS AND FUTURE SCOPE . Continuous integration and continuous delivery is an ideal scenario for application teams in an .

CS 314 Software Engineering Chapter 0 Slides: Course Description Spring 2016 James M. Bieman Colorado State University 0-3 CS 314 Colorado State University Copyright .

Basic flow of the Continuous Integration & Delivery service 1. A developer pushes code changes into a central source code management system (SCM). 2. The SCM triggers an event to which SAP Cloud Platform Continuous Integration and Delivery reacts. 3. The Continuous Integration & Delivery service tests, builds, and deploys the code changes and .

Materials Science and Engineering, Mechanical Engineering, Production Engineering, Chemical Engineering, Textile Engineering, Nuclear Engineering, Electrical Engineering, Civil Engineering, other related Engineering discipline Energy Resources Engineering (ERE) The students’ academic background should be: Mechanical Power Engineering, Energy .

Continuous delivery Continuous delivery is a software development practice where software is always in a releasable state. It allows organizations to rapidly deploy enhancements and fixes when needed. Continuous delivery relies on automated testing and deployment as well as good collabor

DevOps lifecycle: 1. Continuous Development 2. Continuous Testing 3. Continuous Integration 4. Continuous Deployment 5. Continuous Monitoring 1. Continuous Development This is the phase that involves planning and coding of the software application's functionality. There are no tools for planning as such, but there are several tools for

Weight of pile above scour level Wp1 220.893 kN Weight of pile below scour level Wp2 301.548 kN Tota l ultimate resistance of pile Qsf Qb – Wp2 8717.452 kN Allowable load (8717.452 / F.S.) – Wp1 3266 kN. From above calculations, Required depth 26.03m below design seabed level E.G.L. ( ) 1.15 m CD . International Journal of Engineering Trends and Technology (IJETT) – Volume .