Open tboerger opened 5 years ago
I think we could simplify to this:
---
kind: pipeline
name: testing
platform:
os: linux
arch: amd64
steps:
- name: test
image: golang:1.11
commands:
- go vet ./...
- go test -cover ./...
I know the plugins follow different conventions, but the plugins tend to have very complex pipelines (multi-os, multi-arch, docker builds, etc). For libraries I think we can keep things simple.
Not exactly like you defined it, but I have simplified the pipeline now.
All committers have signed the CLA.