NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 7

changes.mady.by.user Unknown User (stanclcr2)

Saved on

compared with

New Version 8

changes.mady.by.user Unknown User (endlecm)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NameRolePresent
Wright, Larry NIH/NCI   x
Fragoso, Gilberto NIH/NCI     x

De Coronado, Sherri    

NIH/NCI    x

Safran, Tracy

NIH/NCI [C] x
Ong, Kim L
IS x
Lucas, Jason R
IS x
Bauer, Scott  Mayo x
Stancl, Craig
Mayo x
Endle,  CoryMayox
Peterson, KevinMayo x
Sharma, DeepakMayo 
Wynne, Robert    NIH/NCI [C] x
Tran, Tin    NIH/NCI [C]  x
Carlsen, Brian NIH/NCI [C] x
Wong, Joanne NIH/NCI [C] 

Kuntipuram, Kumar

NIH/NCI [C]x
Jacques, Toky  

Action Items

AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
Rob

Close issue 

 

Jira
serverNCI Tracker
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId7954a81f-12da-3366-a0ef-97c806660e7c
keyLEXEVS-1516

2016.02.092016.04.10 Open
Craig

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

2016.03.092016.03.30 Open
CraigCreate JIRA issue to remove caCore legacy code2016.04.202016.04.30 Open
CoryUpdate wiki to describe what DBs are supported/tested going forward2016.04.272016.04.30 Open

...

Sprint Status

 

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

LexEVS 6.4 Agile Development - Sprint Status

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.

6.3 CTS2 service deployment The 6.3 patch has been built and deployed to QA. Tin requested that it be moved up the tiers via an email to Barry.
NCI DEV deployment updates Tracy will update the DEV server with the latest artifacts on SFTP site this week.

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.  
  • The remote was testing against real coding schemes. But 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.
  • Additionally, Kevin is working on having the Remote API run the same tests as the local LexEVS API uses.
  • Kevin has this working in his development environment and work is progressing smoothly.
  • Kevin suggested that the developer would do these Junit tests and the end user/testers would test against the real coding schemes.
    • Tracy and Larry agreed that this is a good idea.  
    • However, Larry 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.

Deployment Strategy - Artifact standard naming

LexEVS 6.4 Git Tags and Artifact Naming Conventions

We reviewed this wiki document.

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

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

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

CI Server Followup - Update 

Loader issues/tree extension issues

  • Prioritization
 

LexEVS External Users

  • Updates
 

...