Skip to content

Add install for ginkgo which is used for e2e tests#4714

Merged
jetstack-bot merged 1 commit intocert-manager:masterfrom
SgtCoDFish:install-ginkgo
Jan 6, 2022
Merged

Add install for ginkgo which is used for e2e tests#4714
jetstack-bot merged 1 commit intocert-manager:masterfrom
SgtCoDFish:install-ginkgo

Conversation

@SgtCoDFish
Copy link
Copy Markdown
Member

This is currently done by a bazel rule, but we need a local install of gingko that's done via Make.

This is part of the migration to make.

/kind feature

NONE

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
@jetstack-bot jetstack-bot added release-note-none Denotes a PR that doesn't merit a release note. kind/feature Categorizes issue or PR as related to a new feature. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 6, 2022
@SgtCoDFish SgtCoDFish mentioned this pull request Jan 6, 2022
30 tasks
Copy link
Copy Markdown
Member

@jakexks jakexks left a comment

Choose a reason for hiding this comment

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

/lgtm

As an aside, how are we keeping bazel and Make tool versions in sync? by hand at the moment?

@jetstack-bot jetstack-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 6, 2022
@jetstack-bot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jakexks, SgtCoDFish

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@SgtCoDFish
Copy link
Copy Markdown
Member Author

As an aside, how are we keeping bazel and Make tool versions in sync? by hand at the moment?

Yeah pretty much by hand; I'm keeping an eye on it. I'm kinda hoping that the make stuff won't take too long and there won't be much that will need to be updated in both make + bazel.

@jetstack-bot jetstack-bot merged commit 7021be7 into cert-manager:master Jan 6, 2022
@jetstack-bot jetstack-bot added this to the v1.7 milestone Jan 6, 2022
@SgtCoDFish SgtCoDFish deleted the install-ginkgo branch January 6, 2022 14:51
@munnerz
Copy link
Copy Markdown
Member

munnerz commented Jan 6, 2022

As an aside, how are we keeping bazel and Make tool versions in sync? by hand at the moment?

Yeah pretty much by hand; I'm keeping an eye on it. I'm kinda hoping that the make stuff won't take too long and there won't be much that will need to be updated in both make + bazel.

Hm, with ginkgo specifically, installing using a version number encoded into the Makefile is actually a net addition in the number of places we need to maintain version numbers. Ginkgo is currently made available to Bazel via the go.mod file, as both the Go source files as well as binary executor depend on ginkgo (see https://github.com/jetstack/cert-manager/blob/7021be7a1fa4f69e255d1e7a8b2fb1c41a1bc84a/go.mod#L25).

With this change, we now need to maintain both the go.mod file as well as this Makefile (and will continue to need to do so with or without Bazel).

Is there instead a way we can install the ginkgo binary at the version defined in the go.mod file?

@SgtCoDFish
Copy link
Copy Markdown
Member Author

Is there instead a way we can install the ginkgo binary at the version defined in the go.mod file?

Fair point 👍 I've raised #4717 to do exactly this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants