Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

Details

Type: Feature
Priority: Not Assigned
Fix Version/s: PI3
Component/s: None
Labels:
- Team_SYSTEM

Benefit hypothesis:

Hide

Abstracts the deploy and integration system architecture from the developers so to make their life easier and their time more productive.

Developers do not need to configure the entire systems, which is a very error prone activity, and can rely on a stable set of definitions to start up an integrated environment.

Show
Abstracts the deploy and integration system architecture from the developers so to make their life easier and their time more productive. Developers do not need to configure the entire systems, which is a very error prone activity, and can rely on a stable set of definitions to start up an integrated environment.
Acceptance criteria:
Hide

A developer can add a device to the integration environment acting on one single entry point (file, repo ... )

Ideally this should be tested by someone not developing this feature, with a newly introduced device

The integration environment gets configured according to the device and pulls the latest version of the device as published on the SKA artefact repository.
Show
A developer can add a device to the integration environment acting on one single entry point (file, repo ... ) Ideally this should be tested by someone not developing this feature, with a newly introduced device The integration environment gets configured according to the device and pulls the latest version of the device as published on the SKA artefact repository.
Feature Points:
5
Initial Size:
5
WSJF:
5.8
Epic Link:
DevSecOps Implementation
Agile Teams:

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

Hide

N/A (due to this feature being over 2 years old)

Show
N/A (due to this feature being over 2 years old)
Resolved PI.Sprint:
16.6

Feature Checklist:

Stories Completed, Accepted by FO

Requirement Status:

PI24 - UNCOVERED
Labels_MIRO:
Team_SYSTEM

Description

The current system for testing SKA Tango devices in an integrated environment appears complex to the uninitiated. Ideally, a user would just have to write a Tango device and then define the test environment with little more than a list of devices she would like to run the integration tests with. The CI environment would just run up these devices (and possibly their dependencies) and run the tests.

Attachments

Issue Links

depends on

SP-304 Deploy SKAMPI on the k8s cluster

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...

(8 mentioned in)

Structure

Activity

People

Assignee:: Le Roux, Gerhard [X] (Inactive)

Reporter:: Rees, Nick

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Feature Progress

Story Point Burn-up: (100.00%)

Feature Estimate: 5.0

	Issues	Story Points
To Do	0	0.0
In Progress	0	0.0
Complete	15	38.0
Total	15	38.0

Dates

Created:: 23/Apr/19 9:06 PM

Updated:: 14/Feb/24 3:09 PM

Resolved:: 01/Dec/22 9:53 AM

Easy-to-use guide on how to integrate a simple Tango device in the SKA integration environment