Bpel build process
483078Aug 30 2006 — edited Jan 10 2008Hi,
I´m in the process of creating an ant build script which will build and deploy our bpel application using a continuous integration (continuum) server. I need some advice on the best approach for this.
These are some of my requirements:
* separate hourly and nightly builds. The hourly build will run during working hours and will only compile our code. The nightly build will do a full build, including deployment, code generation, unit testing, qa, etc.
* deliverables should be deployable on multiple environments. For example, i want to generate 1 bpel jar, install it on a test environment, test it, and install exactly the same jar on acceptance and production. (machines may have different names, ports, etc).
* No deployment required for compiling. I want to be able to compile a project without having to first install projects on which it depends. This means that i cannot refer to installed wsdl's. Without this, requirements 1 and 2 cannot be met.
* I need to be able to generate jars which can be send to multiple customers (like a product). A customer should be able to customize a bpel without having to modify the contents of a pbel jar. This means that all the url's in the bpel need to be able to use environment variables defined in the application server. I should not have to recompile to be able to send a new customer an existing bpel (i can't, as i don't know the infrastucture of the customer).
Any idea's, tips, tricks?
Thanks,
Andrej