Join Brian Fox for a 30 minute sneak preview of Insight for CI on Thursday, May 3 at 11AM EDT (GMT-0400). Brian will show you how Insight for CI will help you:
If you register, you’ll also receive access to the recording after the event. So if something comes up and you can’t make it, you won’t miss out.
Sonatype founder and CTO Jason van Zyl will be hosting a free webinar on the future of Hudson next week.
Hudson is a continuous integration (CI) server that helps you check-out source code, build and test your project, publish the results and communicate the results to team members. We’ve been working to make it easier to extend Hudson, to reduce the effort required to write a Hudson plugin, and to put in a new foundation for the next level of Hudson interoperability and performance. We’re excited about the work that has been done and the work yet to come. The benefits of these changes include better leveraging of industry standards, increased performance and stability, and tight integration with Maven 3 that provides greater visibility into running builds. Come to learn more about Hudson CI and future plans for the project.
Continuous Integration is a label for a set of tools and techniques that constantly build and report on the health of your applications, preventing developers from checking in broken code, and allowing your development teams to focus on continual improvement overall code quality. It lets you spot problems early in the development process, before testers or end users discover them and fixes become more costly.
Our Senior Systems Engineer, Blaine Mincey, will be presenting at Chariot Solutions Continuous Integration for the Enterprise in Philadelphia on December 1, 2010.
The presentation will focus on:
If you want to find out how the competition is moving ahead because they don’t have to keep looking behind, this seminar is for you.
Seats are filling up quickly, be sure to register today.
Now that we’ve covered the high points of our Hudson build farm setup here at Sonatype, I want to discuss some of the current issues we’re facing at the moment. It’s important to realize that providing high-quality continuous integration is a long, involved process…not a quick, one-off event. Sure, you can get Hudson up and running fairly rapidly in a non-distributed environment. However, the path to distributed, multi-OS builds that capture a full range of testing can be very, very complex. In the end, if you can get by simply compensating for the problems I talked about in this series of posts, then you’re probably pretty lucky. Here at Sonatype, we’re certainly very conscious of the fact that our continuous integration setup could run more perfectly, and we continue to chip away at the list of things we’d like Hudson to verify automatically on our behalf. So, in the interests of full disclosure, I’m including a short wish list of items we’re currently working on. Continue reading
Continuous Integration is a development best practice that you need to be using in your process; it is an essential part of an efficient Software Development Lifecycle (SLDC). If you aren’t using it already, then you should start, now. The main benefit of Continuous Integration is the ability to flag errors as they are introduced into a system instead of waiting multiple days for test failures and critical errors to be identified during the QA cycle. This post isn’t about the virtues of using CI, it’s about how to setup an optimal environment in a Maven shop. Here are seven tips for running Maven builds in a CI system such as Hudson. Continue reading
