 |
Page History
...
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
Currently the lexevs-system-test is configured and running nightly at NCI.
When the Jenkins build is started, it simply calls a Docker script, passing in parameters that define the LexEVS component branches.
...
- 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
...
Docker Locations
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:
...
We have found in our testing that versions of the above components are regularly updated and at times, the version we specify in our script is no longer available which subsequently breaks our builds. Having consistent, known versions (based on NCI's technology stack) that are available for our builds would provide greater stability.
Next Steps
Once we have the current setup running at NCI, we would like to start looking at the following items:
...
Our next step is to work 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.
...
