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

Fix the path from/to which the Go mod cache is populated in e2e test runs #139

Merged
merged 1 commit into from
Oct 4, 2023

Conversation

ulucinar
Copy link
Contributor

@ulucinar ulucinar commented Oct 4, 2023

Description of your changes

Currently, we are using .work/pkg as the path from/to which the Go mod cache is populated in the official providers' e2e tests. This path does not exist and thus the go mods need to be downloaded again during the builds for the e2e tests:
image

image

This PR proposes to fix that path using the output of the go.mod.cachedir make target. I've also verified that the OP repos upbound/provider-{aws,azure/ad,gcp,terraform} all contain that make target.

I have:

  • Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Tested against upbound/provider-aws:
image

Copy link
Member

@sergenyalcin sergenyalcin left a comment

Choose a reason for hiding this comment

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

Thanks @ulucinar LGTM!

@ulucinar ulucinar merged commit 0bfb3b2 into upbound:main Oct 4, 2023
5 checks passed
@ulucinar ulucinar deleted the fix-gomod-cache branch October 4, 2023 12:41
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.

2 participants