Continuous integration 101
Download as PPTX, PDF0 likes1,678 views
The document provides an overview of continuous integration (CI) as a software development practice that enhances code integration and error detection through automated builds. It discusses the benefits, such as immediate feedback and reduced risks, as well as barriers to implementation. Additionally, it introduces tools like TeamCity and Psake to facilitate CI processes in software development.
![Another Definition…
“CI is the embodiment of tactics that gives us,
as software developers, the ability to make
changes in our code, knowing that if
we break software, we’ll receive
immediate feedback… [It is] the
centrepiece of software development, as it
ensures the health of software through
running a build with every change.”
Reference
“Continuous Integration” – Paul Duval, Addison-Wesley, 2007](https://image.slidesharecdn.com/continuousintegration101-131202154042-phpapp02/85/Continuous-integration-101-7-320.jpg)
Continuous integration 101
- 1. Continuous Integration 101 Gary Ewan Park gep13@gep13.co.uk Twitter: @gep13 Blog: http://www.gep13.co.uk/blog
- 2. Agenda • • • • What is Continuous Integration? What are the barriers to entry? So why would we want to use this? What is TeamCity? • How do I get started with TeamCity? • What is psake? • How do I get started with TeamCity and psake?
- 4. Who here currently uses Continuous Integration?
- 6. A Definition… “Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily – leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.” Reference http://www.martinfowler.com/articles/continuousIntegration.html
- 7. Another Definition… “CI is the embodiment of tactics that gives us, as software developers, the ability to make changes in our code, knowing that if we break software, we’ll receive immediate feedback… [It is] the centrepiece of software development, as it ensures the health of software through running a build with every change.” Reference “Continuous Integration” – Paul Duval, Addison-Wesley, 2007
- 8. What does all that mean? http://en.wikipedia.org/wiki/Continuous_integration
- 9. What are the barriers to entry?
- 10. Typical reasons to not implement Continuous Integration • • • • • It means increased maintenance This is too much change too fast It means additional hardware and software costs Developers should compiling and testing The project is too far along to add it
- 11. So, why would we want to use this?
- 12. So why would I want to implement Continuous Integration? • Immediate feedback when there is a problem • Reduced Risks • Increased project visibility i.e. problems, roadblocks, current status, etc • It is the first building block towards Deployable software (Continuous Delivery and Continuous Deployment)
- 13. What is TeamCity? Note: I am not an affiliate of JetBrains, I just really like their products. My views are my own.
- 14. A Definition… “TeamCity is a closed source, Javabased build management and Continuous Integration server from JetBrains” Reference http://en.wikipedia.org/wiki/TeamCity http://www.jetbrains.com/teamcity/
- 15. Notable Features • You can perform gated commits to your source control system • Allows running multiple builds and tests under different environments simultaneously • Integrated code coverage, inspections, and duplicates search • Integration with IDEs • It’s FREE! (Up to a point, at which point there is commercial license)
- 16. How do I get started with TeamCity?
- 18. Demo 1 Adding Continuous Integration to an ASP.NET MVC Project
- 19. What is psake?
- 20. A Definition… “psake is a domain-specific language and build automation tool written in Powershell to create builds using a dependency pattern similar to Rake or MSBuild” Reference http://en.wikipedia.org/wiki/Psake https://github.com/psake/psake
- 22. How do I get started with TeamCity and psake?
- 24. Demo 2 Adding Continuous Integration to an ASP.NET MVC Project using psake
- 25. “Continuous Integration: Improving Software Quality and Reducing Risk” - Martin Fowler Signature Books Paul M. Duvall http://gep13.me/cibook1
- 26. “Continuous Integration in .Net” - Manning Marcin Kawalerowicz and Craig Berntson http://gep13.me/cibook2
- 27. Questions? Feel free to email me any additional questions at gep13@gep13.co.uk