Continuous Integration: Blueprint, Toolbox, Master Craft

•Download as PPTX, PDF•

0 likes•7,827 views

The practice of continuous integration (CI) has the ability to transform software development from a set of manual processes to a logical series of reproducible, automated processes. There are three concepts that are key to continuous integration; the blueprint, the toolbox, and the master craft. This session presents the CI lifecycle as a blueprint. You will see and understand the series of development processes that establish an effective, automated progression from source code to a packaged deliverable. You will learn about the CI server, which is the fundamental tool that initiates, performs, coordinates, and reports throughout the CI phases. The toolbox includes both the CI server and the combination of technologies that support CI. Continuous integration is a master craft of Agile engineering. To help you be effective with continuous integration, this talk demonstrates both the knowledge and skills needed to achieve the desired results of CI and to maximize its value.

Technology

Continuous Integration:
Blueprint, Toolbox, Master Craft

DC .NET Users Group (@DCDNUG) Stephen D. Ritchie
February 2013 Meeting
@RuthlessHelp
Feb 19, 2013

Stephen D. Ritchie – Managing Consultant – Excella Consulting, Inc., 2300 Wilson Blvd, Suite 630, Arlington, VA 22201 – 703.840.8600 – http://excella.com

Live Tweet, Slides and Examples

• Twitter: @RuthlessHelp

• Slides:
http://www.slideshare.net/ruthlesshelp

• Code Samples:
http://github.com/ruthlesshelp

Stephen D. Ritchie 2

The Problem
1 Scott makes changes
2 Susan makes changes
3 You can’t build
Source
Code

1 3 2

Scott’s Susan’s
You
Computer Computer

Stephen D. Ritchie 3

What Went Wrong?

Conflicts
Missing Files
Breaking Changes
Stephen D. Ritchie 4

How do you
find
integration
issues?
Stephen D. Ritchie 5

Manual Integration

Build
Run Some Unit Tests
Perform Static Analysis
Clean + Rebuild All
Stephen D. Ritchie 6

Continuous Integration Blueprint

Stephen D. Ritchie 7

CI Server

Source CI
Code Server

Scott’s Susan’s
You
Computer Computer

Stephen D. Ritchie 8

CI Server

Triggered by SCM
and

Stephen D. Ritchie 9

CI – Per Commit Steps

1. Clean + Rebuild All
2. Run All Unit Tests
3. Analysis
Static Code Analysis
Coding Standards
Stephen D. Ritchie 10

Continuous Integration Toolbox

Stephen D. Ritchie 11

CI Server – Jenkins

http://jenkins-ci.org/

Free
Open Source
Stephen D. Ritchie 12

CI Server – Cruise Control

http://cruisecontrol.sourceforge.net/

http://www.cruisecontrolnet.org/

Free
Open Source
Stephen D. Ritchie 13

CI Server – TeamCity

http://www.jetbrains.com/teamcity/

Commercial
Easy to Use
Stephen D. Ritchie 14

Perhaps an
example would
be helpful
Stephen D. Ritchie 15

Continuous Integration Master Craft

Stephen D. Ritchie 16

The Master Craft

Unit Testing
Plus

Code Coverage

Stephen D. Ritchie 17

The Master Craft

System Testing
Integration Testing
Acceptance Testing
Stephen D. Ritchie 18

The Master Craft

Code Quality
Visualizations Analysis
Checks
Metrics
Detections
Stephen D. Ritchie 19

The Master Craft

Reporting
And

Visibility

Stephen D. Ritchie 20

The Master Craft

Packaging
And

Deployment

Stephen D. Ritchie 21

Stephen’s Contact Info

• Email: stephen.ritchie@excella.com

• LinkedIn:
http://www.linkedin.com/in/sritchie

Stephen D. Ritchie 22

What's hot

As developers we write code everyday, only to frown at it a week after that. Why do we have such a hard time with code written by others and ourselves, this raging desire to rewrite everything we see? Writing code that survives the test of time and self judgment is a matter of clarity and simplicity. Let's talk about growing, learning and improving our code with calisthenics, readability and good design.

“Writing code that lasts” … or writing code you won’t hate tomorrow.

Rafael Dohms

“Writing code that lasts” … or writing code you won’t hate tomorrow.

Rafael Dohms

Writing code that lasts - JAB14

Rafael Dohms

The world runs on legacy code. For every greenfield progressive web app with 100% test coverage, there are literally hundreds of archaic line-of-business applications running in production - systems with no tests, no documentation, built using out-of-date tools, languages and platforms. It’s the code developers love to hate: it’s not exciting, it’s not shiny, and it won’t look good on your CV - but the world runs on legacy code, and, as developers, if we’re going to work on anything that actually matters, we’re going to end up dealing with legacy. To work effectively with this kind of system, we need to answer some fundamental questions: why was it built this way in the first place? What's happened over the years it's been running in production? And, most importantly, how can we develop our understanding of legacy codebases to the point where we're confident that we can add features, fix bugs and improve performance without making things worse?

.NET Fest 2018. Dylan Beattie. Ctrl-Alt-Del: Learning to Love Legacy Code

NETFest

NCompass Live - April 22, 2015 http://nlc.nebraska.gov/ncompasslive/ In 2015 the hottest accessory for young and old is wearable technology and e-textiles. Wearable technology refers to devices that can be worn by users, taking the form of an accessory such as jewelry, sunglasses, a backpack, or even actual items of clothing like shoes or a jacket. A benefit of wearable technology is that it can conveniently integrate tools, devices, power needs, and connectivity within a user’s everyday life and movements. This NCompass Live focuses on "wearable tech" projects and e-textile projects for youth in your library. Dagen Valentine, Graduate Assistant from Nebraska 4-H will be presenting wearable/e-textiles tech youth project ideas for libraries. He's selected a fiction and a non-fiction book for each of these age-groups, grades K-5, middle school and high school. He'll suggest wearable tech projects that can be done with each book. Dagen will share information on where to purchase the hardware for the wearable tech projects he highlights in today’s webinar.

NCompass Live: Explore Wearable Technologies and Book Connections for Youth

Nebraska Library Commission

Adding features to a programming language is a difficult prospect. Politics, committees, compatibility, and egos don’t make it any easier. And once a feature has finally made it and shipped, there is a whole other question of how does it plays out? Did designers get it right, does adoption occur? Does the promises of the new feature actually solve the software developer’s pain? How do developers decide to use a new feature, do they plan to migrate old code, coordinate coding standards?

Java Generics Adoption: How New Features are Introduced Championed or Ignored

Chris Parnin

DevTechDocsOps

VMware Tanzu

What's hot (7)

“Writing code that lasts” … or writing code you won’t hate tomorrow.

Writing code that lasts - JAB14

.NET Fest 2018. Dylan Beattie. Ctrl-Alt-Del: Learning to Love Legacy Code

NCompass Live: Explore Wearable Technologies and Book Connections for Youth

Java Generics Adoption: How New Features are Introduced Championed or Ignored

DevTechDocsOps

Similar to Continuous Integration: Blueprint, Toolbox, Master Craft

Continuous Integration: Blueprint, Toolbox, Master Craft

Excella

Continuous Integration: Toolbox, Blueprint, Master Craft

DC Agile Engineering Conference

Continuous Integration: Blueprint, Toolbox, Master Craft

Stephen Ritchie

DevOps emphasizes communication, collaboration and integration between the developers and the operations folks. Some teams figure out DevOps on their own, but most struggle in their effort to implement DevOps practices, such as, automated builds, automated tests, automated deployments, continuous integration, and continuous delivery. Many consider these practices essential for the success of any software development project, but they require a new way of thinking. In other words: DevOps requires agility.

DevOps Requires Agility

Stephen Ritchie

Clean Software Design: The Practices to Make The Design Simple

Lemi Orhan Ergin

IATI implementation at DFID

johnthegeo

IP Reuse Impact on Design Verification Management Across the Enterprise

DVClub

Apache Druid Vision and Roadmap

Imply

A Business Case for Git - Tim Pettersen

Atlassian

Stki summit2012infra v7 - major trends - paradign shifts

Pini Cohen

A Gentle Introduction to Tidy Statistics in R.pdf

VickyAlers

Spotify had one of its most disruptive outages in recent history in the evening of 8.3.2022 CET, which resulted in over an hour of downtime and users getting logged out. As luck would have it, I was on-call for the very first time for the User platform tribe. I helped where I could, but mostly watched in awe as a flurry of teams came online after-hours to work together to debug and mitigate the issue. Here, I walk you through the storm of incident-20220308, including symptoms, root causes, aftereffects, and takeaways.

stackconf 2022: Spotify’s outage of 8.3.2022, explained

NETWAYS

stackconf 2022 | Spotify’s outage of 8.3.2022, explained

NETWAYS

Crypto Dev Report · 2022

Maria Xinhe Shen

Open Source Summit - AI4CI.pdf

AakankshaDuggal2

Continuous Delivery and Automated Operations on k8s with keptn

Andreas Grabner

Cytoscape CI Chapter 2

bdemchak

ContinuousDelivery-101

Kishore Bhatia

The Four Keys - Measuring DevOps Success

Dina Graves Portman

SDCSB Advanced Tutorial: Reproducible Data Visualization Workflow with Cytosc...

Keiichiro Ono

Similar to Continuous Integration: Blueprint, Toolbox, Master Craft (20)

Continuous Integration: Blueprint, Toolbox, Master Craft

Continuous Integration: Toolbox, Blueprint, Master Craft

Continuous Integration: Blueprint, Toolbox, Master Craft

DevOps Requires Agility

Clean Software Design: The Practices to Make The Design Simple

IATI implementation at DFID

IP Reuse Impact on Design Verification Management Across the Enterprise

Apache Druid Vision and Roadmap

A Business Case for Git - Tim Pettersen

Stki summit2012infra v7 - major trends - paradign shifts

A Gentle Introduction to Tidy Statistics in R.pdf

stackconf 2022: Spotify’s outage of 8.3.2022, explained

stackconf 2022 | Spotify’s outage of 8.3.2022, explained

Crypto Dev Report · 2022

Open Source Summit - AI4CI.pdf

Continuous Delivery and Automated Operations on k8s with keptn

Cytoscape CI Chapter 2

ContinuousDelivery-101

The Four Keys - Measuring DevOps Success

SDCSB Advanced Tutorial: Reproducible Data Visualization Workflow with Cytosc...

More from Stephen Ritchie

Overview of .NET Best Practices

Stephen Ritchie

Lightweight Documentation

Stephen Ritchie

Agile Engineering Sparker GLASScon 2015

Stephen Ritchie

One of the values of the Agile manifesto is working software over comprehensive documentation. However many agile teams think that now we are Agile we don’t need to document. Come to this session to learn about lightweight documentation and how to strike a sensible balance between working software and documentation. Learn which documents are necessary and which documents you can do without as well. Learn about JIT lightweight alternatives to our tradition documentation set. Leave with specific techniques to evaluate the value of each document along with recommended alternatives.

Lightweight Documentation: An Agile Approach

Stephen Ritchie

Scrum and Agile Engineering Practices - What every ScrumMaster needs to know Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We'll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We'll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team's software development process.

Dc scrum agile_eng_20130923

Stephen Ritchie

Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses the current date and time? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away Agile testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.

Agile Testing Best Practices

Stephen Ritchie

This presentation is a practical overview of many of the best practices that you can apply to your .NET projects today. We will cover a broad range of practices and principles with an emphasis on tools and technologies in four key areas: build automation, continuous integration, automated testing, and code analysis. Since complex problems often require iterative solutions, this presentation looks at an iterative approach to adopting new and better practices. Through a stepwise process we’ll examine key areas to improve, how to get started and continue to grow implementation, and what might motivate folks to stick with .NET best practices.

An Overview of .NET Best Practices

Stephen Ritchie

