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

Pipeline for running E2E tests #2

Open
karuppiah7890 opened this issue Jan 24, 2022 · 0 comments
Open

Pipeline for running E2E tests #2

karuppiah7890 opened this issue Jan 24, 2022 · 0 comments

Comments

@karuppiah7890
Copy link

karuppiah7890 commented Jan 24, 2022

I'm assuming that we want to add pipelines to run E2E tests, and add them to this repo, unlike TCE or TBS etc repos

A few questions off the top of my head

  • What pipeline do you folks wanna use? GitHub Actions, Travis CI, Circle CI etc. We could also consider Prow, which have been setting up for Tanzu OSS projects. https://github.com/vagator/test-infra
  • What environment do you folks plan to run these E2E tests on?
    • As in, we will need a Kubernetes cluster. We can either create a TCE cluster every time we run the test or have a long running cluster. But long running cluster could be a waste of resource if it's only used at times for this test
    • What platform for the cluster? vSphere, AWS, Azure, Docker? I was thinking a Docker cluster would be very simple, assuming we have a big machine (enough CPU and RAM) to run it smoothly. We also need a Docker image registry. Are you
    • And then we need kpack installed. We can install kpack using the TCE package on top of a TCE cluster
    • We also need a container image registry (OCI registry) for the images we pull, push and cleanup. I was wondering what the team used while testing this repo, as Docker Hub didn't work for me out of the box (due to E2E tests failing when using Docker Hub OCI registry as image registry #3) . Did you folks use GCR? Something else? For the test environment, we could use an OCI registry within the Kubernetes cluster too, using something like https://hub.docker.com/_/registry and deploy it , but that would mean we would need to sign the registry certificate using our own Certificate Authority (CA) and use those CA files in a few places to ensure it's a trusted CA by the clients (kpack controller, builder etc). Related issue - Document/support way of providing CA file needed to talk to image registry. buildpacks-community/kpack#207
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

No branches or pull requests

1 participant