Skip to content

[Epic][AP] Next Build content deploy pipeline #15952

Open
@timcosgrove

Description

@timcosgrove

Requirements & Goals

Next Build needs its own content deploy pipeline, including all requisite AWS instances, processes, etc, so that Next Build content can be viewed by the Veteran.

How will we know we've achieved our goal?

Preview Give feedback

Work

Work

Preview Give feedback
  1. Accelerated Publishing CMS Team DevOps Needs refining next-build
  2. 5 of 5
    Accelerated Publishing Needs refining
    jcbolling
  3. 1 of 2
    Accelerated Publishing Needs refining
    jcbolling

Completed work

Preview Give feedback
  1. 5 of 7
    Accelerated Publishing
    jtmst tjheffner
  2. 1 of 2
    Accelerated Publishing Needs refining
    tjheffner
  3. 0 of 3
    Accelerated Publishing
    timcosgrove tjheffner
  4. 3 of 3
    Accelerated Publishing Blocked
    alexfinnarn
  5. 1 of 2
    Accelerated Publishing
    tjheffner
  6. 5 of 5
    Accelerated Publishing Infrastructure-Services
    jschmidt-civicactions olivereri
  7. 4 of 6
    Accelerated Publishing Needs refining
    timcosgrove
  8. 4 of 4
    Accelerated Publishing Needs refining
    ryguyk
  9. 1 of 1
    Accelerated Publishing DevOps Needs refining
    olivereri
  10. 1 of 2
    Accelerated Publishing Needs refining
  11. 0 of 3
    Accelerated Publishing Needs refining

Supporting material

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Accelerated PublishingCMS TeamCMS Product team that manages both editor exp and devopsDevOpsCMS team practice areaEpicIssue typeNeeds refiningIssue statusnext-buildFE Repository that will replace content-build. Uses NextJS, builds static pages.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions