Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

Details

Type: Feature
Priority: Must have
Fix Version/s: PI11
Component/s: None
Labels:
- Team_SYSTEM

ARTs:

Services
Benefit hypothesis:

Hide

In order to provide a stable and long lived, and canonical set of software artefacts for the life time of the SKA, it is necessary to construct a service to house, curate, access control, protect, and ship them. Additionally, these artefacts should be namespaced within the realm of the organisation eg: skatelescope.org, as part of ensuring their authenticity, and control.

Show
In order to provide a stable and long lived, and canonical set of software artefacts for the life time of the SKA, it is necessary to construct a service to house, curate, access control, protect, and ship them. Additionally, these artefacts should be namespaced within the realm of the organisation eg: skatelescope.org, as part of ensuring their authenticity, and control.
Acceptance criteria:
Hide

A migration process is undertaken that moves the single source of truth for SKA development artefacts from the current Nexus solution to the adopted SKA central artefact repository:

migration process is documented

development teams are notified of the required changes so as to be prepared for additional work (migration documentation)

key artefact dependencies are analysed to find order of migration (eg: tang base, lmcbaseclasses etc.)

key artefact dependencies are migrated or rebuilt via CI to provide the necessary upstream sources for projects

Migration progress is reported during PI to inform focus required

artefacts are checked for adherence to standards and best practices prior to move (automated checks) - including PyPi, OCI, Helm, Ansible Roles/Collections

Solution Intent documentation is updated accordingly https://confluence.skatelescope.org/pages/viewpage.action?pageId=93224993
Show
A migration process is undertaken that moves the single source of truth for SKA development artefacts from the current Nexus solution to the adopted SKA central artefact repository: migration process is documented development teams are notified of the required changes so as to be prepared for additional work (migration documentation) key artefact dependencies are analysed to find order of migration (eg: tang base, lmcbaseclasses etc.) key artefact dependencies are migrated or rebuilt via CI to provide the necessary upstream sources for projects Migration progress is reported during PI to inform focus required artefacts are checked for adherence to standards and best practices prior to move (automated checks) - including PyPi, OCI, Helm, Ansible Roles/Collections Solution Intent documentation is updated accordingly https://confluence.skatelescope.org/pages/viewpage.action?pageId=93224993
Feature Points:
4.5
Initial Size:
4.5
WSJF:
6.222
Epic Link:
DevSecOps Implementation
Agile Teams:

Team_SYSTEM
Due Sprint:
Sprint 5
Story Point Burn-up:
Overdue:
Outcomes:

Hide

EngageSKA Nexus has closed down

CAR is in use

Show
EngageSKA Nexus has closed down CAR is in use
Resolved PI.Sprint:
15.4

Feature Checklist:

Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

Demos:
- OMC_ART_SystemDemo_1
Requirement Status:

PI23 - UNCOVERED
Labels_MIRO:
Team_SYSTEM
Goals_MIRO:
SPO-544

Description

Implement a central universal artefact repository to contain all SKA software deliverable including Binaries, Packages, Scripts, Tools, Images and Configuration as Code.

This is a collaborative/shared feature that requires all teams to update pipelines to integrate with the new repository

NOTE: this is subject to the timetable for moving skatelescope.org => xxxx

Attachments

Issue Links

clones

SP-953 Central Artefact Repository (selection)

Done

depends on

SP-1508 Quality checks for Nexus Artefacts naming and versions

Done

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...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...