Have you ever bumped into a wall with your automated tests? Many developers bump into various roadblocks and hurdles when writing test code. Are your test methods starting to fail because the code-under-test uses DateTime.Now? Are your automated integration tests failing because the database they integrate with keeps changing? Do you have an explosion of test methods, with the ratio of test code to code-under-test way too high? Is your effort to refactor and improve code overwhelmed by the time it takes to rewrite all those failing unit tests? This presentation is about clearing away automated testing obstacles, avoiding common pitfalls, and staying away from dangerous practices.

Overcoming the Obstacles, Pitfalls, and Dangers of Unit Testing

Stephen Ritchie

An Overview of .NET Best Practices

Stephen Ritchie

DCDNUG 10/16/2012 Automated testing obstacles pitfalls dangers

Stephen Ritchie

Automated Testing: Obstacles, Pitfalls, and Dangers

Stephen Ritchie

Automated Testing with Databases

Stephen Ritchie

More from Stephen Ritchie (12)

Overview of .NET Best Practices

Lightweight Documentation

Agile Engineering Sparker GLASScon 2015

Lightweight Documentation: An Agile Approach

Dc scrum agile_eng_20130923

Agile Testing Best Practices

An Overview of .NET Best Practices

Overcoming the Obstacles, Pitfalls, and Dangers of Unit Testing

An Overview of .NET Best Practices

DCDNUG 10/16/2012 Automated testing obstacles pitfalls dangers

Automated Testing: Obstacles, Pitfalls, and Dangers

Automated Testing with Databases

Recently uploaded

IESVE for Early Stage Design and Planning

IES VE

TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...

marcuskenyatta275

Linux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdf

FIDO Alliance

Where to Learn More About FDO _ Richard at FIDO Alliance.pdf

FIDO Alliance

Heather Hedden, Senior Consultant at Enterprise Knowledge, presented “Enterprise Knowledge Graphs: The Importance of Semantics” on May 9, 2024, at the annual Data Summit in Boston. In her presentation, Hedden describes the components of an enterprise knowledge graph and provides further insight into the semantic layer – or knowledge model – component, which includes an ontology and controlled vocabularies, such as taxonomies, for controlled metadata. While data experts tend to focus on the graph database components (RDF triple store or a label property graph), Hedden emphasizes they should not overlook the importance of the semantic layer.

Enterprise Knowledge Graphs - Data Summit 2024

Enterprise Knowledge

This presentation dives into the practical applications of machine learning within Google's operations, providing a comprehensive overview of how to leverage AI technologies to solve real-world business challenges. Key Points Covered: - Introduction to Machine Learning at Google: Discussion on the role of ML and its evolution in enhancing Google's operational efficiency. - Experience Sharing: Insights into the team's long-term engagement with machine learning projects and the impacts on Google’s operational strategies. - Practical Applications: Real-world examples of ML applications within Google’s daily operations, providing a blueprint to adapt similar strategies. - Challenges and Solutions: Discussion on the challenges faced during the implementation of ML projects and the strategic solutions employed to overcome them. - Future of ML at Google: Insights into future trends in machine learning at Google and how they plan to continue integrating AI into their ecosystem.

Strategic AI Integration in Engineering Teams

UXDXConf

Syngulon’s technology expands the capacity for selection of microorganisms. The ability to select individual microbes with a behavior of interest is essential, whether for simple cloning at the bench, or for industry-scale production. Synthetic biology uses the concept of “bioengineering” to improve or modify existing genetic systems to create microbes with desired behaviors, and Syngulon uses this approach to develop its selection technologies. This selection technology is based on bacteriocins, ribosomally-produced peptides naturally made by most bacteria to kill competitive microbial species. These bacteriocins can have a limited or wide target range against other microbial species. This technology offers advantageous over antibiotic selection for several reasons: it avoids the use of antibiotics in the first place, helping to reduce the spread of antibiotic resistant microbes. The technology also increases product yield; as bacteriocins are generally smaller peptides, they do not impose a heavy metabolic burden on the producing cell. They can have a wide target specificity, helping to avoid genetic drift. Finally, our system is 100% plasmid-based (e.g. without chromosomal mutations), making it applicable for use in any E. coli strains.

Syngulon - Selection technology May 2024.pdf

Syngulon

Measures in SQL (a talk at SF Distributed Systems meetup, 2024-05-22)

