Re: [Architecture] Automatically deleting old BPEL processes that do not have any associated process instances in BPS

2014-02-18 Thread Pulasthi Supun
Hi Nandika, Yes with the current process that involves Jenkins and puppet the md5 of the zip file that is generated does change every time puppet runs this is the reason why versions are created all the time. we are looking into solving this by changing the deployment process. is

[Architecture] Automatically deleting old BPEL processes that do not have any associated process instances in BPS

2014-02-17 Thread Pulasthi Supun
Hi All, In BPS when we directly copy a new zip ( which is identified by the md5sum of the zip file ) file of an existing BPEL process to /repository/deployment/server/bpel folder this will be picked up as an new version of the process and the existing process will be kept as a retired process (

Re: [Architecture] Automatically deleting old BPEL processes that do not have any associated process instances in BPS

2014-02-17 Thread Nandika Jayawardana
Hi Pulasthi, Are you using the maven-bpel-plugin to build the zip file. It seems like the plugin is generating a zip file which produces a different md5sum each time even though the content of the bpel package has not changed at all. This must be the reason for you issue. Regards Nandika On