So it is possible by editing this script to pass additional options with -D to some of the ANT commands.
Thanks for the insight, that also helps me very much with the clover update. ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Grant Ingersoll [mailto:gsing...@apache.org] > Sent: Wednesday, August 26, 2009 2:20 PM > To: java-dev@lucene.apache.org > Subject: Re: svn commit: r807763 - /lucene/java/trunk/build.xml > > Here's what is currently run on Hudson as shell: > > set -x > > export FORREST_HOME=/export/home/nigel/tools/forrest/latest > > ANT_HOME=/export/home/hudson/tools/ant/latest > > ARTIFACTS=$WORKSPACE/artifacts > MAVEN_ARTIFACTS=$WORKSPACE/maven_artifacts > TRUNK=$WORKSPACE/trunk > mkdir -p $ARTIFACTS > mkdir -p $MAVEN_ARTIFACTS > cd $TRUNK > > echo "Workspace: $WORKSPACE" > > # run build > #$ANT_HOME/bin/ant -lib /export/home/nigel/hudsonSupport/junit \ > # -Dversion=$BUILD_ID -Dtest.junit.output.format=xml nightly > # release it > #cp dist/*.tar.gz $ARTIFACTS > > #Package the Source > $ANT_HOME/bin/ant -Dversion=$BUILD_ID \ > -Dsvnversion.exe=/opt/subversion-current/bin/svnversion \ > -Dsvn.exe=/opt/subversion-current/bin/svn \ > clean package-tgz-src > # release it > cp dist/*-src.tar.gz $ARTIFACTS > > #Generate the Maven snapshot > #Update the Version # when doing a release > $ANT_HOME/bin/ant -lib /export/home/nigel/hudsonSupport/maven \ > -Dsvnversion.exe=/opt/subversion-current/bin/svnversion \ > -Dsvn.exe=/opt/subversion-current/bin/svn \ > -Dversion=2.9-SNAPSHOT generate-maven-artifacts > #copy the artifacts to the side so the cron job can publish them > echo "Copying Maven artifacts to $MAVEN_ARTIFACTS" > cp -R dist/maven/org/apache/lucene $MAVEN_ARTIFACTS > echo "Done Copying Maven Artifacts" > > # run build > $ANT_HOME/bin/ant -lib /export/home/nigel/hudsonSupport/junit \ > -Dsvnversion.exe=/opt/subversion-current/bin/svnversion \ > -Dsvn.exe=/opt/subversion-current/bin/svn \ > -Dversion=$BUILD_ID -Dtest.junit.output.format=xml nightly > # release it > cp dist/*.tar.gz $ARTIFACTS > > $ANT_HOME/bin/ant -Dversion=$BUILD_ID \ > -Dsvnversion.exe=/opt/subversion-current/bin/svnversion \ > -Dsvn.exe=/opt/subversion-current/bin/svn \ > javadocs > > #Rerun nightly with clover on > $ANT_HOME/bin/ant -lib /export/home/nigel/hudsonSupport/junit \ > -lib /export/home/hudson/tools/clover/latest/lib \ > -Dsvnversion.exe=/opt/subversion-current/bin/svnversion \ > -Dsvn.exe=/opt/subversion-current/bin/svn \ > -Dversion=$BUILD_ID -Drun.clover=true clean nightly > > #generate the clover reports > $ANT_HOME/bin/ant -lib /export/home/nigel/hudsonSupport/junit \ > -lib /export/home/hudson/tools/clover/latest/lib \ > -Dsvnversion.exe=/opt/subversion-current/bin/svnversion \ > -Dsvn.exe=/opt/subversion-current/bin/svn \ > -Dversion=$BUILD_ID -Drun.clover=true generate-clover-reports > > > On Aug 25, 2009, at 7:39 PM, Chris Hostetter wrote: > > > > > : Grant does the cutover to hudson.zones still invoke the > > nightly.sh? I > > : thought it did? (But then looking at the console output from the > > : build, I can't "correlate" it..). > > > > nightly.sh is not run, there's a complicated set of shell commands > > configured in hudson that gets run instead. (why it's not just > > exec'ing a > > shellscript in svn isn't clear to me ... but it starts with "set -x" > > so > > the build log should make it clear exactly what's running. > > > > you can see from that log: the "nightly" ant target is still used. > > > > > > > > -Hoss > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
