 |
Page History
...
The purpose of this document is to document the current Docker setup at Mayo and how this setup can be duplicated at NCI and extended to provide additional testing, reporting and deploymentNCI which provides extended testing and reporting.
In the future, we will set up LexEVS to be deployed via Docker containers.
Overview
The Mayo development team currently has Docker and Jenkins setup locally to build and test all of the LexEVS components. It is our intent to move this setup to NCI for a more permanents permanent and stable location. Additionally, we intend on working with the systems team to prototype deploying LexEVS in as Docker containers.
LexEVS System Test
The lexevs-system-test is a Docker script that builds and tests all of the LexEVS components. Jenkins is used to kick off the Docker script.
Jenkins
When the Jenkins build is started, it simply calls a Docker script, passing in parameters that define the LexEVS component branches.
When the Docker script completes, the Jenkin build captures the test reports (XML) files.
Docker
The Docker script is where all of the work is done.
...
- Builds MySQL containers
- Clones LexEVS and LexEVS Remote projects from Git and builds each component
- Creates a container for the URI Resolver
- Builds and runs Junit tests for CTS2
- Runs Junit tests against LexEVS
- Loads terminologies into LexEVS
- Creates a container for LexEVS Remote
- Creates a container for CTS2
- Runs Junit tests against LexEVS Remote
- Stops and remove all containers.
NCI
When possible, we would like to move the current Jenkins/Docker setup from Mayo to Currently the lexevs-system-test is configured and running nightly at NCI.
Additionally, we would like to create more standard containers based on NCI's technology stack and have the containers stored in Nexus for us to pull into our builds. For example, we would like to create a container with NCI approved technology. These containers may include the following:
...
Once we have the current setup running at NCI, we would like to start looking at the following items:
- Create and store known "standard" containers (based on NCI's technology stack) in the NCI Nexus server.
- Use the build script that builds all of the LexEVS components and deploy them to a NCI DEV server for further testing/usageWork with the Systems team to develop LexEVS Docker container(s) that could be deployed to an NCI DEV Docker environment that could be used for testing.
NCI Configuration
These are the links to the systems at NCI that have been set up for migrating our lexevs-system-test script to NCI.
...
