[Building Sakai] building nightly - kernel snapshot version issues

View: New views
3 Messages — Rating Filter:   Alert me  

[Building Sakai] building nightly - kernel snapshot version issues

by Speelmon, Lance Day :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I think there is an issue with the process by which the nightly instances get built.  The problem as I see it lies in the relationship between:
  sakai/master/pom.xml --> <sakai.kernel.version>1.1.0-beta03-SNAPSHOT</sakai.kernel.version> 
and:
  kernel/pom.xml --> <version>1.1.0-beta04-SNAPSHOT</version>

So what does "nightly" really mean?  As it stands right now, we are building sakai/trunk against an older snapshot of kernel; i.e. 1.1.0-beta03-SNAPSHOT.  If you look at the attached shell script, it checks out and builds kernel, but because of the version mismatches, it does not actually use the kernel that gets built.  

It seems to me that the nightly builds should be building and deploying the trunk version of BOTH sakai and kernel.  I am no maven expert, but is there a way to rectify this issue with minimal pain?  That is without rewriting the pom.xml files during the build?  Thanks, L


source /etc/profile

export JAVA_HOME=/opt/jdk1.5.0_06
export PATH=/opt/jdk1.5.0_06/bin:${PATH}

export MAVEN_HOME=/usr/local/maven-2.0.10

export JAVA_OPTS="-server -Xms1g -Xmx1g -XX:MaxNewSize=400m -XX:PermSize=128m -XX:MaxPermSize=256m -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Dsakai.demo=true"

BUILD_DATE=`date "+%D %R"`

sakai-demo/bin/shutdown.sh

sleep 30

killall -9 java

rm -rf sakai
rm -rf sakai-demo
rm -rf kernel

rm -rf .m2/repository

unzip -q apache-tomcat-5.5.23.zip
mv apache-tomcat-5.5.23 sakai-demo
mkdir sakai-demo/sakai
chmod -R +x sakai-demo/bin/*

echo "(Quietly) Checking out source...."
#svn co -q https://source.sakaiproject.org/contrib/rsmart/tool-sandbox sakai
svn co -q https://source.sakaiproject.org/svn/sakai/trunk sakai
echo "(Quietly) Checking out kernel...."
svn co -q https://source.sakaiproject.org/svn/kernel/trunk kernel

cd kernel
$MAVEN_HOME/bin/mvn -Dmaven.test.skip=true clean install

cd ../sakai


REPO_REV=`svn info|grep Revision`


#/usr/local/maven-1.0.2/bin/maven -Dmaven.test.skip=true -Dmaven.tomcat.home=/opt/tomcat-nightly/sakai-demo/ bld dpl
$MAVEN_HOME/bin/mvn -Dmaven.test.skip=true -Dmaven.tomcat.home=/home/tomcat-contrib/sakai-demo/ -Pexperimental clean install sakai:deploy

cd ..

cp server.xml sakai-demo/conf/server.xml

echo "ui.service = trunk + experimental on HSQLDB" >> sakai-demo/sakai/sakai.properties
echo "version.sakai = $REPO_REV" >> sakai-demo/sakai/sakai.properties
echo "version.service = Built: $BUILD_DATE" >> sakai-demo/sakai/sakai.properties
echo "smtp=localhost" >> sakai-demo/sakai/sakai.properties
echo "smtp@...=localhost" >> sakai-demo/sakai/sakai.properties
echo "smtp.enabled = true" >> sakai-demo/sakai/sakai.properties
echo "smtp.port=8028" >> sakai-demo/sakai/sakai.properties
echo "serverName=nightly2.sakaiproject.org" >> sakai-demo/sakai/sakai.properties
echo "webservices.allowlogin=true" >> sakai-demo/sakai/sakai.properties
echo "webservice.portalsecret=nightly" >> sakai-demo/sakai/sakai.properties
echo "samigo.answerUploadRepositoryPath= /tmp/tomcat-contrib/" >> sakai-demo/sakai/sakai.properties

echo making downloadable tarball...
REV_NUM = echo $REPO_REV | cut -d ' ' -f 2
TMPDIR=sakai-nightly_contrib_bin_`date +%m%d%Y-%H%M`-r$REV_NUM
ARCHIVE=$TMPDIR.tar.gz

cd /var/tmp

tar -zcf $ARCHIVE -C /home/tomcat-contrib/ sakai-demo

md5sum $ARCHIVE > $ARCHIVE.md5

mv $ARCHIVE /var/www/html/tarballs
mv $ARCHIVE.md5 /var/www/html/tarballs


cd ~

rm -rf sakai
rm -rf kernel
rm -rf .m2/repository

sakai-demo/bin/startup.sh




Lance Speelmon
Scholarly Technologist


_______________________________________________
sakai-dev mailing list
sakai-dev@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe@... with a subject of "unsubscribe"

Re: [Building Sakai] building nightly - kernel snapshot version issues

by Anthony Whyte :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Good catch.  When kernel 1.1.0-beta03 was released on 17 October 2009, the trunk master pom <sakai.kernel.version> property should have been incremented by 1.  It was not, hence the issue you spotted.  An oversight, I reckon.

http://n2.nabble.com/Sakai-Kernel-1-1-0-beta03-released-td3840477.html

The steps should be

1) perform a K1 1.1.x release
2) update trunk master pom  <sakai.kernel.version> to latest 1.1 snapshot
3) when created, update the 2.7.x branch master pom <sakai.kernel.version> property to latest 1.1 stable release
4) update the standard tool poms <sakai.kernel.version> as necessary in the purepoms project.  A kernel 1.1 release will also require a purepoms release.

I'll fix it trunk now and have a look at purepoms.

Cheers,

Anth




On Oct 29, 2009, at 3:32 PM, Speelmon, Lance Day wrote:

I think there is an issue with the process by which the nightly instances get built.  The problem as I see it lies in the relationship between:
  sakai/master/pom.xml --> <sakai.kernel.version>1.1.0-beta03-SNAPSHOT</sakai.kernel.version> 
and:
  kernel/pom.xml --> <version>1.1.0-beta04-SNAPSHOT</version>

So what does "nightly" really mean?  As it stands right now, we are building sakai/trunk against an older snapshot of kernel; i.e. 1.1.0-beta03-SNAPSHOT.  If you look at the attached shell script, it checks out and builds kernel, but because of the version mismatches, it does not actually use the kernel that gets built.  

It seems to me that the nightly builds should be building and deploying the trunk version of BOTH sakai and kernel.  I am no maven expert, but is there a way to rectify this issue with minimal pain?  That is without rewriting the pom.xml files during the build?  Thanks, L

<experimental_build.sh.txt><ATT00001.htm>
_______________________________________________
sakai-dev mailing list
sakai-dev@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe@... with a subject of "unsubscribe"



_______________________________________________
sakai-dev mailing list
sakai-dev@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe@... with a subject of "unsubscribe"

smime.p7s (3K) Download Attachment

Re: [Building Sakai] building nightly - kernel snapshot version issues

by Speelmon, Lance Day :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

That all sounds good Anthony (although I am still left wondering what pure-poms is...) - thanks!  What I was really asking was if there was some versioning scheme that would make this connection less fragile while still appeasing the maven deities.  Thanks, L  :)


Lance Speelmon
Scholarly Technologist

On Oct 29, 2009, at 4:18 PM, Anthony Whyte wrote:

Good catch.  When kernel 1.1.0-beta03 was released on 17 October 2009, the trunk master pom <sakai.kernel.version> property should have been incremented by 1.  It was not, hence the issue you spotted.  An oversight, I reckon.

http://n2.nabble.com/Sakai-Kernel-1-1-0-beta03-released-td3840477.html

The steps should be

1) perform a K1 1.1.x release
2) update trunk master pom  <sakai.kernel.version> to latest 1.1 snapshot
3) when created, update the 2.7.x branch master pom <sakai.kernel.version> property to latest 1.1 stable release
4) update the standard tool poms <sakai.kernel.version> as necessary in the purepoms project.  A kernel 1.1 release will also require a purepoms release.

I'll fix it trunk now and have a look at purepoms.

Cheers,

Anth




On Oct 29, 2009, at 3:32 PM, Speelmon, Lance Day wrote:

I think there is an issue with the process by which the nightly instances get built.  The problem as I see it lies in the relationship between:
  sakai/master/pom.xml --> <sakai.kernel.version>1.1.0-beta03-SNAPSHOT</sakai.kernel.version> 
and:
  kernel/pom.xml --> <version>1.1.0-beta04-SNAPSHOT</version>

So what does "nightly" really mean?  As it stands right now, we are building sakai/trunk against an older snapshot of kernel; i.e. 1.1.0-beta03-SNAPSHOT.  If you look at the attached shell script, it checks out and builds kernel, but because of the version mismatches, it does not actually use the kernel that gets built.  

It seems to me that the nightly builds should be building and deploying the trunk version of BOTH sakai and kernel.  I am no maven expert, but is there a way to rectify this issue with minimal pain?  That is without rewriting the pom.xml files during the build?  Thanks, L

<experimental_build.sh.txt><ATT00001.htm>
_______________________________________________
sakai-dev mailing list
sakai-dev@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe@... with a subject of "unsubscribe"



_______________________________________________
sakai-dev mailing list
sakai-dev@...
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev

TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe@... with a subject of "unsubscribe"