Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [hudson-dev] Eclipse Hudson 3.0.0 Milestone M0 is available for download

On 1/18/12 12:51 PM, Henrik Lynggaard Hansen wrote:

New questions...  I have found the first plugin which fails
- Where to report bugs on 3.0, bugzilla or jira ?

All core related issues need to be filed in the bugzilla. non bundled Plugins maintained outside of Eclipse in the JIRA. Unfortunately the JIRA is down, we are finding it difficult to revive because of inaccessible credentials to the hypervisor which manages the VMs where it is hosted. We are working on it.

The good news is the wiki, JIRA and the hudson-ci website are moving to new machines in a week or so, which will have proper IT support.

- How to handle if the plugin needs fixing ?
For all tier2 plugins which are maintained at Jenkins, but kept compatible with Hudson, we need to work with the author to find solution that works at both places.

If other plugins (tier3 & tier4) are needed to be updated, we may have to fork them and maintain at hudson-plugins.

btw. It is the Role based security plugin, which gives this error when
saving hudson config (after activating)

Caused by: java.lang.ClassNotFoundException:
	at org.aspectj.weaver.bcel.ExtensibleURLClassLoader.findClass(
	at java.lang.ClassLoader.loadClass(
	at java.lang.ClassLoader.loadClass(
	... 71 more

This issue happens because we moved from acegisecurity (older version) to Spring Security (newer version) in the core, as needed during Eclipse review. In this case we have to fork the plugin.

- Winston

Best regards

2012/1/18 Winston Prakash<winston.prakash@xxxxxxxxx>:
I'm pleased to announce the availability of first milestone (M0) of Hudson
3.0.0 release from the Eclipse Foundation. The war file can be downloaded

This is our very first release of Hudson as a top level technology project
from Eclipse foundation, albeit a Milestone. I wish releasing Hudson from
the Eclipse foundation is as simple as commitng the Hudson code base  in to
the Eclipse Git Repository and then releasing it. Unfortunately that is not
the case. Eclipse Foundation has a very stringent process for releasing  a
product under its umbrella [1]

We have done the following steps to reach this stage

Remove all the dependency on GPL/LGPL libraries [2]
Apply CQs and get approval for individual components of  Hudson code base
Apply CQ and get approval for external Javascript libraries bundled with
Use latest Original libraries rather than the patched version [4]
Provide  branded look and feel [5]
Use BIRT charts for Hudson charting needs (JFreechart can not be use because
of its LGPL license)
Check-in all Hudson code base to Eclipse git [6]
Start continuous builds at Eclipse Hudson [7]
Stabilize the code base after several library and technology changes arise
due to IP review process
QA certify the product before M0 release
Apply CQ and get approval for external Java libraries bundled with Hudson
(Pending) [8]
Apply CQ and get approval for build and test libraries used to build and
test Hudson (Pending)

I'm glad, we have done this. The entire process gave us a great opportunity
to clean up Hudson code base and make it easier to maintain in the future.
Personally, I gained lots experience in understanding the innards of Hudson
and get to know the good, bad, and uglier parts of Hudson code base.

We are not done yet. We are allowed to release Milestones from Eclipse
before completing 11&  12. We expect 3-4 months worth of work to complete
the entire CQ process (11&  12 above) and thus planned our milestones
towards final release of Hudson 3.0.0 around May-June time frame [9]



- Winston

hudson-dev mailing list

hudson-dev mailing list

Back to the top