Julian Hyde

We're living the AI revolution and Salesforce is adapting and bring new value to their customers. Einstein products are evolving rapidly and navigating their limitations, language support, and use cases can be challenging. Let's make review of what Einstein product are available currently, what are the capabilities and what can be used for in CEE region and how Rossie.ai can help to learn Salesforce speak Czech. We will explore the Einstein roadmap and I will make a short live demo (based on your vote) of some Einstein feature.

AI revolution and Salesforce, Jiří Karpíšek

CzechDreamin

The presentation underscores the strategic advantage of treating design systems not just as technical assets but as vital business components that require thoughtful management, robust planning, and strategic alignment with organizational goals. Key Points Covered: - Understanding Design Systems as Business Entities: Conceptualizing design systems as internal business entities can streamline their integration and evolution within a company. - Adoption and Expansion: Elaborating on the importance of tactical adoption across organizational structures, enhancing product suites to cater to user needs and broadening scope to mobile and content authoring solutions. - Data-Driven Development: Utilizing data insights for component development ensures that resources are allocated to create valuable, widely used features. - Financial Modeling for Design Systems: Developing sustainable funding models is crucial for long-term support and success of design systems. - Promoting Internal Buy-In: Stressing on strategies for promoting design systems within the organization to increase engagement and investment from internal stakeholders.

A Business-Centric Approach to Design System Strategy

UXDXConf

Designing inclusive products is not only a social responsibility but also a business imperative. This talk delves into the journey of creating accessible hardware products that cater to diverse user needs. Key Topics Covered: 1. Introduction to Inclusive Design - Importance of accessibility in product design - Overview of Comcast's commitment to making products accessible to a wide audience 2. Case Study: Xfinity Large Button Voice Remote - Initial challenges and the evolution of the product - User research and feedback that shaped the design - Key features of the final product and their benefits 3. Designing for Diverse Needs - Understanding human-centered design and its historical context - The impact of designing for people with disabilities on overall product quality - Examples from other industries, such as architecture and industrial design 4. Integrating Accessibility from the Beginning - The cost and efficiency benefits of designing for accessibility from the start - The process of embedding accessibility as a core trait rather than an optional feature 5. Real-World Impact and Continuous Improvement - Insights from in-home studies with users having assistive needs - How continuous feedback and iterative design lead to better products - The role of inclusive research and development practices

Designing for Hardware Accessibility at Comcast

UXDXConf

ScyllaDB has the potential to deliver impressive performance and scalability. The better you understand how it works, the more you can squeeze out of it. But before you squeeze, make sure you know what to monitor! Watch our experienced Postgres developer work through monitoring and performance strategies that help him understand what mistakes he’s made moving to NoSQL. And learn with him as our database performance expert offers friendly guidance on how to use monitoring and performance tuning to get his sample Rust application on the right track. This webinar focuses on using monitoring and performance tuning to discover and correct mistakes that commonly occur when developers move from SQL to NoSQL. For example: - Common issues getting up and running with the monitoring stack - Using the CQL optimizations dashboard - Common issues causing high latency in a node - Common issues causing replica imbalance - What a healthy system looks like in terms of memory - Key metrics to keep an eye on This isn’t “Death-by-Powerpoint.” We’ll walk through problems encountered while migrating a real application from Postgres to ScyllaDB – and try to fix them live as well.

Optimizing NoSQL Performance Through Observability

ScyllaDB

Speed Wins: From Kafka to APIs in Minutes

confluent

Join me in this session where I'll share our journey of building a fully serverless application that flawlessly managed check-ins for an event with a staggering 80 thousand registrations. We'll dive into three key strategies that made this possible. Firstly, by harnessing DynamoDB global tables, we ensured global service availability and data replication across regions, boosting performance and disaster recovery. Next, we'll explore how we seamlessly integrated real-time updates into the app using Appsync subscriptions, making the experience dynamic and engaging for users. Finally, I'll discuss how provisioned concurrency not only improved performance but also kept costs in check, highlighting the cost-effectiveness of serverless architectures. Through these strategies and the inherent scalability of serverless technology, our application effortlessly handled massive user loads without manual intervention. This session is a real world example to the power and efficiency of modern cloud-based solutions in enabling seamless scalability and robust performance with Serverless

How we scaled to 80K users by doing nothing!.pdf

Srushith Repakula

Intrigued by why some of the world's largest companies (Netflix, Google, Cisco, Twitter, Uber etc) are using gRPC? In this demo based talk we delve into the world of gRPC in .Net, what it does and why we should use it. We compare the interface with both Rest and graphQL. We will show you how to implement grpc server-side in .net and in the web. Finally, I will show you how the tooling helps you deliver powerful interfaces and interact with them quickly and simply.

Demystifying gRPC in .Net by John Staveley

John Staveley

I'm excited to share my latest predictions on how AI, robotics, and other technological advancements will reshape industries in the coming years. The slides explore the exponential growth of computational power, the future of AI and robotics, and their profound impact on various sectors. Why this matters: The success of new products and investments hinges on precise timing and foresight into emerging categories. This deck equips founders, VCs, and industry leaders with insights to align future products with upcoming tech developments. These insights enhance the ability to forecast industry trends, improve market timing, and predict competitor actions. Highlights: ▪ Exponential Growth in Compute: How $1000 will soon buy the computational power of a human brain ▪ Scaling of AI Models: The journey towards beyond human-scale models and intelligent edge computing ▪ Transformative Technologies: From advanced robotics and brain interfaces to automated healthcare and beyond ▪ Future of Work: How automation will redefine jobs and economic structures by 2040 With so many predictions presented here, some will inevitably be wrong or mistimed, especially with potential external disruptions. For instance, a conflict in Taiwan could severely impact global semiconductor production, affecting compute costs and related advancements. Nonetheless, these slides are intended to guide intuition on future technological trends.

Future Visions: Predictions to Guide and Time Tech Innovation, Peter Udo Diehl

Peter Udo Diehl

When you think of a highly secure meeting environment, do you instantly think 'Microsoft Teams'!? Or do you think about some unknown application, troublesome UI and daunting login process...? If you think the latter - let's change that! In this session Femke will show you how using Teams Premium features can create secure, but also good looking meetings! PRETTY. Make sure your company's brand is represented before, during and after the meeting with Customization policies in place. SECURE. Lets utilize Meeting templates and Sensitivity Labels to protect your meeting and data to prevent sensitive information from being leaked. After this session, you will have a clear understanding of the capabilities of Teams Premium features and how to set up the perfect meeting that suits your organizational requirements!

ECS 2024 Teams Premium - Pretty Secure

Femke de Vroome

Explore the core of Salesforce success in 'Salesforce Adoption – Metrics, Methods, and Motivation.' We will discuss essential metrics, effective methods to drive adoption, and the driving force behind user engagement and explore strategies for onboarding, training, and continuous support that empower users to navigate the platform seamlessly. By leveraging these tools, you can effectively measure adoption against your company’s goals and create an environment where users not only adopt Salesforce but actively contribute to its ongoing success.

Salesforce Adoption – Metrics, Methods, and Motivation, Antone Kom

CzechDreamin

Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf

FIDO Alliance

New customer? New industry? New cloud? New team? A lot to handle! How to ensure the success of the project? Start it well! I've created the 3 areas of focus at the beginning of the project that helped me in multiple roles (BA, PO, and Consultant). Learn from real-world experiences and discover how these insights can empower you to deliver unparalleled value to your customers right from the project's start.

Powerful Start- the Key to Project Success, Barbara Laskowska

CzechDreamin

Recently uploaded (20)

IESVE for Early Stage Design and Planning

TEST BANK For, Information Technology Project Management 9th Edition Kathy Sc...

Linux Foundation Edge _ Overview of FDO Software Components _ Randy at Intel.pdf

Where to Learn More About FDO _ Richard at FIDO Alliance.pdf

Enterprise Knowledge Graphs - Data Summit 2024

Strategic AI Integration in Engineering Teams

Syngulon - Selection technology May 2024.pdf

