Example Yaml configuration for a project written in the Go programming language:
workspace:
base: /go
path: src/github.com/octocat/hello-world
pipeline:
build:
image: golang:latest
commands:
- go get ./...
- go test
- go build
Using the official Go image:
pipeline:
build:
+ image: golang:latest
commands:
- go get
- go test
Using the build matrix to test multiple Go versions:
pipeline:
build:
- image: golang:latest
+ image: golang:${GO_VERSION}
commands:
- go get
- go test
+matrix:
+ GO_VERSION:
+ - latest
+ - "1.7"
+ - "1.6"
What is the workspace?
The workspace defines the shared volume and working directory for your build. We recommend projects customize the workspace to use the desired GOPATH.
+workspace:
+ base: /go
+ path: src/github.com/octocat/hello-world
pipeline:
build:
image: golang:latest
commands:
- go get
- go test
What is the workspace base?
The base defines a shared volume that is available to all pipeline steps. This ensures your source code, dependencies and compiled binaries are persisted and shared between steps.
workspace:
+ base: /go
path: src/github.com/octocat/hello-world
pipeline:
deps:
image: golang:latest
commands:
- go get
- go test
build:
image: node:latest
commands:
- go build
What is the workspace path
The path defines the working directory of your build. This is where your code is cloned and will be the default working directory of every step in your build process. The path must be relative and is combined with your base path.
workspace:
base: /go
+ path: src/github.com/octocat/hello-world
git clone https://github.com/octocat/hello-world \
/go/src/github.com/octocat/hello-world
Questions?
We are always happy to help with questions you might have. Search our documentation or check out answers to common questions. You can also post questions or comments to our community forum.
Is there a mistake on this page? Please let us know or edit this page.