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

create post GH workflow #1244

Open
25 tasks
Tracked by #1162
strekm opened this issue Jan 15, 2025 · 0 comments
Open
25 tasks
Tracked by #1162

create post GH workflow #1244

strekm opened this issue Jan 15, 2025 · 0 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@strekm
Copy link
Contributor

strekm commented Jan 15, 2025

Description

implement GH workflow that should be triggered by merge to main branch. Image should be built using neighbours provided image-builder. Run lint and unit tests, integration tests,aws specific tests, gcp specific tests, upgrade test. In the last step of the workflow which in case of a failure is a Slack notification, include information about the owner of the commit.

ToDos [Developer]

  • copy provision/deprovision gardener script from API Gateway
  • ACs:
    • lint and unit tests are run
    • image built using image-builder
    • integration tests are run on k3d, AWS and GCP
    • upgrade tests are run on k3d and AWS
    • AWS specific tests are run
    • GCP specific test are run
    • on failed workflow sent notification to slack channel mentioning commit author
    • workflow names and file names adjusted to naming convention described in test strategy
    • changes updated in ci-cd.md
  • sync the same functionalities with API Gateway pipeline
  • ensure that the logs and resource dumps are stored in an artifact when pipeline is completed
  • consider the current Gardener quota - whether to extend it even more
  • test it before merge ;)

PRs

ACs [PO]

  • lint and unit tests are run
  • image built using image-builder
  • integration tests are run on k3d, AWS and GCP
  • upgrade tests are run on k3d and AWS
  • AWS specific tests are run
  • GCP specific test are run
  • on failed workflow sent notification to slack channel mentioning commit author
  • workflow names and file names adjusted to naming convention described in test strategy
  • changes updated in ci-cd.md

DoD [Developer & Reviewer]

  • Provide documentation.

Attachments

@strekm strekm added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 15, 2025
@strekm strekm mentioned this issue Jan 15, 2025
10 tasks
@kolodziejczak kolodziejczak self-assigned this Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants