Skip to content

Enable Github Actions-based CI#36

Merged
estesp merged 1 commit intocontainerd:masterfrom
estesp:gh-actions
Sep 16, 2020
Merged

Enable Github Actions-based CI#36
estesp merged 1 commit intocontainerd:masterfrom
estesp:gh-actions

Conversation

@estesp
Copy link
Copy Markdown
Member

@estesp estesp commented Apr 9, 2020

Also add linting to CI and remove travis script entries that were no-ops
(there are no tests for other platforms so the extra go test
invocations with GOOS settings were not doing anything)

Signed-off-by: Phil Estes estesp@linux.vnet.ibm.com

@mikebrow
Copy link
Copy Markdown
Member

mikebrow commented Apr 9, 2020

1.12 vendor broken.. passes on 1.13 looks like it's been a while since this repo has had a PR...

@estesp
Copy link
Copy Markdown
Member Author

estesp commented Apr 9, 2020

yeah, as people have noted in other projects, go mod vendor output changes every release sadly.. and we aren't going to support 1.12. I'm just too lazy to edit Travis config when the next PR after this is totally removing the Travis config :)

@mikebrow
Copy link
Copy Markdown
Member

mikebrow commented Apr 9, 2020

yeah, as people have noted in other projects, go mod vendor output changes every release sadly.. and we aren't going to support 1.12. I'm just too lazy to edit Travis config when the next PR after this is totally removing the Travis config :)

other than building version.go12/ version.go13 based vendor trees... maybe we should skip that test on go n-1... oh hell NVM... :-)

@thaJeztah
Copy link
Copy Markdown
Member

@estesp can you try rebasing this one? travis now tests go 1.13/1.14

Also add linting to CI and remove travis script entries that were no-ops
(there are no tests for other platforms so the extra `go test`
invocations with GOOS settings were not doing anything)

Signed-off-by: Phil Estes <estesp@linux.vnet.ibm.com>
@estesp
Copy link
Copy Markdown
Member Author

estesp commented Sep 16, 2020

Updated

@thaJeztah
Copy link
Copy Markdown
Member

CI is green now; I don't see the action running though; does that need configuration changes in the repository first? Or won't it run on this repository until after it's merged?

@estesp
Copy link
Copy Markdown
Member Author

estesp commented Sep 16, 2020

They never run until the first merge and it exists in the "upstream" repo. That's why I always separate removing travis until we can verify and fix any nits with the actions first.

Copy link
Copy Markdown
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment on lines +47 to +52
go get -u github.com/golangci/golangci-lint/cmd/golangci-lint
(
cd "${GOPATH}/src/github.com/golangci/golangci-lint/cmd/golangci-lint"
git checkout v1.23.8
go build -v && go install
)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not for this PR, but we could make use of go modules for these;

  1. change to a directory outside of the project (to prevent the go.mod and/or vendor directory from being updated)
  2. run go get "github.com/golangci/golangci-lint/cmd/golangci-lint@${GOLANG_CI_VERSION}"

edit: although I see they don't recommend installing from source; https://golangci-lint.run/usage/install/#local-installation

@estesp estesp merged commit a032f0d into containerd:master Sep 16, 2020
@estesp estesp deleted the gh-actions branch September 16, 2020 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants