Skip to content

Add a build tag for the e2e test only#4755

Merged
jetstack-bot merged 1 commit intocert-manager:masterfrom
SgtCoDFish:e2e_build_tag
Jan 17, 2022
Merged

Add a build tag for the e2e test only#4755
jetstack-bot merged 1 commit intocert-manager:masterfrom
SgtCoDFish:e2e_build_tag

Conversation

@SgtCoDFish
Copy link
Copy Markdown
Member

This was initially part of #4565 which was closed in favour of moving integration tests, but the consensus was that the e2e test is a special case.

The e2e test requires so much more ahead-of-time setup that our bazel build flow special cases it by marking it manual. This is a go test equivalent to that, which enables the e2e test to remain under the test/ directory while still allowing go test ./test/... to work generally for all other tests.

We'll add make targets for the e2e tests down the road. For now, we add the build tag and define it in bazel so this commit should be a no-op in effect.

/kind cleanup

NONE

@jetstack-bot jetstack-bot added release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. labels Jan 17, 2022
This was initially part of cert-manager#4565 which was closed in favour of moving
integration tests, but the consensus was that the e2e test is a special
case.

The e2e test requires so much more ahead-of-time setup that our bazel
build flow special cases it by marking it manual. This is a `go test`
equivalent to that, which enables the e2e test to remain under the test/
directory while still allowing `go test ./test/...` to work generally
for all other tests.

We'll add make targets for the e2e tests down the road. For now, we add
the build tag and define it in bazel so this commit should be a no-op
in effect.

Signed-off-by: Ashley Davis <ashley.davis@jetstack.io>
@jetstack-bot jetstack-bot added area/testing Issues relating to testing approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 17, 2022
@SgtCoDFish
Copy link
Copy Markdown
Member Author

/test all

@SgtCoDFish
Copy link
Copy Markdown
Member Author

/test

@jetstack-bot
Copy link
Copy Markdown
Contributor

@SgtCoDFish: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

  • /test pull-cert-manager-bazel
  • /test pull-cert-manager-chart
  • /test pull-cert-manager-deps
  • /test pull-cert-manager-e2e-v1-23
  • /test pull-cert-manager-upgrade

The following commands are available to trigger optional jobs:

  • /test pull-cert-manager-bazel-nocache
  • /test pull-cert-manager-bazel-gocache
  • /test pull-cert-manager-bazel-experimental
  • /test pull-cert-manager-e2e-v1-18
  • /test pull-cert-manager-e2e-v1-19
  • /test pull-cert-manager-e2e-v1-20
  • /test pull-cert-manager-e2e-v1-21
  • /test pull-cert-manager-e2e-v1-22
  • /test pull-cert-manager-issuers-venafi-tpp
  • /test pull-cert-manager-e2e-issuers-venafi-cloud

Use /test all to run the following jobs that were automatically triggered:

  • pull-cert-manager-bazel
  • pull-cert-manager-chart
  • pull-cert-manager-deps
  • pull-cert-manager-e2e-v1-23
  • pull-cert-manager-upgrade
Details

In response to this:

/test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@SgtCoDFish
Copy link
Copy Markdown
Member Author

/test pull-cert-manager-e2e-v1-18
/test pull-cert-manager-e2e-v1-19
/test pull-cert-manager-e2e-v1-20
/test pull-cert-manager-e2e-v1-21
/test pull-cert-manager-e2e-v1-22

@SgtCoDFish SgtCoDFish mentioned this pull request Jan 17, 2022
30 tasks
@jetstack-bot
Copy link
Copy Markdown
Contributor

@SgtCoDFish: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Rerun command
pull-cert-manager-e2e-v1-18 f2d8a33 link /test pull-cert-manager-e2e-v1-18

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SgtCoDFish
Copy link
Copy Markdown
Member Author

/test pull-cert-manager-e2e-v1-18

@irbekrm
Copy link
Copy Markdown
Contributor

irbekrm commented Jan 17, 2022

I agree about e2e tests being a special case after the discussion we had 👍🏼

I've not tried running this branch locally, but looking at which tests where skipped for this PR and which tests where skipped for another PR, the numbers are the same, so no reason to doubt if the tag works.

(This did make me randomly wonder whether we should name the tests somehow better as by looking at the skipped tests, it is not possible to tell why they are skipped, but that is completely unrelated to this PR)

/lgtm
/approve

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: irbekrm, 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

@jetstack-bot jetstack-bot merged commit 4cbfd2e into cert-manager:master Jan 17, 2022
@jetstack-bot jetstack-bot added this to the v1.7 milestone Jan 17, 2022
@SgtCoDFish SgtCoDFish deleted the e2e_build_tag branch January 17, 2022 17:18
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. area/testing Issues relating to testing dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants