Real-World Example
See it in action
Here's how dunebot a real ContainifyCI project defines its entire build and CI pipeline.
engine-ci building itself
1. Define your build
.containifyci/containifyci.go
package main
import (
"os"
"github.com/containifyci/engine-ci/client/pkg/build"
"github.com/containifyci/engine-ci/protos2"
)
func main() {
os.Chdir("../")
opts := build.NewGoServiceBuild("dunebot")
opts.Application = "dunebot"
opts.File = "main.go"
opts.Properties = map[string]*build.ListValue{
"goreleaser": build.NewList("true"),
}
build.Serve(opts)
}
2. Wire it into GitHub Actions
.github/workflows/pull-request.yaml
name: Pull Request
on:
pull_request:
branches: [main]
jobs:
build:
name: Build
uses: containifyci/.github/.github/workflows/pull-request.yml@v1
secrets: inherit
3. Add a release workflow
.github/workflows/release.yaml
name: Release
on:
push:
branches: [main]
paths-ignore: ['.github/**']
jobs:
build-and-release:
uses: containifyci/.github/.github/workflows/release.yml@v1
secrets: inheritOne Go file for your build logic. Two tiny YAML files to
connect it to GitHub Actions. The same engine-ci run command works locally and in
CI. There are no divergence and no surprises.
See the full working example at containifyci/dunebot.