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

Review and define steps needed to onboard PSS repos at T0

Details

    • Spike
    • Not Assigned
    • PI8
    • COM PSS SW
    • None
    • Data Processing
    • Hide

      PSS is a one of the core elements being developed by the ART and as such all PSS code on a route towards testing and integration as part of the SKA evolutionary prototyped (deployed using SKAMPI) and as such this should be easily discoverable by other SKA developers and provide CI metrics to be able to make an assessment of current levels of technical debt.

      Show
      PSS is a one of the core elements being developed by the ART and as such all PSS code on a route towards testing and integration as part of the SKA evolutionary prototyped (deployed using SKAMPI) and as such this should be easily discoverable by other SKA developers and provide CI metrics to be able to make an assessment of current levels of technical debt.
    • Hide
      • Review and describe the set of steps needed, and resources and support required, for enabling automated CI and (collection of CI metrics) and publishing user and developer documentation for core PSS repos that could be integrated into SKAMPI.**

      Stretch:

      • Short spike during PI8 to review and clarify status of PSS repos in SKA gitlab.
        • For active repos consider moving these into a PSS subgroup to improve discoverability.
        • For empty placeholder repos, or ones that won't be onboarded until construction (T0), consider labeling these as placeholders or removing them.
      • Timeboxed activity to implement a small number of steps towards automated CI the steps identified by this spike.
      Show
      Review and describe the set of steps needed, and resources and support required, for enabling automated CI and (collection of CI metrics) and publishing user and developer documentation for core PSS repos that could be integrated into SKAMPI.** Stretch: Short spike during PI8 to review and clarify status of PSS repos in SKA gitlab. For active repos consider moving these into a PSS subgroup to improve discoverability. For empty placeholder repos, or ones that won't be onboarded until construction (T0), consider labeling these as placeholders or removing them. Timeboxed activity to implement a small number of steps towards automated CI the steps identified by this spike.
    • 0.5
    • 0.5
    • 14
    • Team_PSS
    • Sprint 3
    • Hide

      See attachment below.

      Show
      See attachment below.
    • 8.4
    • Stories Completed, Outcomes Reviewed, Satisfies Acceptance Criteria, Accepted by FO

    Description

      Not expecting all code to meet SKA DoD, but where at all possible should report against agreed minimal set of CI metrics.

      If due to h/w dependencies a full CI pipeline cannot be run, the CI pipeline should be executed to test and report on as much as possible. If (as expected this is the case) requirements to build a full CI solution should be provided or referred to in the outcome of this ticket.

      Should review and act on the use of Gitlab groups

      Attachments

        Issue Links

          Structure

            Activity

              People

                b.mort Mort, Ben
                b.mort Mort, Ben
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 0.5

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete14.0
                  Total14.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel