Why is it that every web build system needs you to adapt to its way of working? Why do you have to write manifest files, put files into a specific directory structure and do a lot of manual work to have an optimized production build of your web site. If your browser can see the unoptimized assets in your web page, why shouldn’t your build system be able to as well? Read more
Specially for large enterprise builds, the build performance is critical. Yet the build must be reliable and should be intuitive to use. Gradle offers plenty of features to support this: Gradle keeps a history of past build executions, provides ready to use and performant tools for change detection. You will learn about the unique Gradle incremental compile with a state-of-the-art dependency analysis. We will show Gradle’s multi-threaded test execution and the advantages of a fully customizable fork frequency. You will also learn about Gradle’s smart skipping and the many ways how you can control the execution of a multi-project build and optimize it for certain use cases. All this is provided out-of-the-box for standard Java project’s. Yet Gradle provides all this not via a rigid framework but by a rich domain model. That way all those features a part of an extremely customizable, true build language.
Build scripts are an essential art in any software project. And yet they are so often fragile, brittle and unportable things, hard to understand and harder to maintain. In this talk, we cover what constitutes a good build script, and look at a few of the essential rules in writing one. John Smart looks at general techniques that are applicable to any build scripting technology, as well as some technology-specific tips for Ant and Maven.
Steve Andrews discusses Microsoft’s Application Lifecycle Management (ALM) which delivers source control, work item tracking, Team Foundation Build, a team project portal Web site, reporting, and project management capabilities.
Sam Newman discusses how to improve the process going from software development to production, covering the following steps: building, configuration, automated testing, deploying, monitoring, logging and disasters. He offers practical advice on how to avoid transforming the development, QA and Operations into silos by using build pipelines providing continuous builds and deployment.
This screencast demonstrates how to use Rake to build .NET solution, run unit tests and build documentation. Rake with Ruby is a perfect combination which will eliminate Nant and MSBuild hell.
In this screencast Mohammad Azam introduces Rake. Rake is a build framework for Ruby language but it can also be used to build, compile .NET applications.keep looking »