《Continuous Integration》读书笔记
Trigger a Build whenever a change occurs. it can help us reduce assumptions on a projecvt by rebuilding software whenever a change occurs in a version control system.
The value of CI:
- Reduce risks
- Defects are detected and fixed sooner
- Health of software is measurable
- Reduce assumptions
- Reduce repetitive manual processes
- CI can be run repeatly
- Generate deployable software at any time and at any place
- Enable better project visibility
- Effective decisions
- Noticing trends
- Establish greater confidence in the software product from the development team
Steps of implement CI
- Identify, find the processes that need to be automated
- Build, create some scripts to run the process
- Share, make everything managed by version control
- Continuous, let script run when a change occurs
Best Practices using CI
- Commit code frequently
- Make small changes
- Commit after each task
- At least once a day
- Do not commit broken code
- Do not commit code that does not compile with other code or fails a test
- Fix broken builds immediately
- make it as high priority
- Write automated developer tests
- Make sure tests will be run during build
- Run private builds
- This is to prevent integration failure
- Avoid getting broken code
Software Risks
- Lack of Deployable Software
- Little or no confidence in whether we could even build the software
- Lengthy integration phases before delivering the software internally or externally, during which time nothing else got done
- Inability to produce and reproduce testable builds
- Late Discovery of Defects
- Lack of Project Visibility
- Low-quality Software
Build Software at Every Change
- Perform build automatically
- Perfomr build through single command
- Separate build script from IDE
- Centralize Software Assets
- Create a Consistent Directory Structure
- Fail Builds Fast
- Build for Any Environment
- Use a Dedicated Integration Build Machine
- Use a CI Server
- Run Manual Integration Builds
- Run Fast Builds
- Stage Builds
Build Type
- Private Build
- Integration Build
- Release Build
Build Mechanisms
- On-demand
- Scheduled
- Poll for changes
- Event-driven
Responsibilities of CI Server
- Poll for changes in the version control repository on a specified time interval
- Perform certain actions on a scheduled basis, such as hourly or daily
- Identify a "quiet period" during which no integration builds are performed for the project
- Support for different build scripting tools including command-line tools such as Rake, make, Ant or NAnt
- Send e-mails to the concerned parties
- Display a history of previous builds
- Display a dashboard that is Web accessible so that everyone can review integration build information -Support multiple version control systems for your different projects
Continuous Database Integration
- Automate Database Integration
- Use a Local Database Sandbox
- Use a Version Control Repository to Share Database Assets
- DDL to drop and create tables and views, including constraints and triggers
- Stored procedures and functions
- Entity relationship diagrams
- Test data for differrent environments
- Specific database configurations
- Give Developers Capability to Modify the Database
- Make DBA Part of Development Team
Repeatable Database Integration Activities
- Drop database
- Create database
- Insert system data
- Insert test data
- Migrate database and data
- Set up database instances in multiple environments
- Modify column attributes and constraints
- Modify test data
- Modify stored procedures/functions/triggers
- Obtain access to different environments
- Back up/restore large data sets
The reliablity of a linear system is the product of the reliablity of each of the system's components, i.e. a system with three components, each component is 90% reliable, the the whold product is 73%(90%90%90%) reliable.
Unit tests verify the behavior of samll element in a software system, which are most often a single class.
Component or subsystem tests verify portions of a system and may require a fully installed system or some external dependencies, such as database, file system or network endpoint.
System tests exercise a complete software system and therefore require a fully installed system, such as a servlet container and associated databas.
Functional tests or acceptance tests are used to test the functionality of an application from the viewpoint of a client, which means the tests themselves mimic clients.
We need to categorize the tests during creating the test cases, as different kinds of tests need different duration to run.
Time requirement for test: Unit Test > Component Test > System Test
We should create test against defect. a test case can make sure: 1) you fix the defect; 2) prevent the defect from recurring.
Continuous Testing
- Automate Unit Tests
- Automate Component Tests
- Automate System Tests
- Automate Functional Tests
- Categorize Developer Tests
- Run Faster Tests First
- Write Tests for Defects
- Make Component Tests Repeatable
- Limit Test Cases to One Asset
Pair programming is treated as best practice of Agile. but many companies can not afford it.
Peer-based code reviews are generally considered benegicial to the overall quality of a code base because they present opportunities for an objective analysis by a second pair of eyes.
There are many tools can help do this, like Java's PMD and .NET's FxCop.
We prefer to use tools to run inspection automatically, Once you run a automatic build, you should run automatic inspection.
We can use NDepend or some similiar tols to check the dependencies of different classes. it will generate a human readable html report.
We need to consider how to add inspection to continous integration process, it will improve software quality.
A typical deployment includes:
- Label a repository's assets
- Produce a clean environment, free of assumptions
- Generate and label a build directly from the repository and install it on the target machine
- Successfully run tests at all levels in a clone of the production environment
- Create build feedback reports
- If necessary, you can roll back the release by using labels in your version control repository
When preparing a clean environment, it may include:
- Operating System
- Operating system configuration, i.e. network connectivity/firewall
- Server components for the software, i.e. database server/messaging server
- Server configuration
- Thrid-party tools, i.e. Web Frameworks
- Custom software
Feedback is a key output for a CI system, we should send the right information to the right people at the right time and in the right way.
Everyone needs to reveive some type of feedback on the project, but not necessarily every item every time. Sending feedback to all project members too often will ensure that everyone begins to ignore the messages. it is important that your team does not learn to ignore messages from CI build process.
The following people should receive feedback:
- Project Manager
- Architect/Technical Lead
- Developers
- Testers
At the heart of continous feedback is reducing the time between when a defect is introduces, discovered and fixed.
We can use the following ways to deliver feedback:
- SMS
- Ambient Orb and X10 Devices
- Windows Taskbar
- Sounds
- Wide-Screen Monitors
CI Tools
- Anthillpro
- Apache Continuum(Maven)
- Banboo
- BuildForge
- Continous Integration Server Matrix
- CruiseControl
- CruiseControl.NET
- Draco.NET
- Gauntlet(not found)
- LuntBuild
- ParaBuild
- PMEase QuickBuild
- Sin
Build Script Tools
- Ant
- Groovy
- Maven
- NAnt
- Rake
Version Control Tools
- ClearCase
- CVS
- MKS
- SubVersion
- SnapshotCM
- RTC
- GitHub
- Visual SourceSafe
DataBase Resources
- Hypersonic DB
- Mckoi
- MySQL
- Oracle
- PostgreSQL
Test Tools
- Agitator
- DbUnit
- Fit
- FitNesse
- Floyd(not found)
- HtmlUnit
- JUnit
- JWebUnit
- NDbUnit
- NUnit
- Selenium
- SQLUnit
- TestNG
- utPLSQL
- Watir
- xUnit Test Patterns
Inspection Tools
- Checkstyle
- Clover
- Cobertura
- EMMA
- FindBugs
- FxCop
- JavaNCSS
- JDepend
- NCover
- NDepend
- PMD
- Simian
- SourceMonitor
Deployment Resources
- Capistrano
Documentation Resources
- Doxygen
- JavaDoc
- NDoc
《Continuous Integration》读书笔记的更多相关文章
- csapp读书笔记-并发编程
这是基础,理解不能有偏差 如果线程/进程的逻辑控制流在时间上重叠,那么就是并发的.我们可以将并发看成是一种os内核用来运行多个应用程序的实例,但是并发不仅在内核,在应用程序中的角色也很重要. 在应用级 ...
- CSAPP 读书笔记 - 2.31练习题
根据等式(2-14) 假如w = 4 数值范围在-8 ~ 7之间 2^w = 16 x = 5, y = 4的情况下面 x + y = 9 >=2 ^(w-1) 属于第一种情况 sum = x ...
- CSAPP读书笔记--第八章 异常控制流
第八章 异常控制流 2017-11-14 概述 控制转移序列叫做控制流.目前为止,我们学过两种改变控制流的方式: 1)跳转和分支: 2)调用和返回. 但是上面的方法只能控制程序本身,发生以下系统状态的 ...
- CSAPP 并发编程读书笔记
CSAPP 并发编程笔记 并发和并行 并发:Concurrency,只要时间上重叠就算并发,可以是单处理器交替处理 并行:Parallel,属于并发的一种特殊情况(真子集),多核/多 CPU 同时处理 ...
- 读书笔记汇总 - SQL必知必会(第4版)
本系列记录并分享学习SQL的过程,主要内容为SQL的基础概念及练习过程. 书目信息 中文名:<SQL必知必会(第4版)> 英文名:<Sams Teach Yourself SQL i ...
- 读书笔记--SQL必知必会18--视图
读书笔记--SQL必知必会18--视图 18.1 视图 视图是虚拟的表,只包含使用时动态检索数据的查询. 也就是说作为视图,它不包含任何列和数据,包含的是一个查询. 18.1.1 为什么使用视图 重用 ...
- 《C#本质论》读书笔记(18)多线程处理
.NET Framework 4.0 看(本质论第3版) .NET Framework 4.5 看(本质论第4版) .NET 4.0为多线程引入了两组新API:TPL(Task Parallel Li ...
- C#温故知新:《C#图解教程》读书笔记系列
一.此书到底何方神圣? 本书是广受赞誉C#图解教程的最新版本.作者在本书中创造了一种全新的可视化叙述方式,以图文并茂的形式.朴实简洁的文字,并辅之以大量表格和代码示例,全面.直观地阐述了C#语言的各种 ...
- C#刨根究底:《你必须知道的.NET》读书笔记系列
一.此书到底何方神圣? <你必须知道的.NET>来自于微软MVP—王涛(网名:AnyTao,博客园大牛之一,其博客地址为:http://anytao.cnblogs.com/)的最新技术心 ...
- Web高级征程:《大型网站技术架构》读书笔记系列
一.此书到底何方神圣? <大型网站技术架构:核心原理与案例分析>通过梳理大型网站技术发展历程,剖析大型网站技术架构模式,深入讲述大型互联网架构设计的核心原理,并通过一组典型网站技术架构设计 ...
随机推荐
- python中常用的函数与库一
1, collections.deque 在python里如果我们用列表作为队列使用也是可以的,只是当从队尾删除或者增加元素的时候是很快的,但是从队首删除或者增加元素则要慢得多,这是因为在队首进行操作 ...
- OOM异常产生的原因和处理方法
一般而言,android中常见的原因主要有以下几个: 1.数据库的cursor没有关闭. 2.构造adapter没有使用缓存contentview. 3.调用registerReceiver()后未调 ...
- 快速入门系列--WCF--01基础概念
转眼微软的WCF已走过十个年头,它是微软通信框架的集大成者,将之前微软所有的通信框架进行了整合,提供了统一的应用方式.记得从自己最开始做MFC时,就使用过Named Pipe命名管道,之后做Winfo ...
- 小实例窥探dotnet垃圾回收
今天项目调试时发现VS中有下面这样的现象. 说明,file.ServerLocation是一个完整的物理路径.第三句代码是错误的,保留只是因为它使用了"s"字符串. 个人认为当 ...
- 面试准备 - C# 版本的树状数组
树状数组 计算 任意连续N个值的和的时间复杂度为Log(n) 修改也是Log(n) 而普通数组修改是O(1) 计算和是O(n) 具体定义可以看这里:http://zh.wikipedia.org/zh ...
- Cocos2d-x 3.2 学习笔记(五)Sprite Node
游戏中最重要的元素Sprite精灵,关于精灵的创建,精灵的控制等等. 涉及到的类Class: AnimationFrame 动画帧. Animation 动画对象:一个用来在精灵对象上表现动画的动画对 ...
- redis学习之二from github
大概敲了一遍基本命令,熟悉了redis的存储方式.现在开始进一步系统的学习.学习教程目前计划有三个,一个是github上的https://github.com/JasonLai256/the-litt ...
- 【读书笔记】--SQL基础概念复习
主键:每个表,只能有一个主键,主键不能为NULL,且必须是唯一的.主键最好是由单个列组成,但这不是必须的,主键也可以是由多个列组成,如果表的两个列组合在一起能唯一标识一个行,而单个列不能,则可以将这两 ...
- SQL---一次插入多条数据【使用Union】
--做测试的时候使用.--缺点:结果集的数量,类型都要一样.INSERT INTO Student ( StudentID, StudentName, StduentAge, StudentBirth ...
- 国产达梦数据库的结合Enterprise Library的应用开发
在上篇<基于Enterprise Library的Winform开发框架实现支持国产达梦数据库的扩展操作>介绍了如何在Enterprise Library的数据访问层上支持这种神秘的国产数 ...