There are a number of inconveniences of the sipxconfig dev environment that have crept in over the years. 1.) creating a artificial work environment to run integration tests in is very difficult to maintain code wise 2.) it takes a long time to restart the work environment after making a code change to neoconf or web layers 3.) plugins that are built outside the sipxconfig project don't have access to integration tests 4.) need to rebuild CDR, ACD postgres test DBs and now mongo DBs need test versions as well
I'm bring up these issues now as I try to port the sipxconfig build scripts from ant to automake and struggle with porting the code and scripts to construct the artificial environment. So I thought it would be prudent to look into alternative strategies for building a dev. environment. So far, using chroot utility looks promising, but it must address the three issues we currently have before I declare it as useful. So far I have sipxecs running in a chroot which is fairly promising. If you have other points you think i should address, please mention them. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
