NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In addition to performing manual Protégé builds, automated build scripts have also been developed to facilitate the build process.   The manual process is shown for the sake of better understanding vital scripts and configuration files, and the workflow of the build.      The automated process takes care of creating the build folder directory, checking out all SVN files, and running the proper ant targets to create the folders, and finally, deploying the newly created folders to a specific location on the server.

Automated build scripts have been created for all tiers, although they have been used widely for Dev, QA, and Stage tiers only. Production tier folders are usually tested folders that are copied up from lower tiers and configured manually.

...

BUILD_DIR /app/protege/repo/1.34
BUILD_VERSION 1.4.30
BUILD_NUMBER 6

These parameters will result in the build directory residing in /app/protégé/repo/1.34/<build folder> with the Protégé admin, client, server, and explanation folders appended with '-1.34.06'.

svn.log.csh

This script can be run to provide a record of all files that were checked in prior to the build.

Steps to Run an Automated Build1.    From

  • From the bin folder, select a tier to build, then run  (i.e. ./build.dev.csh)

...

  • The build will commence, and will take anywhere from 10-15 minutes.  Monitor status on the server console.

...

  • Upon completion, navigate to /app/protégé/repo/x.x/ to verify that the build directory has been created.

...

  • Navigate to /usr/local/protégé/ to verify that the Protégé

...

  • Folders have been deployed properly.

...