Page History

...

How do I setup a new branch build?

...

1. Log into build machine, go to /usr/local/hiveptest/etc/

...

1. public, create a new profile properties in the form {newprofile.properties} , where "newprofile" is the name of the new profile.  Easiest way is to copy an existing one, for example "trunk-mr2.properties" which are used to run pre-commit tests.
2. In the new profile property, set the "repository" property in the new profile to point to the new branch

...

1. , and "repository-name" property to any unique value (will be used as the directory name of the checked-out code).  Set any other properties accordingly, as they will be invoked by the jenkins build.
2. In Jenkins, create a new job by copying template from existing job.
3. In new Jenkins job, go in the build config modify the profile argument in the Hive PTest2 WebServer call (it will be like: "java ... org.apache.hive.ptest.api.client.PTestClient --profile trunk-

...

1. mr2") to point to

...

1. the new profile  ie, ("java ...–profile newprofile).

How can I read or make changes to Hive PTest2 Infra code?

...

$ sudo /usr/local/hiveptest/bin/stop-server.sh 
$ sudo /usr/local/hiveptest/bin/start-server.sh 
$ sudo /usr/local/hiveptest/bin/restart-server.sh 
$ sudo /usr/local/hiveptest/bin/update.sh 

How do I change a build to run a new MiniMr/TezDriver q-test?

See: MiniMR+and+PTest2.

This is all same as configuring any build profile property, located at /usr/local/hiveptest/etc/public.  Find the profile properties of your build (for example the pre-commit tests are using "trunk-mr2.properties), and edit "qFileTests.miniXXXDriver.groups...." to include the name of the new q-test.  TODO- link to more complete instructions.

...