Ok sounds good. FWIW, the code that will actually execute on the Jenkins slave is actually just a very lightweight REST client that communicates with our "parallel test" service.
My username is brock. Hive Dev: I think that at least two more committers should create accounts so we don't have a bus factor here. Brock On Mon, Oct 28, 2013 at 1:06 AM, Roman Shaposhnik <r...@apache.org> wrote: > Hi Brock, > > For as long as these jobs don't block Bigtop > builds too much -- I'd love to help. > > I think the easiest would be for you to register > on our jenkins: > http://bigtop01.cloudera.org:8080/ > and then let me know your creds. I can > give you enough karma to manage jobs/etc. > > Given that we already have a few jobs > running unit tests: > http://bigtop01.cloudera.org:8080/view/UnitTests/ > you can just follow those examples and > set up yours. > > Thanks, > Roman. > > On Fri, Oct 25, 2013 at 8:17 AM, Brock Noland <br...@cloudera.com> wrote: > > This proposal already has support from the Hive community but adding > > dev@hive as an FYI. > > > > On Thu, Oct 24, 2013 at 2:18 PM, Brock Noland <br...@cloudera.com> > wrote: > >> Hey guys, > >> > >> Hive doesn't have any dedicated Apache Jenkins executors and sometimes > >> our precommit jobs wait for hours to execute. I'd like to move our > >> jenkins jobs to the BigTop jenkins. > >> > >> Post move, the Hive project would remain 100% responsible for > >> maintaining and debugging our jobs. The only thing I see required on > >> the BigTop front is creating accounts for the hive team members who > >> need access. > >> > >> Thoughts? > >> > >> Cheers, > >> Brock > > > > > > > > -- > > Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org > -- Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
