Uploaded image for project: 'SAFe Solution'
  1. SAFe Solution
  2. SS-80

All artefacts are released and uploaded to the CAR

    XporterXMLWordPrintable

Details

    • Enabler
    • Must have
    • PI12
    • None
    • Data Processing, Obs Mgt & Controls, Services
    • Hide

      In order to improve the identification and tracability of software releases at the component and aggregate level (Skampi), a set of tools and processes are proposed:

      • Commits are correctly labelled with the relevant Stories/Features relating to a new tagged version 
      • ChangeLogs are automatically generated and used to populate GitLab release pages illustrating commits/Stories/Features involved in a tagged release
      • The tagged source code version, release page and related artefacts published are published on a related REL Jira project ticket
      • These processes are automated via gitlab-ci templates 
      Show
      In order to improve the identification and tracability of software releases at the component and aggregate level (Skampi), a set of tools and processes are proposed: Commits are correctly labelled with the relevant Stories/Features relating to a new tagged version  ChangeLogs are automatically generated and used to populate GitLab release pages illustrating commits/Stories/Features involved in a tagged release The tagged source code version, release page and related artefacts published are published on a related REL Jira project ticket These processes are automated via gitlab-ci templates 
    • Hide
      • All artefacts are released following a coherent process at a very high level, including: 
      • All repositories generate artefacts that are uploaded to the CAR
      • Nexus on EngageSKA can be turned off as there are no more artefacts required to be served from there
      Show
      All artefacts are released following a coherent process at a very high level, including:  Gitlab Release page at the repository level For all PBS level products: ( the modules in our system level modules view https://confluence.skatelescope.org/display/SWSI/Views%3A+Module  ) The Release is tracked in the Jira Release Management Project using the   Product Version  issue type https://jira.skatelescope.org/projects/REL/summary   Release is planned and advertised in the Release Management Forum  All repositories generate artefacts that are uploaded to the CAR Nexus on EngageSKA can be turned off as there are no more artefacts required to be served from there
    • Overdue

    • PI22 - UNCOVERED

    Description

      This Solution Enabler is to roll out a first form of release process across the collaboration. 

      The Services train will have to support this capability, while the OMC and DP trains will have to implement the necessary changes. 

      As part of this capability: 

      • All artefacts are released following a coherent process at a very high level, including: 
      • All repositories generate artefacts that are uploaded to the CAR

       

      Notes: https://confluence.skatelescope.org/display/SE/Release+Management+Process+-+Scratch+Pad 

      Attachments

        Issue Links

          is required by

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SS-82 Make sure SKAMPI is stable for developers and users

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Releasing
          Parent Of

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-2112 dspsr-test migration to new CAR

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Funnel

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1821 Complete Raw Artefact CAR Integration

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1844 All artefacts are migrated to CAR

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-2319 Update PST TANGO devices and supporting infrastructure

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1802 Communicate releases for Artefacts, and contributing components

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1820 Complete Conan CAR Integration

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1838 Automated Artefact Releases

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-2160 Port CBF/PST Interface to CAR

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done
          relates to

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1850 Support SKA-base class migration to v0.11

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Discarded

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1941 Establish / refine process / reporting tool(s) for determining the current status of functionality for each product

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Analyzing
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          mentioned on

          GitLab Commit - Merge branch 'ss-80-move-ci-image-to-car' into 'master'

          GitLab Commit - SS-80 Ensure processor gets GC'd after every test

          GitLab Commit - SS-80 Fix docker tagging for GitLab container repo

          GitLab Commit - SS-80 Move CI image to CAR

          GitLab Commit - SS-80 Move CI image to CAR

          GitLab Merge request - SS-80 Create arrow images on GitLab, fix test cases

          Features

          Structure

            Activity

              People

                m.bartolini Bartolini, Marco
                m.bartolini Bartolini, Marco
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (87.10%)

                  Feature Estimate: 0.0

                  IssuesStory Points
                  To Do12.0
                  In Progress   00.0
                  Complete813.5
                  Total915.5

                  Capability Progress

                    Feature Point Burn-up: (86.67%)

                    Capability Estimate: 0

                    CountFeature Points
                    Todo12
                    In Progress   00
                    Done813
                    Total915

                    Dates

                      Created:
                      Updated:

                      Structure Helper Panel