-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix CircleCI build and Golang linting #186
Changes from all commits
ba40823
bad7ad5
9597105
65d03b7
8646eb1
4555af2
80ea845
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,7 @@ jobs: | |
build: | ||
working_directory: /go/pkg/mod/github.com/admiral | ||
docker: | ||
- image: circleci/golang:1.11 | ||
- image: circleci/golang:1.16 | ||
steps: | ||
- checkout | ||
- run: | ||
|
@@ -54,6 +54,7 @@ jobs: | |
MINIKUBE_WANTREPORTERRORPROMPT: false | ||
MINIKUBE_HOME: /home/circleci | ||
CHANGE_MINIKUBE_NONE_USER: true | ||
resource_class: large | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Curious to know why we need a large build container (assuming it is a build container) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is for the integration tests. The container was increased to match the size that CircleCI has with the limits I increased minikube to. https://circleci.com/docs/2.0/configuration-reference/#resourceclass |
||
steps: | ||
- attach_workspace: | ||
at: . | ||
|
@@ -104,7 +105,7 @@ jobs: | |
./run.sh "1.16.8" "1.7.6" "../out" | ||
publish-github-release: | ||
docker: | ||
- image: circleci/golang:1.11 | ||
- image: circleci/golang:1.16 | ||
working_directory: /go/pkg/mod/github.com/admiral | ||
steps: | ||
- attach_workspace: | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,7 +5,7 @@ | |
k8s_version=$1 | ||
|
||
if [[ $IS_LOCAL == "false" ]]; then | ||
sudo -E minikube start --vm-driver=none --cpus 4 --memory 4096 --kubernetes-version=$k8s_version &> $HOME/minikube.log 2>&1 < /dev/null | ||
sudo -E minikube start --vm-driver=none --cpus 6 --memory 6144 --kubernetes-version=$k8s_version &> $HOME/minikube.log 2>&1 < /dev/null | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is the increment in resources due to some new dependency? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Increased demands for the tests with added GRPC clients. I noticed the tests were flaky and seemed to be failing to timeout. Experience with running minikube has shown that the lack of responsiveness occurs when it becomes resource strapped so I increased it to account for this. I also had to increase the integration test vm resources to account for this change as well. |
||
else | ||
minikube start --memory=4096 --cpus=4 --kubernetes-version=$k8s_version --vm-driver "virtualbox" | ||
#label node for locality load balancing | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use 1.17 ?