Hi Zach, I would be concerned with the stability of Jenkins. With the static code review going on, builds and integration tests Jenkins will get more complex to maintain and Jobs might fail more often requiring more sys admin effort.
I would suggest deploying with cargo or some such mechanism (scp plugin) and dedicate a whole VM to an integration server. You can then incrementally hook in automatic stress tests and Functional tests. You can also consider have a slave Jenkins server which then does any significant work leaving the Master with the task of keeping the artefact's up to date. I have been putting off automating testing from the Jenkins server until I could separate out from the core business. Regards, Alan Alan Berg Group Education and Research Services Central Computer Services University of Amsterdam ________________________________ From: [email protected] [[email protected]] on behalf of Zach A. Thomas [[email protected]] Sent: 06 June 2012 22:26 To: OAE Development Subject: [oae-dev] oae-builds: Jenkins now using port 8888 Hi, all. I'm working on getting Jenkins to run our integration tests automatically whenever the nakamura build completes successfully. Because our integration tests assume they'll be running against localhost:8080, I did the simple thing, which was to change the port Jenkins is running on. So whenever you want to check in on Jenkins, you'll find it at http://oae-builds.sakaiproject.org:8888/ This system is not currently all that happy running the integration tests. If I work out these issues, we'll have a nice feedback loop for finding new defects fast. regards, Zach
_______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
