LexEVS Meeting Minutes - 2016.06.01

De Coronado, Sherri    

Safran, Tracy

Kuntipuram, Kumar

Close issue 

  LEXEVS-1516 - Getting issue details... STATUS

Create JIRA issue to update CTS2 service to use Apache Commons Collections Version 3.2.1 (security issue)

• Sprint 31
• On going Support

• Sprint 31
• On going Support

• Sprint 31

• Sprint 31
• Agile Admin

Sprint Status

Current Sprint -  Sprint 31 (May 26, 2016 – June 08, 2016)

LexEVS S13-500 Agile Development - Sprint Status#SprintStatus-Sprint31

LexEVS artifacts are built and on the SFTP site.

Scott is focusing on code clean up and Cory is working on LEXEVS-1789.

Kevin is working on the Remote API testing and making it more generic.

The CTS2 6.3 patch has been built and deployed to QA.

Tin requested that it be moved up the tiers via an email to Barry.

LexEVS testing strategy

• Remote API testing

• System level testing

Remote API testing

• Kevin presented an overview on the remote API testing was done in the past and how he suggested we perform tests going forward.
• The lexevs local API tests against made up coding schemes (automobiles and others).  
• The remote API was testing against real coding schemes. However, there is a lot of potential maintenance with this approach.
• Kevin is working on running the remote API against the same made up coding schemes as the local LexEVS API.
• Kevin has this working in his development environment and work is progressing smoothly.
• Kevin suggested that the developer would do the Junit tests and the end user/testers would test against the real coding schemes.
  • Tracy and Larry agreed that this is a good idea.  
  • Larry noted that he would like the ability to run these tests without having to update the tests each release based on coding scheme changes.
• Kevin mentioned that using the local LexEVS tests would provide more coverage of the remote API codebase.
• Kevin agreed that the tests against the real coding schemes still have great value and should still be run at some level.
• At the QA tier, Tracy was suggesting that we run more integration tests that are similar to the current remote API tests against real coding schemes.
• Mayo would work with Toky to get this set up on NCI's CI server.

Craig will set up a meeting to meet with Toky, Tin, and Tracy to give an overview of Kevin's work on Jenkins using Docker with LexEVS.

LexEVS 6.4 Git Tags and Artifact Naming Conventions

We reviewed this wiki document.

Toky suggested having a property file that would have the artifact names. Jenkins could then ingest this file.

Tracy was questioning why the tag and file name changes at each tier level.

• There was a lot of conversation and concern about renaming artifacts as they go from QA to PROD.

Loader issues/tree extension issues

• Prioritization

This was discussed offline in an email.

• Gilberto set the priority of all OWL2 loader issues as high priority (except for LEXEVS-1337, which is medium priority). The “high” priority items are needed to use this loader in production.
• These need to be completed no later than end of FY16.

LexEVS External Users

• Updates