Atlassian Bamboo and Crucible connectors for Eclipse Mylyn released
, March 23rd, 2009Last fall Atlassian and Tasktop joined forces in order to provide users of Atlassian’s very popular developer tools with first-rate Eclipse and Mylyn integration. That effort reached its first public milestone today, with Atlassian’s beta release of the Crucible and Bamboo connectors for code review and continuous integration.
Our relationship with Atlassian started a couple of years ago with a tremendous amount of Mylyn community demand for a JIRA connector. Atlassian’s developer tool suite has grown considerably since that time. Confluence has become a popular wiki, and last week’s Mylyn 3.1-based release of the JIRA connector now supports Confluence markup for editing issues inside Eclipse. Crucible is a newer tool that has made it possible to work with code reviews as easily as it is to work with tasks and issues. With today’s release, all of Crucible’s facilities are hooked seamlessly into the Eclipse IDE. Reviews can be managed in Mylyn’s Task List and scheduled with a click.
Commenting on reviews is as easy as commenting on issues, and can be done right from the Java editor. Changes under review can be inspected in a diff view. And as expected from a Mylyn integration, the task-focused interface works for reviews, meaning that you only see the code relevant to the review in the Package Explorer and Java editor. We’ve been using this for all of our code reviews at Tasktop and as expected, the integration between Crucible’s collaborative facilities and Eclipse’s code navigation is a killer feature that we’re very happy to get into the hands of Mylyn and Tasktop users. It’s great to see this new application of the task-focused interface action, two new Tasktop Certified connectors, and the Mylyn API changes that Crucible and Bamboo are pushing will open up doors for other interesting tools.
The Bamboo integration speaks for itself. Setting up a Bamboo server is as easy as connecting Mylyn to JIRA, at which point builds can be managed within the IDE, and Mylyn’s desktop notifications make you aware of build status changes. My favorite feature is the ability to populate Eclipse’s JUnit view with failed tests in order to rerun them. You can then right-click a test to create a JIRA issue from the failure and have that instantly show up in your Task List, all in just a few clicks.
For those at EclipseCon, check out the tools in action at tonight’s BOF and the other Mylyn sessions. For more information check out the Atlassian blog post, New & Noteworthy and for those of you already using Crucible and Bamboo, enjoy!
March 23rd, 2009 at 12:00 pm
[...] Tasktop Blog » Blog Archive » Atlassian Bamboo and Crucible connectors for Eclipse Mylyn… [...]
March 24th, 2009 at 5:12 pm
For anyone using the beta or wanting to contribute ideas to the Eclipse Connector project, please submit your issues or suggestions in our public JIRA instance.
Thanks,
Ken
March 25th, 2009 at 1:49 am
Hi Mik,
This is exciting news.
You’ve mentioned “Mylyn API changes that Crucible and Bamboo are pushing”. Have these changes landed into the Mylyn repository? Also, is there any timeline for getting them released?
Thanks,
Robert
March 25th, 2009 at 8:21 am
Regarding the API improvements, a couple of highlights are tre changes for task repositories and task editors.
We already had calendar repositories (e.g., Outlook, Google Calendar) in Tasktop, but did not incorporate these into Mylyn’s Task Repositories view and API because one new kind of repository was not enough to justify broadening the API. With the new Atlassian tools, we now have Bamboo and Crucible repositories, which had a very large amount of overlap with Task Repositories like JIRA. So for last week’s Mylyn 3.1 release we ensured that the API could support these other kinds of repositories. For an example see the screenshot on the New & Noteworthy. For the Galileo-based Mylyn 3.2 we are thinking of changing the name of the Task Repositories view to “Team Repositories”, and categorizing it by repository kind, e.g., Tasks, Email, Calendars, Build Systems, Code Review.
The other interesting part is the overlap between the code review editor and the task editor. For the beta we managed to get some reuse and a consistent look, but we could not quite fit it into the task editor framework. I’m hoping that for Mylyn 3.2 we’ll be able make the task editor more flexible in order to better support new kinds of task editors of this sort. It’s the same story with Tasktop’s task editor for email threads. It’s still overriding a lot of behavior from the task editor instead of inheriting it, and we hope to improve on that for the next release.
March 25th, 2009 at 3:07 pm
When doing API changes for other kinds of repositories, please note that the current operation set is not fully orthogonal for CRUD, as we noticed with the Industrial SQL connector. Deleting a task is now only possible in the local repository. Maybe isLocal() should be replaced by a more finely grained set of capabilities defined in the extension point, also allowing delet tas on the server, as well as delete comment and delete attachment.
File a bug?