Skip to content

refactor: update performance test workflows to use templates #1537

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ritwikranjan
Copy link
Contributor

Description

This pull request includes significant updates to the performance testing workflows by creating a reusable template and refactoring existing workflows to use this template. The changes aim to streamline the performance testing process and improve maintainability.

Key changes include:

Workflow Refactoring:

  • Renamed perf-basic and perf-advanced jobs to perf-test-basic and perf-test-advanced respectively, and replaced their steps with a reference to the new perf-template.yaml workflow. (.github/workflows/images.yaml)

New Workflow Template:

  • Added a new workflow template file perf-template.yaml to define common steps for performance testing, including setting up Go, logging into Azure CLI, and running performance tests. (.github/workflows/perf-template.yaml)

Scheduled Workflow:

  • Created a new scheduled workflow perf-schedule.yaml to run performance tests at specified intervals using the new template. (.github/workflows/perf-schedule.yaml)

Cleanup:

  • Removed the old perf.yaml workflow file, as its functionality is now covered by the new template and refactored workflows. (.github/workflows/perf.yaml)

Checklist

  • I have read the contributing documentation.
  • I signed and signed-off the commits (git commit -S -s ...). See this documentation on signing commits.
  • I have correctly attributed the author(s) of the code.
  • I have tested the changes locally.
  • I have followed the project's style guidelines.
  • I have updated the documentation, if necessary.
  • I have added tests, if applicable.

Please refer to the CONTRIBUTING.md file for more information on how to contribute to this project.

@ritwikranjan ritwikranjan requested a review from a team as a code owner April 15, 2025 09:43
@apontejaj
Copy link
Contributor

LGTM :-)

Copy link
Contributor

@apontejaj apontejaj left a comment

Choose a reason for hiding this comment

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

LGTM :-)

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