|Headless build without RCP [message #1353460]
||Tue, 13 May 2014 23:05
| B B
Registered: July 2009
I've been using headless Buckminster on Jenkins to build an RCP thick-client for about 6 years. Recently I have been tasked with setting up a CI server for a set of Spring applications that run as jars and wars on a set of EC2 instances.|
Having familiarity with Jenkins and Buckminster, I elected to try that route. I created OSGi artifacts for the plugins and downloaded Virgo. I created a cpsec and an rmap, which both work well from the Eclipse workbench; I can then use the basic PDE wizards to export my plugins and drop them into Virgo. Those artifacts deploy and run as expected.
The problem is that I want to automate this process and I'm beginning to wonder whether I've misappropriated Buckminster. Everything materializes on my Jenkins server, but all the examples of actually building seem to involve RCP. I think this means that I will need to write my own cspex for starters, and possibly a few Ant files, but all of this leads me to a question: is this effort worthwhile or am I trying to put a square peg into a round hole? I like Buckminster, but I don't want to over-engineer this automated build, if that's what I'm doing.
I guess I could materialize using Buckminster and then run a simple console command that invokes equinox to handle building the artifacts; but I worry about stitching together something that takes a circuitous route to do something that could be handled by a simpler script.
Any thoughts would be appreciated.
[Updated on: Tue, 13 May 2014 23:07]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.12468 seconds