Open
Milestone

My Crossref running on production infra

This milestone covers the development of the configuration and deployment features within the MyCrossref Frontend Application.

User Stories

  • As the Crossref development team, I want to apply different configuration values to MyCrossref, when I deploy to a particular environment, so that I can change the application's behaviour to suit the environment.
  • As the Product team, I want MyCrossref to be hosted under a staging url, so that I can acceptance test new features
  • As a Crossref member, I want MyCrossref to be hosted under a sandbox url, so that I can test my integrations against it
  • As a Crossref member, I want MyCrossref to be hosted under a production url, so that I can use it
  • As the Crossref development team, I want to apply sanity tests to configuration parameters, so that they do not break the application
  • As the Crossref member, I want to new versions of the app to be available quickly, so that I can make use of the new features

Acceptance Criteria

  • Applying environmental configuration
    • Given that specific parameters for a named environment are defined for MyCrossref
    • When the application is deployed into that environment
    • Then the configuration parameters exist in the application
  • Hosting MyCrossref under a staging URL
    • Given that new features are ready for testing
    • When MyCrossref is deployed
    • Then I can access the features via the staging URL
  • Hosting MyCrossref under a sandbox URL
    • Given there is a new version of MyCrossref
    • When MyCrossref is deployed
    • Then I can access the new version via the sandbox URL
  • Hosting MyCrossref under a production URL
    • Given there is a new version of MyCrossref
    • When MyCrossref is deployed
    • Then I can access the new version via the production URL
  • Apply sanity checks to configuration parameters
    • Given that there are updated configuration parameters
    • When MyCrossref is deployed
    • Then those parameters are tested for sanity
  • New versions are available quickly
    • Given there is a new version of MyCrossref
    • When MyCrossref is deployed
    • Then I can access the new version via the production URL without a long delay

Notes

  • In the context of this feature when we talk about applying configuration to the application, we mean applying parameters that will be pulled in via the webpack build process, and available within the Typescript code.

Related Epic

&51 (closed)

  • Work items 0
  • Merge requests 0
  • Participants 0
  • Labels 0
Loading
Loading
Loading
Loading
0% complete
0%
Start date
No start date
None
Due date
No due date
0
Work items 0
Open: 0 Closed: 0
None
Total weight
None
0
Merge requests 0
Open: 0 Closed: 0 Merged: 0
0
Releases
None
Reference: crossref%"My Crossref running on production infra"