Hi P. Taylor Goetz Did any progress ever get made on this? On Wed, Dec 18, 2013 at 10:14 AM, FangKun Cao <[email protected]> wrote:
> Hi P. Taylor Goetz > > I have successfully running Storm CI on Jenkins , see attachment > screenshot. > Following is my install mannal , hope this can help you . > > $ yum install epel-release > $ yum install clojure > $ wget https://raw.github.com/technomancy/leiningen/preview/bin/lein lein > $ chmod a+x lein > $ ./lein > $ vim ~/lein/profiles.clj > {:user {:plugins [[lein-difftest "1.3.8"] > [lein-marginalia "0.7.1"] > [lein-pprint "1.1.1"] > [lein-swank "1.4.4"] > [no-man-is-an-island/lein-eclipse "2.0.0"] > [lein-package "2.1.1"] > [test2junit "1.0.1"] > [lein-cloverage "1.0.2"] > > ] > } > } > > > $ yum install libuuid-devel > $ yum install git > $ yum install ruby > $ yum install ruby-json > $ yum install rubygems > > $ git clone https://github.com/apache/incubator-storm > $ cd incubator-storm > $ bin/install_zmq.sh > $ cd storm-core > $ lein test2junit > $ lein cloverage > > > > 2013/12/18 Doug Cutting <[email protected]> > >> You don't need a build host, just an account on the Jenkins server so >> you can configure your build. >> >> I just tried to add you to the right LDAP group but I don't have the >> privileges. I think it's supposed to be self-serve through the >> project chair. If you ask nicely on #asfinfra IRC if someone will >> probably just add you, failing that you can send the Incubator project >> chair (Marvin) a note asking. >> >> Doug >> >> On Tue, Dec 17, 2013 at 3:25 PM, P. Taylor Goetz <[email protected]> >> wrote: >> > Thanks Doug. >> > >> > Good point on just having the build process download and install it. >> That’s probably the path of least resistance. >> > >> > Should I query builds@ to see if someone can set up a build host for >> us? >> > >> > - Taylor >> > >> > On Dec 17, 2013, at 6:19 PM, Doug Cutting <[email protected]> wrote: >> > >> >> You don't have to use Maven, but it does simplify Jenkins >> configuration. >> >> >> >> You could probably get Leiningen installed on the build hosts, or you >> >> might just have your build script download it to your workspace when >> >> it's not present. (Jenkins workspaces persist.) >> >> >> >> Dunno about Vagrant. >> >> >> >> These questions are probably appropriate for the builds@ list rather >> >> than for just your mentors. >> >> >> >> Doug >> >> >> >> On Tue, Dec 17, 2013 at 2:56 PM, P. Taylor Goetz <[email protected]> >> wrote: >> >>> I’d like to get started with setting up Storm CI on Jenkins. My >> understanding is that mentors have to initiate that (as opposed to INFRA). >> >>> >> >>> A few questions/comments about our build process: >> >>> >> >>> Storm’s build system is Leiningen [1], which I didn’t see as an >> option in the Apache Jenkins docs. Is this a problem? Are we going to have >> to move to maven instead? Are there any other Apache projects using >> Clojure, and if so what are they using? >> >>> >> >>> For testing Storm in distributed (multi-node) mode, would it be >> possible to use something like Vagrant [2] to spin up a cluster for >> automated integration testing? >> >>> >> >>> Thanks, >> >>> >> >>> Taylor >> >>> >> >>> [1] http://leiningen.org >> >>> [2] http://www.vagrantup.com >> > >> > > > > -- > Best wishs！ > Fangkun.Cao > -- Best wishs！ Fangkun.Cao
