De Zero a Produção - João Jesus
-
Upload
comunidade-netponto -
Category
Technology
-
view
216 -
download
2
description
Transcript of De Zero a Produção - João Jesus
De Zero a Produção – Automação de processos de build e deployment
João Jesus
http://netponto.org36ª Reunião Presencial – Lisboa - 03/02/2013
João Jesus
Twitter: http://twitter.com/joaomajesusLinkedIn: http://pt.linkedin.com/in/joaomajesusFacebook: http://www.facebook.com/joaomajesusGeekList: http://geekli.st/joaomajesusGithub: https://github.com/joaomajesus
Agenda
• Continuous Integration• Continuous Delivery• Web Deploy• Web.Config Transformations• Web.Config Parametrizations• Jenkins
Continuous IntegrationContinuous integration (CI) is the practice, in software engineering, of merging all developer workspaces with a shared mainline several times a day. It was first named and proposed as part of extreme programming (XP). Its main aim is to prevent integration problems, referred to as "integration hell" in early descriptions of XP.
Continuous DeliveryContinuous delivery (CD) is a pattern language in growing use in software development to improve the process of software delivery. Techniques such as automated testing, continuous integration and continuous deployment allow software to be developed to a high standard and easily packaged and deployed to test environments, resulting in the ability to rapidly, reliably and repeatedly push out enhancements and bug fixes to customers at low risk and with minimal manual overhead.
Continuous Delivery
JenkinsJenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Jenkins focuses on the following two jobs:
• Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity.
• Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Jenkins keeps those outputs and makes it easy for you to notice when something is wrong.
Referências
Jenkins the Definite Guidehttp://www.wakaleo.com/books/jenkins-the-definitive-guide
Continuous Integration in .NET
Agile ALM
Inside the Microsoft Build Engine: Using MSBuild and Team Foundation Build
Referências Jenkins
http://jenkins-ci.org/
.NET Web Development and Tools Blog - Site Home - MSDN Blogshttp://blogs.msdn.com/b/webdev/
Vishal Joshi's Tangenthttp://vishaljoshi.blogspot.pt/
Microsoft Web Deployment Team Blog : The Official Microsoft IIS Sitehttp://blogs.iis.net/msdeploy/default.aspx
Publish : The Official Microsoft IIS Sitehttp://www.iis.net/learn/publish
Web Deployment Content Map for Visual Studio and ASP.NEThttp://msdn.microsoft.com/en-us/library/bb386521.aspx
Web Deployment Made Awesome: If You're Using XCopy, You're Doing It Wrong - Scott Hanselmanhttp://www.hanselman.com/blog/WebDeploymentMadeAwesomeIfYoureUsingXCopyYoureDoingItWrong.aspx
Sayed Ibrahim Hashimi - MSBuild, Web Deploy (MSDeploy), ASP.NEThttp://sedodream.com/
Patrocinador “GOLD”
Twitter: @PTMicrosoft http://www.microsoft.com/portugal
Patrocinadores “Silver”
Patrocinadores “Bronze”
Próximas reuniões presenciais
02/03/2013 – Fevereiro (Lisboa)09/03/2013 – Março (Porto)16/03/2013 – Março (Lisboa)20/04/2013 – Abril (Lisboa)
Reserva estes dias na agenda! :)