Measures in SQL (a talk at SF Distributed Systems meetup, 2024-05-22)

AI revolution and Salesforce, Jiří Karpíšek

A Business-Centric Approach to Design System Strategy

Designing for Hardware Accessibility at Comcast

Optimizing NoSQL Performance Through Observability

Speed Wins: From Kafka to APIs in Minutes

How we scaled to 80K users by doing nothing!.pdf

Demystifying gRPC in .Net by John Staveley

Future Visions: Predictions to Guide and Time Tech Innovation, Peter Udo Diehl

ECS 2024 Teams Premium - Pretty Secure

Salesforce Adoption – Metrics, Methods, and Motivation, Antone Kom

Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf

Powerful Start- the Key to Project Success, Barbara Laskowska

Continuous Integration: Blueprint, Toolbox, Master Craft

1. Continuous Integration: Blueprint, Toolbox, Master Craft DC .NET Users Group (@DCDNUG) Stephen D. Ritchie February 2013 Meeting @RuthlessHelp Feb 19, 2013 Stephen D. Ritchie – Managing Consultant – Excella Consulting, Inc., 2300 Wilson Blvd, Suite 630, Arlington, VA 22201 – 703.840.8600 – http://excella.com

2. Live Tweet, Slides and Examples • Twitter: @RuthlessHelp • Slides: http://www.slideshare.net/ruthlesshelp • Code Samples: http://github.com/ruthlesshelp Stephen D. Ritchie 2

3. The Problem 1 Scott makes changes 2 Susan makes changes 3 You can’t build Source Code 1 3 2 Scott’s Susan’s You Computer Computer Stephen D. Ritchie 3

4. What Went Wrong? Conflicts Missing Files Breaking Changes Stephen D. Ritchie 4

5. How do you find integration issues? Stephen D. Ritchie 5

6. Manual Integration Build Run Some Unit Tests Perform Static Analysis Clean + Rebuild All Stephen D. Ritchie 6

7. Continuous Integration Blueprint Stephen D. Ritchie 7

8. CI Server Source CI Code Server Scott’s Susan’s You Computer Computer Stephen D. Ritchie 8

9. CI Server Triggered by SCM and Stephen D. Ritchie 9

10. CI – Per Commit Steps 1. Clean + Rebuild All 2. Run All Unit Tests 3. Analysis Static Code Analysis Coding Standards Stephen D. Ritchie 10

11. Continuous Integration Toolbox Stephen D. Ritchie 11

12. CI Server – Jenkins http://jenkins-ci.org/ Free Open Source Stephen D. Ritchie 12

13. CI Server – Cruise Control http://cruisecontrol.sourceforge.net/ http://www.cruisecontrolnet.org/ Free Open Source Stephen D. Ritchie 13

14. CI Server – TeamCity http://www.jetbrains.com/teamcity/ Commercial Easy to Use Stephen D. Ritchie 14

15. Perhaps an example would be helpful Stephen D. Ritchie 15

16. Continuous Integration Master Craft Stephen D. Ritchie 16

17. The Master Craft Unit Testing Plus Code Coverage Stephen D. Ritchie 17

18. The Master Craft System Testing Integration Testing Acceptance Testing Stephen D. Ritchie 18

19. The Master Craft Code Quality Visualizations Analysis Checks Metrics Detections Stephen D. Ritchie 19

20. The Master Craft Reporting And Visibility Stephen D. Ritchie 20

21. The Master Craft Packaging And Deployment Stephen D. Ritchie 21

22. Stephen’s Contact Info • Email: stephen.ritchie@excella.com • LinkedIn: http://www.linkedin.com/in/sritchie Stephen D. Ritchie 22

Continuous Integration: Blueprint, Toolbox, Master Craft

Recommended

Recommended

More Related Content

What's hot

What's hot (7)

Similar to Continuous Integration: Blueprint, Toolbox, Master Craft

Similar to Continuous Integration: Blueprint, Toolbox, Master Craft (20)

More from Stephen Ritchie

More from Stephen Ritchie (12)

Recently uploaded

Recently uploaded (20)

Continuous Integration: Blueprint, Toolbox, Master Craft