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

CICD support for previous versions of nodeos for Performance Harness #1156

Closed
oschwaldp-oci opened this issue May 11, 2023 · 1 comment · Fixed by #1356
Closed

CICD support for previous versions of nodeos for Performance Harness #1156

oschwaldp-oci opened this issue May 11, 2023 · 1 comment · Fixed by #1356
Assignees
Labels
CICD Anything dealing with the CI workflow behavior 👍 lgtm OCI Work exclusive to OCI team

Comments

@oschwaldp-oci
Copy link
Member

Looking for options to test against previous versions of nodeos in CI/CD.

@heifner heifner added the CICD Anything dealing with the CI workflow behavior label May 11, 2023
@BenjaminGormanPMP BenjaminGormanPMP added the more-info waiting for submitter to reply with more information label May 11, 2023
@heifner heifner removed the triage label May 11, 2023
@oschwaldp-oci
Copy link
Member Author

As the Performance Harness is meant to benchmark and track performance enhancements and safeguard against degradations over the product development lifecycle, it would be good to have a means to run the Performance Harness in an automated and periodic manner.

To enable the historical benchmarking and safeguard against breaking compatibility with past versions of nodeos that still maintain performance measurements for historical comparison, it would be good to have access to those previous versions of nodeos in CICD to run smoke tests against for maintaining compatibility as the Performance Harness continues to develop. Currently, Performance Harness development has attempted to maintain the ability to benchmark performance on releases starting at 2.0, 2.1, 3.1, 3.2 up to current. If the ability to regenerate historical benchmarks with newly developed metrics is not desired then this could become a non-issue. If it is desired, some additional input into how far back to go would also be valuable.

@bhazzard bhazzard added OCI Work exclusive to OCI team 👍 lgtm and removed more-info waiting for submitter to reply with more information labels May 18, 2023
@oschwaldp-oci oschwaldp-oci added OCI Work exclusive to OCI team and removed OCI Work exclusive to OCI team labels Jun 27, 2023
oschwaldp-oci added a commit that referenced this issue Jun 30, 2023
…flow

Create stub workflow ph_backward_compatibility.yaml
oschwaldp-oci added a commit that referenced this issue Jul 14, 2023
[PH] Create workflow to test backward compatibility of performance harness
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CICD Anything dealing with the CI workflow behavior 👍 lgtm OCI Work exclusive to OCI team
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants