Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 357020

Summary: add Mylyn Hudson/Jenkins connector to Java package
Product: [Technology] EPP Reporter: Steffen Pingel <steffen.pingel>
Component: java-packageAssignee: Steffen Pingel <steffen.pingel>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: mik.kersten, mknauer, steffen.pingel
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
patch none

Description Steffen Pingel CLA 2011-09-07 18:43:26 EDT
I would like to add the Mylyn Builds Hudson/Jenkins connector to the Java package for the Juno release: http://www.eclipse.org/mylyn/new/#hudson.
Comment 1 Steffen Pingel CLA 2011-09-08 02:59:41 EDT
* What is the impact on the download size of the Java package if the new component is included?

~1 MB

* Does the new component depend on components (e.g. PDE) that are not already part of the Java package?

The Hudson/Jenkins connector pull in other parts of Mylyn such as the builds and versions framework features that it is built on.

* Does the new component or any of its dependencies have incubation status?

Yes, the Hudson connector and some of its Mylyn dependencies are still in Incubation but we expect all relevant projects to graduate for Juno.

* Does the new component require additional components that would not be shipped as part of the Java package (e.g. an external runtime)?

No, but it's most useful if a Hudson or Jenkins server is available.

* Does the new component log any output to the console?

No.

* Does the new component contribute a startup extension?

Yes, the builds framework contributes a startup extensions to update the icon of the builds view to reflect the status of monitored build plans. If build jobs are selected the startup extension will also cause initialization of the Hudson server auto discovery. 

* Does the new component contribute any (modal) dialogs that are visible on startup?

No.

* What is the runtime impact if the new component is not used?

The startup activation will run briefly but it won't cause further initialization if no jobs are monitored.

* Which UI contributions if any does the new component add to the Java perspective?

None.
Comment 2 Steffen Pingel CLA 2011-09-08 03:08:36 EDT
Created attachment 202965 [details]
patch
Comment 3 Steffen Pingel CLA 2011-09-12 09:13:26 EDT
I have committed the patch.