Cruise Training Introduction of Continuous Integration.

Slides:



Advertisements
Similar presentations
Michael Lepine Agile2013 Recap. What is DevOps?
Advertisements

Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Nine Steps to Delivering Defect-Free Software By: Terence M. Colligan Presented by: Isaac Bailey.
Roadmap to Continuous Integration Testing and Benefits Gowri Selka, Walgreens Natalie Koltun, Walgreens May 20th, 2014 ©2013 Walgreen Co. All rights reserved.
Cruise Training Introduction of Cruise. What you’ll learn Cruise features Pipeline workflows Zero-configuration build grid Parallelization Usability-driven.
What is workflow?  A workflow is a structured way of defining and automating structures and procedures within an organization. What is workflow management.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
Continuous Integration for OpenEdge Applications NameDivyaTheja Pachipula TitleSenior Engineer Date8 th June, 2015.
Agile Testing with Testing Anywhere The road to automation need not be long.
/t/ / I d/ /d/ Try Again Go on /t/ / I d/ /d/
Improving Software Quality with Continuous Integration
Continuous Integration for Databases Learn how to automate your build and test Steve Jones Red Gate Software Part II of the Continuous Delivery for Databases.
Introduction to Continuous Integration Mike Roberts.
Wellcome Trust Centre for Gene Regulation & Expression College of Life Sciences, University of Dundee Dundee, Scotland, UK Continuous Integration 0.
By John Boal  Continuous Integration [CI] ◦ Automating the build process ◦ Build the entire system each time any new.
CONTINUOUS DELIVERY / CONTINUOUS INTEGRATION. IDEAS -> SOLUTIONS Time.
CONTINUOUS INTEGRATION, DELIVERY & DEPLOYMENT ONE CLICK DELIVERY.
Continuous Delivery Ajey Gore Head of Technology ThoughtWorks India.
Visually Execute Your Strategy. The Disconnect  2014 KPI Fire2 Strategic Goals KPIs Projects Poor Results.
© 2012 IBM Corporation Rational Insight | Back to Basis Series SCM introduction Chu Shu June 2012.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Craig Berntson
Sumedha Rubasinghe October,2009 Introduction to Programming Tools.
By Touseef Tahir Software Testing Basics. Today's Agenda Software Quality assurance Software Testing Software Test cases Software Test Plans Software.
Branching. Version Control - Branching A way to write code without affecting the rest of your team Merge branches to integrate your changes.
4/23/ :45 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.
Continuous Processes By Kelvin Zhu CSCI577B Spring 2013.
Continuous Deployment JEFFREY KNAPP 8/6/14. Introduction Why is it valuable How to achieve What to consider.
Code and Asset Branching Best Practices Session 315 Philip Wolfe, Lead Developer Farm Credit Services of America.
Perforce Software Version Everything.. Visual Studio Industry Partner Perforce Software NEXT STEPS Contact us at: Perforce products.
Confidential Continuous Integration Framework (CIF) 5/18/2004.
Anubha Gupta | Software Engineer Visual Studio Online Microsoft Corp. Visual Studio Enterprise Leveraging modern tools to streamline Build and Release.
1 Copyright © 2015, Drilling Info, Inc. All right reserved. All brand names and trademarks are the properties of their respective companies. Webinar Series.
CONTINUOUS DELIVERY OF MICROSERVICES Ken Mugrage
Continuous Integration CruiseControl.Net. Best Practices Use version control; Automate the build; Build should be self tested; Developers must commit.
Build automation. Prerequisites for Continuous Integration (CI)  Version Control System  Build automation  Notification on build result sent to related.
(1) Introduction to Continuous Integration Philip Johnson Collaborative Software Development Laboratory Information and Computer Sciences University of.
(1) Introduction to Continuous Integration Philip Johnson Collaborative Software Development Laboratory Information and Computer Sciences University of.
Software Testing Process
Build and Deployment Process Understand NCI’s DevOps and continuous integration requirements Understand NCI’s build and distribution requirements.
Ahmed Idris Tahir Waseel Application Service Provider.
CERN IT Department CH-1211 Genève 23 Switzerland t Migration from ELFMs to Agile Infrastructure CERN, IT Department.
ITM 353 Final Project Demos. Your Last Assignment There’s one more fun presentation in store for you all: the Transition Readiness Review (TRR) aka your.
Continuous Integration for Databases Steve Jones SQLServerCentral Red Gate Software.
1 Punishment Through Continuous Delivery If it hurts, do it more often…
Benjamin Day Get Good at DevOps: Feature Flag Deployments with ASP.NET, WebAPI, & JavaScript.
ALM Deployment Pipeline Implementation. Create a Repeatable, Reliable Process for Releasing Software. Automate Almost Everything Keep Everything in Version.
1 © Agitar Software, 2007 Automated Unit Testing with AgitarOne Presented by Eamon McCormick Senior Solutions Consultant, Agitar Software Inc. Presented.
Automated Build and Test
Implementing Cloud-based Agile Team Development - Lessons Learned
Essential Needs of Software Test Automation
Continuous Delivery- Complete Guide
Tribes, Squads, Chapters & Guilds
Lessons learned and proposals Sylvain Desbureaux, Morgan Richomme
An Intro to ALM Using TFS and Visual Studio for Source Control, Build Automation, Continuous Integration and Deployments.
Beijing S3P test strategy Eric Debeau, Sylvain Desbureaux, Morgan Richomme December 12, 2017.
Introduction to Software Engineering
Continuous Integration and Continuous Delivery ( Dev-Ops ) - Fortunesoft
Continuous Integration For Databases
X in [Integration, Delivery, Deployment]
Get Good at DevOps: Feature Flag Deployments with ASP
Continuous Delivery good & bad 4/20/2012
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
Your code is not just…your code
Continuous Integration
Continuous Integration Tool
Node.js Test Automation using Oracle Developer Cloud- Simplified
Utilizing CI environment for efficient and effective testing of NFRs
Your code is not just…your code
Presentation transcript:

