#ci/cd + #tools

Woodpecker uses docker containers to execute pipeline steps.

.woodpecker/build.yaml

steps:

• name: build image: debian:stable-slim commands:
  • echo building
  • sleep 5

.woodpecker/deploy.yaml

steps:

• name: deploy image: debian:stable-slim commands:
  • echo deploying

depends_on:

• lint
• build
• test

.woodpecker/test.yaml

steps:

• name: test image: debian:stable-slim commands:
  • echo testing
  • sleep 5

depends_on:

• build

.woodpecker/lint.yaml

steps:

• name: lint image: debian:stable-slim commands:
  • echo linting
  • sleep 5

Before running any cacheable task, Nx computes its computation hash. As long as the computation hash is the same, the output of running the task is the same.

By default, the computation hash for something like nx test remixapp includes:

All the source files of remixapp and its dependencies Relevant global configuration Versions of external dependencies Runtime values provisioned by the user such as the version of Node CLI Command flags

Nx is a build system for monorepos. It helps you develop faster and keep CI fast as your codebase scales.

Runs tasks fast - Caches results so you never rebuild the same code twice. Understands your codebase - Builds project and task graphs showing how everything connects. Orchestrates intelligently - Runs tasks in the right order, parallelizing when possible. Enforces boundaries - Module boundary rules prevent unwanted dependencies between projects. Handles flakiness - Automatically re-runs flaky tasks and self-heals CI failures.

A simple tool to automate version bumps, changelogs, and releases using Conventional Commits.

📄 Uses conventional-changelog to parse commits, determine the next version, and generate a changelog.
🗂️ Supports monorepos and can release multiple packages in a single run.
🧩 Flexible and extensible with custom addons for different project types.
🚀 Has GitHub Action to automate releases in CI/CD pipelines.