Hi,
This mail is to get your feedback and idea on integrating the modules
development to continuous integration (CI)
which means as we have pi development are tracked/compiled/tested in
builds.openbravo.com, the modules that are in development phase will
be continuously compiled and on success generate obx for testing.
The Ultimate goal is to have a job in "builds.openbravo.com" and
trigger it periodically and report the results to appropriate team.
Here we have the proposal on how to integrate modules to CI and make
them available to appropriate team to track.
* Have the ERP source in hudson local workspace to compile and build
the obx, periodic polling to pi branch will be done and
the workspace will be updated to the latest changeset.
* The main module (in development phase) and the dependent/included
modules are cloned to <path to workspace>/modules/
* Monitor the modules source repo (which includes main module,
dependent and included modules) for new changeset, if any of the
module in the list is with new changeset, then trigger on the compile
and build the obx for the main module. Targets that gets triggered for
every build are
* install.source
* package.module -Dmodule=<org.openbravo.module>
* On failure, e-mail notification will be sent to appropriate team.
We also like know how you would like to have the jobs to be, options
1) One job for each team (erp_devel_mods-loc, erp_devel_mods-platform,
erp_devel_mods-eng-dev ...)and configure it based on the module your
team is currently working and modify it when the team takes up another
new module development.
2) One job for each active module (erp_devel_mod-advpaymentmngt,
erp_devel_mod-generictreereport, erp_devel_mod-uiselector ...) and
remove the job when the module has no more development activity and
create a new job for next active module.
Any comments/suggestion are welcome
Regards
Priya Muthukumar
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Openbravo-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-development