Cruise Training Introduction of Continuous Integration

What you’ll learn Problems around software development Why those problems happen again and again What is Continuous Integration What’s the benefits we can get Key practices to CI Introduction of Cruise / Cruise Control

Question When you finished the dev tasks in a project, can you answer the question: When can you deploy to the production? o How long is the integration? o Will QAs found lots of bugs after integration? o How long it take to fix the bugs and integrate again? o How many round of the process dev -> integration -> qa -> dev will be?

Problems Problems around software development o Integration is a long and unpredictable process  No real idea of how long the integration would take  Need to fix bugs found during the integration and do it again o Slow to deliver a new feature o Bugs in deployed software

Problems: Why those problems happen again and again?

Continuous Integration: What it is a software development practice team members integrate their work frequently be verified by an automated build

Continuous Integration: What it is

Continuous Integration: What it is not Not a tool to avoid bugs (but provide fast feedback to help detect bugs) Not a tool magically make your life auto (but drive automated process to make up effective CI)

Continuous Integration: Benefits Integration is fast you know where you are, what works, what doesn't, the outstanding bugs you have Easy to find bugs and fix them Fast to deliver a new feature

Continuous Integration: Key practices Get everything you need into source control Get the build automated Introduce some automated testing into you build Try to speed up the commit build Make it easy to get the latest executable Everyone can see what's happening

Cruise Control: Born of Cruise ThoughtWorks developed the CruiseControl in 2000 The latest version is release on 12 Jan 2009

Cruise Control: Grow up to Cruise Cruise Control focused on development, and lacks features to support modern development o Workflows o Build Grid o Parallelization o Central Artifacts o Security

Summary Problems around software development Why the problems happening again and again What is Continuous Integration What’s the benefits we can get Key practices to CI Introduction of Cruise / Cruise Control

Questions

Thanks