Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-1067

Abstract CI/CD pipelines

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Enabler
    • Not Assigned
    • PI7
    • None
    • Services
    • Hide

      Enable SDLC processes to be infrastructure provider independent, and capable of being concurrently deployed and federated.

      Redevelop the deployment and management  processes for the CI/Pipeline machinery, so that it can be rebuilt and reconfigured on demand to make the entire Common Platform and Services managed by the Systems Team  portable, robust and responsive.

      Show
      Enable SDLC processes to be infrastructure provider independent, and capable of being concurrently deployed and federated. Redevelop the deployment and management  processes for the CI/Pipeline machinery, so that it can be rebuilt and reconfigured on demand to make the entire Common Platform and Services managed by the Systems Team  portable, robust and responsive.
    • Hide
      • The deployment process for GitLab runners is developed for deployment on Kubernetes.
      • A deployment process for GitLab runners is developed for deployment on VMs to service specialised shell executors (note: this will be discouraged) (this has been descoped for PI#7)
      • An automated process is developed for retiring existing runners, automatically configuring new runners, and maintaining the runner registrations for existing SKA repositories.
      • The existing runners merged into the Kubernetes cluster runners, and newly deployed VMs for shell executors (in the systems-team project).
      • The updated deployment process for the CI/Pipeline machinery is repeatable and idempotent.
      • The deployment automatically updates the global service inventory (see: SP-1061).(this has been descoped for PI#7)
      • The process runs seamlessly from the management server (see: SP-1061).
      • Systems Team documentation is updated to explain how to work with deployment process.
      Show
      The deployment process for GitLab runners is developed for deployment on Kubernetes. A deployment process for GitLab runners is developed for deployment on VMs to service specialised shell executors (note: this will be discouraged) (this has been descoped for PI#7) An automated process is developed for retiring existing runners, automatically configuring new runners, and maintaining the runner registrations for existing SKA repositories. The existing runners merged into the Kubernetes cluster runners, and newly deployed VMs for shell executors (in the systems-team project). The updated deployment process for the CI/Pipeline machinery is repeatable and idempotent. The deployment automatically updates the global service inventory (see:  SP-1061 ).(this has been descoped for PI#7) The process runs seamlessly from the management server (see:  SP-1061 ). Systems Team documentation is updated to explain how to work with deployment process.
    • 3
    • 3
    • 7
    • Team_SYSTEM
    • Sprint 5
    • Hide
      • The deployment process for runners has been automated
      • The Kubernetes based runner has been deployed as is actively taking a share of the workload for CI/CD
      • Tooling has been developed to start automating the management of runners
      Show
      The deployment process for runners has been automated The Kubernetes based runner has been deployed as is actively taking a share of the workload for CI/CD Tooling has been developed to start automating the management of runners
    • 9.3
    • Stories Completed, Integrated, Solution Intent Updated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
    • PI22 - UNCOVERED

    • Team_SYSTEM
    • SPO-544

    Description

      Redevelop the CI/Pipeline machinery deployment solution

      Attachments

        Issue Links

          Structure

            Activity

              People

                m.bartolini Bartolini, Marco
                P.Harding Harding, Piers
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete513.0
                  Total513.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel