InfoQ Homepage Automation Content on InfoQ
-
Automating (almost) Everything Using Git, Gerrit, Hudson and Mylyn
Ryan Slobojan discusses how to perform issue tracking, code review, commits and builds in an automated manner by integrating Git, Gerrit, Hudson and Mylyn.
/presentations/Automating-almost-Everything-Using-Git-Gerrit-Hudson-and-Mylyn/en/smallimage/Ryan.JPG)
-
Evolving Continuous Delivery
Chris Read describes a situation where they had to gradually reorganize a development process standardizing the build and deployment scripts, adding CI, automating everything, staging the binaries.
/presentations/Evolving-Continuous-Delivery/en/smallimage/Chris.JPG)
-
Test First Development v.Next with Pex and Moles
David Starr demoes Pex –a parameterized white box unit test tool- and Moles –an isolation framework-, two .NET tools useful for test-first development.
/presentations/Pex-and-Moles/en/smallimage/David.JPG)
-
Why Program by Hand in Five Days what You Can Spend Five Years of Your Life Automating?
Terence Parr discusses using automation tools including DSLs to automate the software creation process as much as possible in order to increase output, effectiveness, correctness and velocity.
/presentations/Automation-DSL/en/smallimage/Terence.JPG)
-
Testing for the Unexpected
Ulf Wiger discusses the importance of automated testing along with some lessons learned at Ericsson, including using randomized and extensive testing, aiming to achieve system robustness.
/presentations/Testing-for-the-Unexpected/en/smallimage/Ulf.JPG)
-
Remediation Patterns - How to Achieve Low Risk Releases
Jez Humble presents remediation patterns based on prevention, low risk release through automate provisioning and deployment plus dev/test/ops collaboration, and incremental delivery.
/presentations/Remediation-Patterns/en/smallimage/Jez.JPG)
-
Savara - Formally Verifying SOA Designs Against Requirements
Steve Ross-Talbot presents Savara, comprising a set of tools enabling enterprise architects to validate various artifacts against other artifacts based on the “Testable Architecture” methodology.
/presentations/Savara/en/smallimage/steve.JPG)
-
The Case for Evolvable Software
Stephanie Forrest believes in the possibility to create evolvable software through automated bug repair, optimizing or improving code and creating new combinations of existing functionality.
/presentations/The-Case-for-Evolvable-Software/en/smallimage/STEF.JPG)
-
Being Elastic - Evolving Programming for the Cloud
Randy Shoup discusses the cloud programming model, covering topics such as state/statelessness, distribution, workload partitioning, cost and resource metering, automation, and deployment strategies.
/presentations/Evolving-Programming-for-the-Cloud/en/smallimage/Randy.JPG)
-
Continuous Deployment to Production 50 Times a Day
Eishay Smith discusses the advantages of using continuous deployment (CD) at a rapid pace, dozens of times a day, the process and the tools needed to attain CD, and practices to ensure code quality.
/presentations/Continuous-Deployment-50-Times-a-Day/en/smallimage/EishaySmith.JPG)
-
Development at the Speed and Scale of Google
Ashish Kumar on how Google keeps the source code of over 2000 projects in a single code trunk containing 100s of M of code lines, with more than 5,000 developers accessing the same repository.
/presentations/Development-at-Google/en/smallimage/Kumar.JPG)
-
Availability, the Cloud and Everything
Joe Williams discusses how distributed systems, cloud computing and configuration management affect system’s availability. He exemplifies with a database service built on CouchDB, Erlang, Chef, EC2.
/presentations/Availability-Cloud-and-Everything/en/smallimage/Joe.JPG)