# Orchestrate Git and CI pipelines with nodulz

Source: https://nodulz.com/use-cases/ci-pipelines

Language: en

> Editorial summary. Check the source page for current prices, availability and live data.

Start with a Git event, check out the repository and run your CI commands and checks before notifying the team.

## The day-to-day need.

Build and validation commands already exist, but their orchestration is scattered. Finding logs and understanding which step blocked the process requires several tools.

## Example: validate a branch before delivery

An event on the tracked branch starts a repository checkout. Run your build commands, perform your checks and send a notification when the sequence completes.

## Without a workflow

The team fetches a branch, runs commands and gathers logs before communicating the result.

## With nodulz

A Git event starts checkout, commands and checks in that order; notification follows successful steps.

## How nodulz solves the problem.

nodulz orchestrates your existing build tools. Repository and Git reference enter the workflow, then CI steps use the context prepared by checkout.

### A shared Git context

The trigger selects events on the tracked branch. Checkout retrieves the relevant reference so subsequent steps work with the same content.

### Your commands, in a visible order

Shell CI runs project commands such as preparation and build. CI verification runs required checks; their logs distinguish preparation errors from failed checks.

### Communicate after validation

Discord follows the checks. The notification can reuse Git information to tie the result to the branch; configure failure handling according to your process.

## From trigger to outcome.

Git · Checkout · Shell CI · CI verification · Discord

## What this workflow brings.

Your team follows the sequence and reads CI step logs in nodulz. Commands stay specific to the project and the workflow exposes their execution order.

- Repository and Git reference as a common context.

- Explicit order between preparation, build and checks.

- Logs connected to the steps that actually ran the commands.

## Keep control of the process.

Define Git permissions, commands and the build environment. Deployment is outside this example; add it after your checks if your process requires it.

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)