Hudson build editor, history and server auto detection
, February 16th, 2011Disclaimer: This post is a shameless plug to lure you into voting for Mylyn Builds which is the awesome project that hosts the Mylyn Hudson Connector and was nominated for the Most Innovative New Feature or Project at the Eclipse Community Awards 2011.
Obviously, with EGit and other great Eclipse projects being nominated in the same category competition is tough. To help you decide please read on for an update on features that were added since my last post about the Mylyn Hudson Connector.
Builds now open in a a rich editor that provides a quick overview of tests results, artifacts and changes for a particular build. Double clicking on a change set opens the corresponding task based on the commit comment, clicking on a revision opens the file in the compare editor if it’s available in the local workspace and hosted in CVS.
This change set integration leverages APIs provided by the Mylyn Versions project and is a great example of the type of integration between Mylyn sub-projects that we are aiming for. We are planning to make this work for Git as well and work on an EGit connector has already been started (be on the look out for an upcoming post on the EGit Summit for more information).
Additionally, tasks can now be created from builds through the editor toolbar or context menu of the Builds view. The task description is pre-populated with relevant build details about changed files and failed tests so you can create Bugzilla bugs to track test failures with a few simple clicks.
When a plan is opened in the Builds view, the latest build of the corresponding Hudson job is shown by default. Older builds for a job are now accessible from the History view as well which can be opened through the context menu of the Builds view.
A neat feature that was contributed by Torkild Ulvøy Resheim, who is now a committer, is auto detection of Hudson servers. It builds on the ECF discovery API and listens to multicast DNS broadcasts. When a broadcast is received from a Hudson server that has not been configured, yet, a service message is displayed in the Builds view. Clicking the link opens a pre-populated Hudson server configuration dialog. Auto discovery is configurable in the preferences under General > Notifications.
You can find the latest build on the new Mylyn weekly update site at http://download.eclipse.org/mylyn/snapshots/weekly. The first 0.7 release which will be part of Mylyn 3.5 is planned for March.
February 16th, 2011 at 1:22 pm
I’m pressed Steffen, great work!
Will this work with Jenkins instances too?
February 16th, 2011 at 1:59 pm
Thanks Chris. The connector should work with Jenkins instances in the same way that it works with Hudson servers. The vast majority of the work on the connector occurred before the fork, and so support for Jenkins has not been tested and is not explicit in the UI. We are interested in expanding support for Jenkins and community contributions. Please feel encouraged to file bugs if you run into any problems or comment on bug 337373: https://bugs.eclipse.org/bugs/show_bug.cgi?id=337373 .
March 24th, 2011 at 7:45 pm
Thanks to *everyone* that contributed to this! I absolutely love the autodiscovery, the deep integration with all the right bits of Eclipse – great attention to the details. You guys just kick ass. No way around it – awesome. I’m also chuffed about renewed work on the redmine connector – can’t wait to show the pointy haired bosses how all this stuff integrates to create a great continuous integration story.
Now if tycho can just step up and replace all the B3, Buckminster, Athena, Ant goop….ahhh build nirvana