Repository types

The SLC SE Repo Manager has different tabs for the different repository types:

The following subsections provide more information about the different tabs.

Protocols

This tab lists repositories that contain a Visual Studio solution of a specific protocol.

Changes made to a protocol repository trigger the corresponding protocol CI/CD pipeline.

Visio files

This tab lists repositories that contain a Visio file.

Changes made to a Visio repository trigger the corresponding Visio CI/CD pipeline.

Custom solutions

This tab lists repositories that contain a Visual Studio solution. These are typically class library solutions that are in turn used by e.g. protocols or Automation scripts.

Changes made to a custom solution repository trigger the corresponding custom solution CI/CD pipeline.

The Custom Solutions tab contains an additional icon that, when clicked, adds another JenkinsNuGetConfiguration.xml file that allows you to enable and configure NuGet-related stages in the pipeline.

Functions

This tab lists repositories that contain a function.

Changes made to a function repository trigger the corresponding functions CI/CD pipeline.

Automation scripts

This tab lists repositories that contain an Automation script solution, which might consist of one or multiple Automation scripts.

Changes made to an Automation script repository trigger the corresponding Automation script solution CI/CD pipeline.

Dashboards

This tab lists repositories that contain a dashboard.

Changes made to a dashboard repository trigger the corresponding dashboard CI/CD pipeline.

Examples

This tab lists repositories that contain an example protocol or Automation script.

Changes made to an example repository trigger the corresponding example CI/CD pipeline.

Packages

This tab lists repositories that define an install package.

Changes made to a package repository trigger the corresponding install package CI/CD pipeline.

Files

This tab lists repositories that contain files. These are typically repositories that are used as part of a package.

These repositories are not linked to a CI/CD pipeline.