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

Integration improvements between MCCS sub-components

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

Details

    • True
    • LOW ART
    • Hide

      Needed to speed up the release process for the overall MCCS component.

      Show
      Needed to speed up the release process for the overall MCCS component.
    • Hide
      • Enable MCCS developers to release a new version of MCCS as quickly (target less than a few hours for software-only releases) and as frequently as possible (TBD: approx target ~1 canary release / day)
      • Follow a demo by Giorgio Brajnik on the new integration test harness for SKA software (see here). Investigate the test harness before deciding whether or not to adopt it in a future PI (small spike), and provide some feedback to Giorgio.
      Show
      Enable MCCS developers to release a new version of MCCS as quickly (target less than a few hours for software-only releases) and as frequently as possible (TBD: approx target ~1 canary release / day) Follow a demo by Giorgio Brajnik on the new integration test harness for SKA software (see here ). Investigate the test harness before deciding whether or not to adopt it in a future PI (small spike), and provide some feedback to Giorgio.
    • 2
    • 2
    • 0
    • Team_MCCS
    • Sprint 4

    • PI24 - UNCOVERED

    • Team_MCCS mccs_software testing

    Description

      The release process for the overall MCCS component could speeded up by improving the integration testing between the sub-components. This has given trouble to the release process; although the different repos were passing their integration tests (against the other releases), when it came to integrating all the latest (main branch) repos together, that is when issues emerged. The suggestion is to have regular "Canary" builds that integrate main branch from all repos.

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-152 Release, deployment & integration improvements

          • High - Serious problem that could block progress.
          • Implementing

          Structure

            Activity

              People

                Thomas.Franzen Franzen, Thomas
                S.Melhuish Melhuish, Simon
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (75.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do12.0
                  In Progress   00.0
                  Complete56.0
                  Total68.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel