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

[SURE-9889] Create private runner for running CAPV E2E #612

Closed
alexander-demicev opened this issue Jul 23, 2024 · 4 comments
Closed

[SURE-9889] Create private runner for running CAPV E2E #612

alexander-demicev opened this issue Jul 23, 2024 · 4 comments
Assignees
Labels
area/ci area/testing Indicates an issue related to test JIRA must shout

Comments

@alexander-demicev
Copy link
Member

Setup a private runner to run E2E test for CAPV integration

@alexander-demicev alexander-demicev moved this to CAPI Backlog in CAPI / Turtles Jul 23, 2024
@yiannistri yiannistri self-assigned this Jul 30, 2024
@kkaempf kkaempf added area/testing Indicates an issue related to test area/ci labels Aug 5, 2024
@yiannistri
Copy link
Contributor

There is now an EIO ticket to move this forward https://github.com/rancherlabs/eio/issues/2579

@kkaempf
Copy link

kkaempf commented Nov 27, 2024

This should be unblocked and done now.

Anything missing @yiannistri ?

@yiannistri
Copy link
Contributor

yiannistri commented Nov 27, 2024

Now that we have an environment we need to:

  • Run the e2e tests manually to ensure they pass. As it's a new environment I anticipate that we need to do some configuration on the vSphere side to be able to create CAPI clusters.
  • Figure out how to run them as part of CI (*)

* After talking to Brandon, it became evident that we can't use VPN to access this environment for security reasons. So perhaps we need to create a self-hosted runner (a new VM basically) that is running on vSphere, that will be used to run e2e tests against Turtles using vSphere. We may need a research task/ticket for this.

Sorry, something went wrong.

@kkaempf kkaempf moved this from Blocked to CAPI Backlog in CAPI / Turtles Nov 27, 2024
@yiannistri yiannistri removed their assignment Jan 21, 2025
@kkaempf kkaempf added the JIRA must shout label Mar 4, 2025
@kkaempf kkaempf changed the title Create private runner for running CAPV E2E [SURE-9889] Create private runner for running CAPV E2E Mar 4, 2025
@kkaempf kkaempf self-assigned this Mar 4, 2025
@yiannistri yiannistri self-assigned this Mar 5, 2025
@yiannistri yiannistri moved this to In Progress (8 max) in CAPI / Turtles Mar 5, 2025
@kkaempf
Copy link

kkaempf commented Mar 18, 2025

we can run capv tests now

@kkaempf kkaempf closed this as completed Mar 18, 2025
@github-project-automation github-project-automation bot moved this from In Progress (8 max) to Done in CAPI / Turtles Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci area/testing Indicates an issue related to test JIRA must shout
Projects
Archived in project
Development

No branches or pull requests

3 participants