a) the why don't we -- we are working on this right now. I just came out of a design session that will make standing up development enviornments easier. Until now, our services were not that complex. As things on the project are maturing, we now see developers requiring more complex dev environments.

b) on continous integration, we are well aware of jenkins and other tools for doing this. We had CI running before christmas as a prototype, and then took it off line. We are working on bringing this back on line and have a target timeline to have this in place for the next major build.

On Mar 10, 2014, at 4:11 PM, Roman Sutormin <rsutormin@lbl.gov>

wrote:

Hello everybody,

I have little bit strange question. Why don't we make testing environment for tests in our projects?

My problem is that now I need to install local workspace service (and shock server + mongo that are used in WS) and job status service in order to be able to run tests for my service (genome comparison). But I'm sure that everybody who is developing services would be glad to have testing services and dbs that are necessary for running tests without installing all necessary parts on some random magellan instances or even locally.

Another useful outcome of testing env will be ability to install automation testing software like https://wiki.jenkins-ci.org/display/JENKINS/Unit+Test .

Thanks for your ideas and suggestions.

-Roman.

_______________________________________________
Release-team mailing list
Release-team@lists.kbase.us
https://lists.kbase.us/mailman/listinfo/release-team