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

fix(ci): trigger e2e on keycloakify changes; don't wait for each image instead use timeout #1175

Merged
merged 2 commits into from
Feb 28, 2024

Conversation

corneliusroemer
Copy link
Contributor

@corneliusroemer corneliusroemer commented Feb 28, 2024

Summary

  • fix(ci): add keycloak to paths that trigger E2E
  • No need to wait for particular images, kubernetes will retry pulling images and backoff if not found. Given we build many docker images, we would otherwise wait for each - not just the 2 here. Instead, use timeout to fail if the images never make it.

…images and backoff if not found

Given we build many docker images, we would otherwise wait for each - not just the 2 here.

Instead, use timeout to fail if the images never make it.
@corneliusroemer corneliusroemer changed the base branch from main to keycloakify February 28, 2024 20:46
@corneliusroemer corneliusroemer changed the title fix: trigger e2e on keycloakify changes fix(ci): trigger e2e on keycloakify changes; don't wait for each image instead use timeout Feb 28, 2024
@corneliusroemer corneliusroemer merged commit 2254a5b into keycloakify Feb 28, 2024
10 checks passed
@corneliusroemer corneliusroemer deleted the e2e-on-keycloakify branch February 28, 2024 20:53
- name: Deploy with helm
uses: WyriHaximus/github-action-helm3@v4
with:
exec: ./deploy.py --verbose helm --branch ${{ github.ref_name }} --sha ${{ github.sha }} --dockerconfigjson ${{ secrets.GHCR_DOCKER_CONFIG }}

- name: Wait for the pods to be ready
timeout-minutes: 10
Copy link
Member

Choose a reason for hiding this comment

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

The script already has a timeout – worth keeping to one or the other

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh I didn't know!

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

Successfully merging this pull request may close these issues.

2 participants