NIH | National Cancer Institute | NCI Wiki  

Sprint Dates

 - 


Sprint Goals

  • Re-Bentofication
  • Test all user stories
  • Deploy release candidate to Stage

Sprint Jira Issue Types

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

Completed in Sprint 

com.atlassian.sal.api.net.ResponseException: Could not parse json from Jira

Sprint Schedule

DateScrum CeremonyPurpose

Sprint KickoffInitiate new sprint

  

Sprint Pre-planning Review tasks targeted for next sprint and identify clarifications needed, apply initial story point estimations and initial projected assignees

 

Sprint PlanningReview prioritized tasks, assert assigned stories, assert final story point estimations, review story points by assignee

  

Sprint Review & RetrospectiveDemo work completed, discuss what went well and what can be improved

Software Release Information

DateBuild TypeRelease Blocker FoundFront-End VersionBack-End VersionFile System Version

 

Release Candidateyes3.59.214.8.0.771.4.0.59

 

Release Candidateyes3.59.314.8.0.771.4.0.59

  

Release Candidateyes3.59.414.8.0.771.4.0.59

 

Release Candidateyes3.59.514.8.0.771.4.0.59

 

Release Candidateyes3.59.614.8.0.771.4.0.59

 

Release Candidateno3.59.714.8.0.771.4.0.59

Release Blocker Bugs (High impact to release schedule)

Jira IssueDescription
ICDC-3159JBrowse doesn't open as a new session window and still supports navigation
ICDC-3160JBrowse button on Explore Page not consistent with approved design and function
ICDC-3163JBrowse button on Cart Page not consistent with approved design and function
ICDC-3168File Manifest download icon is blurred
Data Model Navigator text is overlapping Filter & Search text box
ICDC-3175On the Case Files tab the "All filtered files" button does not add all files
ICDC-3185Clicking the PDF icon on READMe file in "My Files" Cart Page downloads as csv
ICDC-3186Alignment issues on the "My Files" Cart Page READMe PDF 
ICDC-3202Unable to open files in JBrowse due to CORS policy

DevOps Post-Mortem (High impact to release schedule)

Jira IssueDescription NotesPath Forward
ICDC-3194Deploy Interoperation Microservice to Stage and ProductionWork with CloudOne to run deployment pipelines and update necessary secretsSynchronize resources across upper and lower tiers.
ICDC-3145Add Interoperation Microservice URL to exception listThe production WAF has a size limitation of 8KB if a request is made larger than that we need to have our microservice added to a "whitelist" so that it can request a larger payloadNew microservices need environment review from DevOps team.
ICDC-3146Mitigate WAF restriction to ICDC CloudFront DistributionsThere is a WAF rule limiting data push to the CloudFront distribution. Each AWS account has a soft and hard limit. CloudOne had exhausted their soft limit and had to go back to AWS for workaround.New microservices need environment review from DevOps team.
ICDC-3204Update PEM key for the Files MicroserviceWithout a valid PEM key the application cannot process download requests. To sign URLs a private key is needed. The File service was not using Fargate making this more challenging.Synchronize resources across upper and lower tiers.
ICDC-3207Standup a dedicated CloudFront Distribution for StageA single CloudFront (CF) distribution is not sufficient to serve multiple instances of an application since CF caches the "Access-Control-Allow-Origin" header causing errors when fetching the same file across multiple tiers within a limited timeframe.A dedicated CF distribution for each tier in their own domain all accessing the production AWS S3 bucket.

Sprint Retrospective

ICDC Sprint 40 Retrospective

  • No labels