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

[CI] Optimize the cost of Github actions by triggering necessary tests #253

Closed
Jeffwan opened this issue Sep 27, 2024 · 2 comments · Fixed by #411
Closed

[CI] Optimize the cost of Github actions by triggering necessary tests #253

Jeffwan opened this issue Sep 27, 2024 · 2 comments · Fixed by #411
Assignees
Labels
area/cicd good first issue Good for newcomers help wanted Extra attention is needed
Milestone

Comments

@Jeffwan
Copy link
Collaborator

Jeffwan commented Sep 27, 2024

🚀 Feature Description and Motivation

image

Right now, we kick off following pipelines for every single request.

  • doc
  • python
  • golang

image

This is cost inefficient and we spend a little bit more money on the test runs. It's better to trigger corresponding tests when necessary. For example, for the doc change, we do not need to test any golang or python pipelines.

Use Case

No response

Proposed Solution

No response

@varungup90
Copy link
Collaborator

For push the image, should be do nightly such as 12AM daily? If needed for a particular release tag, we can manually kickoff the workflow.

@varungup90
Copy link
Collaborator

Second, we do not need docker-build-images workflow because it runs as a part of installation-test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cicd good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants