Echelon.Providers.Abstractions
0.3.0
dotnet add package Echelon.Providers.Abstractions --version 0.3.0
NuGet\Install-Package Echelon.Providers.Abstractions -Version 0.3.0
<PackageReference Include="Echelon.Providers.Abstractions" Version="0.3.0" />
<PackageVersion Include="Echelon.Providers.Abstractions" Version="0.3.0" />
<PackageReference Include="Echelon.Providers.Abstractions" />
paket add Echelon.Providers.Abstractions --version 0.3.0
#r "nuget: Echelon.Providers.Abstractions, 0.3.0"
#:package Echelon.Providers.Abstractions@0.3.0
#addin nuget:?package=Echelon.Providers.Abstractions&version=0.3.0
#tool nuget:?package=Echelon.Providers.Abstractions&version=0.3.0
Echelon
Echelon plans and runs releases around the unit people actually work in: the task. It reads tasks from an issue tracker and merge requests from one or more VCS connections, works out everything a task waits on, orders the work into deploy waves, and drives the rollout into each environment.
This is one of the Echelon libraries. Reference them only if you are writing a provider - a VCS, a
tracker, a deploy strategy or an action handler. Most users just run the container image
(docker.io/frigat/echelon).
The package IDs match the namespaces, so dotnet add package Echelon.Providers.Abstractions gives
you using Echelon.Providers.Abstractions.
Library packages:
| Package | What is in it |
|---|---|
Echelon.Core |
Enums and pure parsing: task-key extraction, label sets, status vocabularies. No dependencies |
Echelon.Providers.Abstractions |
The provider ports and the normalized models they exchange |
Echelon.Application |
Ports, message contracts and the planning algorithm, with no Entity Framework |
Writing a provider
A provider adapter references Providers.Abstractions and nothing else of ours, so a breaking change
to a port is a compile error in your adapter on the next build rather than a surprise at runtime.
Providers are registered at compile time through keyed services; there is no runtime assembly
scanning, because a container image is rebuilt anyway.
See docs/en/providers.md.
Links
- Source and documentation: https://github.com/jrfrigat/echelon
- Container image: https://hub.docker.com/r/frigat/echelon
- License: MIT
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Echelon.Core (>= 0.3.0)
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Echelon.Providers.Abstractions:
| Package | Downloads |
|---|---|
|
Echelon.Application
Ports, message contracts and the rollout planning algorithm: dependency closure, wave ordering, the YAML ordering-rule language. Pure, with no Entity Framework, so it can be used and tested on its own. |
GitHub repositories
This package is not used by any popular GitHub repositories.