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

Validate E2E workflow in CI #340

Closed
2 tasks
john-odonnell opened this issue Jun 24, 2021 · 1 comment · Fixed by #348
Closed
2 tasks

Validate E2E workflow in CI #340

john-odonnell opened this issue Jun 24, 2021 · 1 comment · Fixed by #348

Comments

@john-odonnell
Copy link
Contributor

john-odonnell commented Jun 24, 2021

Is your feature request related to a problem? Please describe.

Before adding E2E tests with more environments and authenticators, it would help to
set up either Jenkins or a GitHub action to validate the E2E workflows. Whichever CI
is used could trigger on each PR and daily to ensure additions work in an ambiguous
environment.

Describe the solution you would like

CI flow to validate the current E2E workflow path, using either

  • GitHub action
  • Jenkinsfile

The CI flow should also be easily extensible to add other elements of the test matrix described in #310.

Describe alternatives you have considered

Additional context

@diverdane
Copy link
Contributor

+1 for implementing this using GitHub actions. For reference, this GitHub action uses Helm V3 and KinD:
https://github.com/cyberark/conjur-authn-k8s-client/blob/master/.github/workflows/ci.yaml
so it would be a good starting point!

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

Successfully merging a pull request may close this issue.

4 participants