[Jboss-dev-forums] [Design of JBoss Eclipse IDE (dev)] - JBossIDE Automated Product Build

[<mcu...@jb...>]

Hey everyone..

JBossIDE's productBuild.xml ant script is up and running (insert praise to proper dieties here). I will be able to integrate hibernate tools with little to no hassle, and as soon as I can get a working build for jBPM Designer we should be able to get it working as well.

Basically, I provide a list of builders that make up the product, and where each of these builders build.directory is (it's important that they all build to the same place). The product build script supports two "product build types" at the moment: standalone, and bundle-eclipse. Standalone produces all the plugins and features installable as a large zip file (comparable to JBossIDE-XXX-ALL.zip). bundle-eclipse takes all the zips and extracts them into a clean eclipse extraction, bundles our pretty splash screen, and zips/targzs it all back up. It's important to note that bundle-eclipse will only build for the platforms set by the "platform.names" property in the productBuild's build.properties file. Currently we are just building win32 and linux-gtk.

There are issues that need to be worked out, mainly:

1) Every "platform" build requires a clean source build from each builder. I should only run the builder builds once, and use the same builds for each platform. This should cut the massive amount of time it takes for this script to execute in half (A fresh run of the script took exactly 20 minutes to execute, I estimate that each platform should add about 1-2 minutes to the build, not another 10.)

2) Builders that have dependencies from other builders (ejb3: aop + core) should use the builds from those builders rather than re-building it's dependencies form scratch. This will probably save a minute or so on the build.

3) Non-plugin dependencies. Namely: JBossAOP, Hibernate, EJB3. We are bundling current versions of the JARs from these projects with our plugins and it is imperative that we find a way to integrate our build system with the building of these components. This is where we will need to integrate with Ryan and the new jboss build system I believe, but I'm not sure how long it will be until we have this integration.

4) Update site building. It should be semi-trivial to convert the built binaries into an "update site compatible" file structure, but this hasn't been done yet.

5) Automatic cvs tagging for integration and release builds. After a succesful product build, each builder should tag it's repository with the integration and/or release build name. Any thoughts on implementation details of this are very much welcome.

6) Once we get hibernate tools and jbpm designer integrated, we need to get some space on a jboss server somewhere and run this as a nightly cron job for our nightly builds. SSH access will also be needed so the release engineer (me ;) can remotely do integration and release builds.

7) Email notification of build failures to the JBossIDE list. I'm not sure how this is going to work yet but hopefully Ryan can give me a hint on this.

8) FTP upload of builds. We need some sort of insecure access (ala sourceforge's release upload system) to a public jboss ftp server so I don't have to store username/password combos in plain text in a file in version control.

Any suggestions for features are certainly welcome. I'm going to go ahead and commit all of what I currently have to /jbosside/releng as soon as I can solve #8. I will be writing documentation for this new build system this week =).



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876510#3876510

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876510