Skip to content
This repository was archived by the owner on Aug 30, 2024. It is now read-only.

Use release binary in integration tests #98

Merged
merged 1 commit into from
Aug 22, 2020
Merged

Conversation

cmoog
Copy link
Contributor

@cmoog cmoog commented Aug 21, 2020

@cmoog cmoog requested a review from coadler August 21, 2020 21:12
@cmoog cmoog force-pushed the fix-coder-cli-test-binary branch from ff685cb to 318e09e Compare August 21, 2020 21:13
cmd := exec.Command(
"sh", "-c",
fmt.Sprintf("cd ../../ && go build -o %s ./cmd/coder", path),
fmt.Sprintf(
"cd ../../ && mkdir -p %s && ./ci/steps/build.sh && cp ./ci/bin/%s %s/ && tar -xzf %s -C %s",
Copy link
Contributor

Choose a reason for hiding this comment

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

What if you just pulled the go build command into its own function and source it so you can call it? Would remove the step of tar -> untar

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd prefer it to use as close to the actual release artifact as possible. Maybe that's not particularly rational in this case but the aim of this test is to prevent the previous regression from going undetected.

Copy link
Contributor

Choose a reason for hiding this comment

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

Makes sense

@cmoog cmoog merged commit ddaeba7 into master Aug 22, 2020
@cmoog cmoog deleted the fix-coder-cli-test-binary branch August 22, 2020 18:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants