Added by Anthony Perritano, last edited by Scott Cytacki on Oct 22, 2008  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

This Page is out of date.

Overview

There are two "codebases". Each codebase contains a set of jnlp files and a set of jar files. These codebases will be referred too as: frozen and snapshot. Originally this page only showed how to update the snapshot jnlps.

Update Snapshot Codebase

Getting Started

The snapshot codebase is currently located at:

http://tels-develop.soe.berkeley.edu:8080/maven-jnlp-snapshot/

Before updating the this codebase you need to Setup JNLP Deployment Environment
Before doing these steps you should make sure the jars you want have been built by continuum. this process pulls the jars built by continuum. If you just checked in some code, you will need to go to continuum and make sure it has been built:
http://www.telscenter.org/continuum/servlet/continuum/

Process

  1. ssh tels-develop.soe.berkeley.edu
  2. cd /var/local/maven-jnlp-staging/pas-jnlp
  3. ./deploy.sh

Result

When it is done there will be a new jnlp in the snapshot codebase with a timestamp. Something like:

plr-everything-jdic-snapshot-20070118-0956.jnlp

And if there have been any updates to the snapshot jars, then those will also be signed, compressed and copied to the snapshot codebase.

Update Frozen Codebase

Getting Started

The snapshot codebase is currently located at:

http://tels-develop.soe.berkeley.edu:8080/tels-jnlp/

Before updating the this codebase you need to Setup JNLP Deployment Environment
This process copies the contents from the snapshot codebase and deploys. So
Before following this procedure you should make sure the snapshot codebase contains all the jars and jnlps that you need.

Process

  1. ssh tels-develop.soe.berkeley.edu
  2. cd /var/local/maven-jnlp-staging/tels-jnlp
  3. ./update.sh
  4. ./deploy.sh

Result

When it is done the frozen codebase will match the snapshot codebase.

Rational for 2 codebases

The reason for 2 codebases is because of a flaw in the deployment of files to tomcat. Currently there is pause of about 1 minute while the old files will not be available when deploying new files. So if a class is in the middle of doing a run and a developer updates the codebase the class is using it will cause network errors.

So if possible the frozen codebase should not be updated while a classroom might be using it.