Page History

...

1. A new release will be tagged in the github project https://github.com/ncievs/nci-protegeprotege5.git
2. Navigate to Jenkins at https://evs-jenkins.nci.nih.gov/jenkins/job/_default/job/_lower/job/_Protege/
3. Choose protege_build > Build with Parameters and select the appropriate tag in the BRANCH_OR_TAG selection box and click Build
4. Review the Console Output for any errors
5. For Dev, choose protege_deploy_dev > Build with Parameters. You should be presented with the same tag. Click Build
6. Review the Console Output for any errors
7. Check the protege dev server and see that the /local/content/protege/protege-server and protege-desktop have been updated
8. Confirm the service has started by checking /local/content/protege/logs/protserv-console.txt for "Admin server has started at port 9091"

...

1. A new release will be tagged in the github project https://github.com/ncievs/nci-protegeprotege5.git
2. Clone the new release into a new directory in /local/project.  "git clone https://github.com/ncievs/nci-protege5.git nci-protege-V<tag>"
3. Enter into the scripts subdirectory "cd nci-protege-V<tag>/scripts/"
4. Run the build script, passing in the version number "./build.sh <tag> ncievs >> build.log".
5. Review the output for errors or build failures: "cat build.log | grep FAILURE"
6. Check the structure of the build.  The following folders and files should be present under <build-location>/nci-protege5/scripts/nci-protege5
   • binaryowl
   • explanation-workbench
   • metaproject
   • nci-protege_<date>.tar.gz
   • nci-protege_<date>.zip
   • owlapi
   • protege
   • protege-server
   • run-protege.sh
   • run-server.sh

...