Hey hcat gurus - short version: please run ./build-support/scripts/test.sh for routine local testing as it contains our collective knowledge of what commands to run. e2e tests have not changed.
details: In https://issues.apache.org/jira/browse/HCATALOG-558 we committed test.sh, a script that contains all the commands one should run when doing routine testing on CI or locally. As our needs change we can evolve the script and keep everyone on the same page wrt how tests should be run. I just updated https://builds.apache.org/job/Hcatalog-trunk-build/ to run test.sh, and kicked off a build. The full log what what changed is below. NEW BUILD COMMAND: #!/bin/bash source ${WORKSPACE}/nightly/hudsonEnv.sh cd $TRUNK ./build-support/scripts/test.sh PREVIOUS BUILD COMMAND #!/bin/bash source ${WORKSPACE}/nightly/hudsonEnv.sh export ANT_HOME=/home/jenkins/tools/ant/apache-ant-1.8.2 env cd $TRUNK $ANT_HOME/bin/ant -v ${BUILD_FLAGS} ${BUILD_ARGS} ${BUILD_TARGETS} REMOVED BUILD PARAMETERS AS THEY ARE NO LONGER NEEDED VERSION 0.5.0-SNAPSHOT To set build version BUILD_FLAGS -Dhcatalog.version=$VERSION -Dtest.junit.output.format=xml -Divy.default.ivy.user.dir=${WORKSPACE}/trunk/build To set build flags BUILD_ARGS -Dforrest.home=$FORREST_HOME To set various build tools home folder BUILD_TARGETS clean test docs forrest tar mvn-deploy To call regular build targets Thanks! Travis
