Skip to content
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

build: set GOPATH in Makefile #2398

Merged
merged 1 commit into from
Nov 4, 2022
Merged

Conversation

zachaller
Copy link
Collaborator

We currently assume that GOPATH is set within the developers environment go has some defaults that get used when no GOPATH is defined. If we use go env GOPATH to set the env var for the Makefile we will then also fall back to golang defaults which help contributior experiance.

Signed-off-by: zachaller [email protected]

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
  • The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
  • I've signed my commits with DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My builds are green. Try syncing with master if they are not.
  • My organization is added to USERS.md.

We currently assume that GOPATH is set within the developers environment
go has some defaults that get used when no GOPATH is defined. If we use
`go env GOPATH` to set the env var for the Makefile we will then also fall
back to golang defaults which help contributior experiance.

Signed-off-by: zachaller <[email protected]>
@@ -23,6 +23,7 @@ E2E_INSTANCE_ID ?= argo-rollouts-e2e
E2E_TEST_OPTIONS ?=
E2E_PARALLEL ?= 1
E2E_WAIT_TIMEOUT ?= 120
GOPATH ?= $(shell go env GOPATH)
Copy link
Member

Choose a reason for hiding this comment

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

yes!

@sonarcloud
Copy link

sonarcloud bot commented Nov 4, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
1.8% 1.8% Duplication

@zachaller zachaller changed the title fix: set GOPATH in Makefile build: set GOPATH in Makefile Nov 4, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2022

Go Published Test Results

1 778 tests   1 778 ✔️  2m 29s ⏱️
   101 suites         0 💤
       1 files           0

Results for commit 5e8e2fa.

@codecov
Copy link

codecov bot commented Nov 4, 2022

Codecov Report

Base: 82.76% // Head: 82.76% // No change to project coverage 👍

Coverage data is based on head (5e8e2fa) compared to base (076ea43).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2398   +/-   ##
=======================================
  Coverage   82.76%   82.76%           
=======================================
  Files         121      121           
  Lines       18536    18536           
=======================================
  Hits        15341    15341           
  Misses       2410     2410           
  Partials      785      785           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 4, 2022

E2E Tests Published Test Results

    2 files      2 suites   1h 29m 41s ⏱️
  89 tests   86 ✔️ 3 💤 0
178 runs  172 ✔️ 6 💤 0

Results for commit 5e8e2fa.

@leoluz leoluz merged commit 5db47e7 into argoproj:master Nov 4, 2022
jandersen-plaid pushed a commit to jandersen-plaid/argo-rollouts that referenced this pull request Nov 8, 2022
We currently assume that GOPATH is set within the developers environment
go has some defaults that get used when no GOPATH is defined. If we use
`go env GOPATH` to set the env var for the Makefile we will then also fall
back to golang defaults which help contributior experiance.

Signed-off-by: zachaller <[email protected]>

Signed-off-by: zachaller <[email protected]>
jandersen-plaid pushed a commit to jandersen-plaid/argo-rollouts that referenced this pull request Nov 26, 2022
We currently assume that GOPATH is set within the developers environment
go has some defaults that get used when no GOPATH is defined. If we use
`go env GOPATH` to set the env var for the Makefile we will then also fall
back to golang defaults which help contributior experiance.

Signed-off-by: zachaller <[email protected]>

Signed-off-by: zachaller <[email protected]>
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.

3 participants