This page tracks the status of the [http://code.google.com/soc/ GSOC] project "Hudson integration for Mylyn".<br />

+

Student: Markus Knittig<br />

+

Mentor: Steffen Pingel

−

This page contains the project proposal created by [[mailto:harshana05@gmail.com Harshana Martin]] for the idea of "Hudson Integration for Mylyn" from the [[http://wiki.eclipse.org/Google_Summer_of_Code_2010_Ideas GSoc 2010 idea list]]. I am extreamly happy to have comments from the viewers.

+

== About ==

−

== Summery ==

+

The goal of this projects is to integrate Hudson with Mylyn. It will be part of Mylyn/Build after the [http://eclipse.org/project-slides/mylyn-restructuring-review.html restructuring of Mylyn]. It should provided the following features:

−

+

* Monitoring build statuses in Eclipse

−

Eclipse Mylyn is the task and application lifecycle management (ALM) framework for Eclipse. under this Mylyn project there are several sub projects as Tasks, Context, SCM, Build, Docs and etc. The project idea "Hudson integration for Mylyn" is aiming at implementing a client application which implements Hudson's remote APIs and OSLC-Automation RESTful service APIs for interoperability among different vendors and platforms and implementing the basic UI layer for Eclipse that displays build status, console output and test results for builds.

+

* Viewing build details in Eclipse

+

* Running a build from within Eclipse

+

* Viewing test results in Eclipse

+

* Viewing a build log in Eclipse

+

* Adding a task from a failed build in Eclipse

== Details ==

== Details ==

−

Eclipse Mylyn is the task and application lifecycle management (ALM) framework for Eclipse. under this Mylyn project there are several sub projects as Tasks, Context, SCM, Build, Docs and etc. Integration with the Hudson continuous build server is categorized under the Build sub project since this provides a reference implementation to the Build server integration which follows the set of Open standard APIs called OSLC-Automation. So this implementation will follow the Open standard APIs for build automation which is known as OSLC-Automation. These set of standard APIs provides interoperability among different software/hardware vendors as well as different software/hardware platforms. So any set of software and hardware will be able to communicate with another different set of software and hardware which follows the same APIs. This provides the information exchange less painful and less overhead.

+

=== Package structure ===

−

When we consider the build automation Hudson CI server is one of the widely used servers. It provides users to build system automatically without human intervention upon set of triggers such as SCM commits, time based triggers such as nightly builds. But the problem is currently there is no UI in the Eclipse IDE which provides access to the Hudson server. So the users who are using Hudson server can write code in Eclipse and then commit it to their respective SCM system from Eclipse IDE using CVS, Subversion, Egit and other SCM integrations.But then to check whether code compiles well, he/she has to switch to a web browser to check the hudson server status. So if we can provide the Hudson integration, then users can write code, commit code and test and validate code from the Eclipse IDE without switching to any other view. So this will decrease the context switching among tasks of humans and it will increase the productivity of developers.

+

The project namespace will be ''org.eclipse.mylyn.hudson''.

+

The namespace for common build infrastructure will be ''org.eclipse.mylyn.builds''.

−

Implementation work of this project can be divided to 2 different sections.