Perforce Software announced the availability of P4Mylyn, its new connector to the Mylyn task and ALM framework for Eclipse. P4Mylyn's task-focused interface filters a developer's view to include only those Perforce-managed assets, along with their dependencies, that are associated with a given change request. Distilling a developer's focus to only those resources relevant to a particular task lets them respond quickly to change in agile workflows.
P4Mylyn was developed in cooperation with Tasktop Technologies, creators of Eclipse Mylyn. The P4Mylyn extension is distributed via Mylyn's Connector Discovery mechanism, making it effortless to download and install the integration from within the Eclipse IDE and ensuring interoperability with a wide variety of Tasktop Certified open source and commercial ALM solutions.
"Our Mylyn Connector will help developers manage and focus on a set of tasks, as well as prioritise, schedule and share the context of a task with others," explained Kevin Sawicki, P4Mylyn creator and lead contributor to Mylyn's SCM subproject API. "Contributors can quickly understand which Perforce-managed assets are associated with the task and coordinate their work more effectively, regardless of the team's physical location or area of expertise."
The Perforce Mylyn Connector automatically tracks code changes on a per-task basis, making it easy to commit to Perforce only the relevant changes when working on multiple tasks. It automatically generates commit comments that link back to the relevant story, defect or issue, providing complete traceability from any line of code back to the relevant task associated with the change.
Specific benefits of the P4Mylyn connector include:
- Easy client integration and code-to-task traceability with other third party tools that have Mylyn connectors, such as Bugzilla, JIRA, Mingle, Rally, and VersionOne.
- Hyperlinks to tasks from any repository. This allows developers to easily switch back and forth between tasks, file revisions, source code comments, and submitted or shelved groups of changes. For example, P4Mylyn gives developers the ability to switch from the Perforce to Bugzilla or JIRA repositories.
- 'Jobs', Perforce's built-in defect tracking system, becomes a first-class Mylyn task. This gives developers complete visibility into the tasks their team members are working on as well as automatically linking their own pending work to the Perforce job being fixed.
- Graphical differencing tools display only those changes specific to the associated change request.