This article explains how to write a .anguscicd.yaml that builds and tests on every push, after the repository already accepts pushes to AngusGit. After reading it, you can fill in the top-level fields, chain several jobs in order, choose when the pipeline runs, and reference a credential (a token or password saved on the platform) from a script without writing the token into a repository file.

Three facts come first. This file uses AngusGit’s own syntax. It is a different file from GitLab CI’s .gitlab-ci.yml and from a GitHub Actions workflow. Pipelines are available on Team and Enterprise. Community has no CI/CD menu. A runner is the program on a build machine that picks up a job and runs the commands. Connect one before the first run, or the job stays pending after the push. Sign in to AngusGit, open CI/CD → Runners in the sidebar, and click Add Runner . Change Control plane URL to an address the build machine can reach. Name the machine, for example build-linux-01 . Click Generate token .…