Write CI/CD pipelines in C#. Debug them locally. Ship with confidence.

You know the drill. You write some YAML, push it, wait for CI to start, watch it fail on a typo, fix it, push again, wait again. Repeat until you lose the will to live.

YAML pipelines are:

• Impossible to debug locally - "Works on my machine" but fails mysteriously in CI
• No compile-time safety - Typos in variable names? Enjoy your 10-minute feedback loop
• Copy-paste hell - Reusing logic means duplicating YAML and hoping you update all the copies
• Vendor lock-in - Switching from GitHub Actions to Azure Pipelines? Rewrite everything

ModularPipelines lets you write your CI/CD pipelines as regular C# code. That means:

Set a breakpoint. Step through your pipeline. Fix it before you push.

[DependsOn<BuildModule>]
[DependsOn<TestModule>]
public class PublishModule : Module<CommandResult>
{
    protected override async Task<CommandResult?> ExecuteAsync(IPipelineContext context, CancellationToken cancellationToken)
    {
        // This is real C#. Set a breakpoint. Inspect variables. Debug locally.
        return await context.DotNet().Publish(new DotNetPublishOptions
        {
            Project = "src/MyApp/MyApp.csproj",
            Configuration = Configuration.Release,
            Output = "publish/"
        }, cancellationToken);
    }
}

Intellisense, refactoring, compile-time errors. Your pipeline code gets the same treatment as your application code. Rename a module? Your IDE updates all the references. Typo in an option? Red squiggle before you even save.

Test your entire pipeline on your machine before pushing. No more "let me push and see if it works" commits. Debug failures in your IDE instead of reading logs from a build agent.

Modules declare their dependencies with attributes. ModularPipelines figures out what can run in parallel and maximizes throughput. No more manually orchestrating parallel jobs.

Your pipeline logic lives in C#, not in vendor-specific YAML. Moving from GitHub Actions to Azure Pipelines to TeamCity? Change one line - your modules stay the same.

Inject services, configuration, and secrets the same way you do in ASP.NET Core. Mock dependencies for testing. No more environment variable gymnastics.

Secrets are automatically obfuscated in logs. No more accidentally exposing API keys in build output.

dotnet new console -n MyPipeline
cd MyPipeline
dotnet add package ModularPipelines

// Program.cs
await PipelineHostBuilder.Create()
    .AddModule<BuildModule>()
    .AddModule<TestModule>()
    .AddModule<PublishModule>()
    .ExecutePipelineAsync();

// BuildModule.cs
public class BuildModule : Module<CommandResult>
{
    protected override async Task<CommandResult?> ExecuteAsync(IPipelineContext context, CancellationToken cancellationToken)
    {
        return await context.DotNet().Build(new DotNetBuildOptions
        {
            Project = "MySolution.sln",
            Configuration = Configuration.Release
        }, cancellationToken);
    }
}

// TestModule.cs
[DependsOn<BuildModule>]
public class TestModule : Module<CommandResult>
{
    protected override async Task<CommandResult?> ExecuteAsync(IPipelineContext context, CancellationToken cancellationToken)
    {
        return await context.DotNet().Test(new DotNetTestOptions
        {
            Project = "MySolution.sln",
            Configuration = Configuration.Release
        }, cancellationToken);
    }
}

Run it:

dotnet run

That's it. No YAML. No waiting for CI. Just dotnet run and watch your pipeline execute.

See exactly what's happening as your pipeline runs:

Get a clear summary when your pipeline completes:

ModularPipelines has strongly-typed wrappers for the tools you already use:

Package	Description	Version
ModularPipelines	Write your pipelines in C#!
ModularPipelines.AmazonWebServices	Helpers for interacting with Amazon Web Services.
ModularPipelines.Azure	Helpers for interacting with Azure.
ModularPipelines.Azure.Pipelines	Helpers for interacting with Azure Pipeline agents.
ModularPipelines.Chocolatey	Helpers for interacting with the Chocolatey CLI.
ModularPipelines.Cmd	Helpers for interacting with the Windows cmd process.
ModularPipelines.Docker	Helpers for interacting with the Docker CLI.
ModularPipelines.DotNet	Helpers for interacting with dotnet CLI.
ModularPipelines.Email	Helpers for sending emails.
ModularPipelines.Ftp	Helpers for downloading and uploading via FTP.
ModularPipelines.Git	Helpers for interacting with git.
ModularPipelines.GitHub	Helpers for interacting with GitHub Actions build agents.
ModularPipelines.Google	Helpers for interacting with the Google gcloud CLI.
ModularPipelines.Helm	Helpers for interacting with Helm CLI.
ModularPipelines.Kubernetes	Helpers for interacting with kubectl CLI.
ModularPipelines.MicrosoftTeams	Helpers for sending Microsoft Teams cards.
ModularPipelines.Node	Helpers for interacting with node / npm CLI.
ModularPipelines.Slack	Helpers for sending Slack cards.
ModularPipelines.TeamCity	Helpers for interacting with TeamCity build agents.
ModularPipelines.Terraform	Helpers for interacting with Terraform CLI.
ModularPipelines.WinGet	Helpers for interacting with the Windows Package Manager.
ModularPipelines.Yarn	Helpers for interacting with Yarn CLI.

ModularPipelines takes a different approach: each unit of work is a self-contained module class. This keeps code organized, makes merge conflicts rare, and lets you test modules in isolation.

• Parallel execution - Automatic based on declared dependencies
• Dependency management - Circular dependency detection built-in
• Strong typing - Pass data between modules with compile-time safety
• Debug locally - Set breakpoints, inspect variables, fix issues before pushing
• Build agent agnostic - Same code runs on GitHub, Azure, TeamCity, or your laptop
• Secret obfuscation - Automatic masking in logs
• Hooks - Run code before/after any module
• Skip conditions - Dynamically skip modules based on custom logic
• Requirements validation - Check prerequisites before running
• Progress reporting - Real-time console output with parallel execution visualization
• Source controlled - Your pipeline is code, version it like code

While I aim to maintain stability, minor versions may include breaking changes. These will always be documented in release notes.