CI/CD overview

DataStar slots into build and release pipelines through two components and several pipeline-specific integrations.

The CLI tools

Two cross-platform .NET command-line utilities cover everything a build agent needs to do:

DataStar.Tools. Runs deployments. Takes a deployment manifest and executes it against a target database. Supports Oracle and SQL Server, audit tables, reversal-script generation, and NuGet-package publishing.
GitSources.Tools. Packages the scripts referenced by a deployment file out of a Git checkout and produces a deployable artefact (NuGet or zip) ready for Octopus or any other release tool.

Both run anywhere .NET does.

First-class task library published to the Visual Studio Marketplace.

Build pipeline. End-to-end build process driven by a work item.
Release pipeline. Using the DataStar tasks to deploy a built artefact.
Reversal. How the reversal flow is wired into a pipeline.
Artifacts / Package templates. Guidance on structuring artefacts and templates.
Individual task reference. Eight tasks, one page each.

Octopus overview. How DataStar fits into an Octopus project, with step-template JSON you can import.
Create Release, Deploy Release, Apply Reversal. Each flow end-to-end.

Bitbucket Pipelines. A worked example using the DataStar tools from Bitbucket with Jira for deployment-file storage.

Whatever the pipeline, most DataStar CI/CD flows share the same four stages:

Stage 1 pulls the deployment file (from source control, from a Jira / Azure Boards attachment, or from a shared release folder).
Stage 2 gathers the SQL scripts referenced by the manifest, the DataStar.Tools CLI, and the component templates (needed if reversal is enabled). Produces a single artefact.
Stage 3 pushes the artefact to whatever feed your release tool watches.
Stage 4 runs the DataStar.Tools CLI against the target environment to execute the deployment.

The integration pages above show how each specific CI/CD system realises this shape.