We(rSmart) have already invested a lot in setting up this exact build/test environment in EC2. I'd be happy to have one of the guys from my team help get this running for you if you'd like. I'll share a diagram that outlines all the components and the build/test workflow so you can see end state.
-Kyle Sent from my iPad On Jun 7, 2012, at 6:07 AM, "Berg, Alan" <[email protected]> wrote: > Yes, On the same page. It would be nice to have a build pipe where we: > > build > unit test > deploy artefact's > Push data to sonar - Code Review > Deploy integration server / QA server / Even an institutes skinned server > Automate Stress / Functional /Security / Other tests and reports > Promote build ready for bug bashes. > > It is all doable, but would require some servers perhaps in the cloud. > Puppet is a great idea to lower configuration effort. I would enjoy > supporting this effort. > > > > 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: 07 June 2012 14:53 > To: OAE Development > Subject: Re: [oae-dev] oae-builds: Jenkins now using port 8888 > > I definitely want to be able to provision systems that aren't on the Jenkins > server itself. To that end, I have been working on incorporating Erik's work > with puppet[1], using Amazon EC2 as a test bed that can be set up and torn > down in just a few moments. Here is a work-in-progress CloudFormation > template for that: https://gist.github.com/2888642 > > I'd say the next obstacle to clear is that the project does not currently > have an environment that we can point Jenkins to. This could be at Amazon, or > it could be one or a couple of Linode VMs, but we haven't established that > yet. > > Running integration tests on the Jenkins server itself is really only > intended as a quick way to get the tests running all the time (like so many > things, it turns out to be not-so-quick). > > regards, > Zach > > [1] https://github.com/efroese/puppet-oae-example > On Jun 7, 2012, at 3:18 AM, Berg, Alan wrote: > >> 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
_______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
