This document describes the process to build and deploy LexEVS and all of its components.
Update PTEs
PTEs describe the build/deploy process for the NCI systems team to build/deploy our LexEVS artifacts.
Create a directory with the name of the release for the LexEVS PTE documents similar to this one:
ARC Documents
Update LexEVS ARC Documents - Update the tags that will be used in Git.
Building LexEVS Code
Once the code is tested and ready for a FINAL tag, update the build versions in the property files/pom.xml files
- LexEVS
- Update /lbPackager/build.properties to the FINAL release
- Check in to git
- Tag as 6.5.0.FINAL
- Build the project
- Deploy LexEVS artifacts in lbPackager/dist to the NCI sFTP site (caftps.nci.nih.gov)
- lexevs-remote
- Copy the built lexbig.jar and lexbig-test-6.5.0.FINAL-tests.jar to lexevs-remote/LexEVSService/system/lib/
- Update class path to point to lexbig-test-6.5.0.FINAL-tests.jar
- Update project version in LexEVSService/conf/deploy.properties
- Check in to git
- Build the project
- Tag as 6.5.0.FINAL
- Deploy artifacts to the NCI sFTP site (caftps.nci.nih.gov)
- lexevs-service (CTS2)
- Update pom to pull lexevs 6.5.0.FINAL
- Update lexevs-version in pom to 1.6.0.FINAL
- Check in and tag as 1.6.0.FINAL
- Build the project
- Deploy artifacts to the NCI sFTP site (caftps.nci.nih.gov)
Jenkins build script
Lexevs-system-test
