I have finally configured my environment enough for setting up a basic Hudson plugin. Basically I have followed the brief overview from here: http://wiki.hudson-ci.org/display/HUDSON/Plugin+tutorial. The biggest problem I had where that the mvn hpi:create didn´t recognize the systemPath to tools.jar in the JAVA_HOME lib folder. When running the command in debug mode I found out that the pom somehow expected the JAVA_HOME to be pointing to the JRE subfolder. When changing this I succeeded to create a project, download a skeleton project, make some changes, deploy it and run a locale debug instance of Hudson with the changes reflected. Great!
I am considering to write a plugin dedicated to Flex application build jobs. Are there any special needs out there, that could be covered by a such plugin?
If you enjoyed this article, please consider sharing it!
Why yes there is! AsDoc, Packaging of AIR projects to mention the two on the top of my mind
I don´t think that withdrawals with asdocs.exe and adl.exe, should be solved with a Hudson plugin. This is also the case with unsatisfying Ant Flextasks (mcml, compc), or flex-mojo´s. Instead I think that these issues should be solved in those tools. I am more thinking about Flex(As3/SWF specifics for a Hudson job – like making configuration/testing easier, rendering som nice view/statistics….
By making a plugin like this I actually hope to make Hudson more appealing for the Flex Community and that this will engage more people in the future of this great CI server.
1. Setting Flex SDK in Global Config, like the JDK;
2. Publish ASDoc;
…