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 benchmark.yml and add end-to-end benchmark #1736

Merged
merged 6 commits into from
Apr 27, 2023

Conversation

edithwuly
Copy link
Contributor

@edithwuly edithwuly commented Apr 25, 2023

Summary

Create git action to keep runing benchmarks and graphing the results each time push on main branch. Benchmark for pack build --buildpack is added as well.

Output

The graphs for benchmark results will be shown in https://buildpack.github.io/pack/dev/bench/.

Before

Brank branch gh-pages is required for saving benchmark result data. index.html and data.js will be created automatically. alert-threshold and alert-comment-cc-users field should be decided.

After

Documentation

  • Should this change be documented?
    • Yes, see #___
    • No

Related

Resolves #___

@edithwuly edithwuly requested review from a team as code owners April 25, 2023 09:34
@github-actions github-actions bot added type/chore Issue that requests non-user facing changes. type/enhancement Issue that requests a new feature or improvement. labels Apr 25, 2023
@github-actions github-actions bot added this to the 0.30.0 milestone Apr 25, 2023
trustedImg = baseImg + "-trusted-"
builder = "cnbs/sample-builder:bionic"
mockAppPath = filepath.Join("..", "acceptance", "testdata", "mock_app")
paketoBuilder = "paketobuildpacks/builder:base"
Copy link
Member

Choose a reason for hiding this comment

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

Could we make this configurable with an env var or something? It would be nice to make it easy for contributors to test this out with builders that they care about.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, I have created setEnv() to set these values. If value is not set in the environment, default values will be assigned. setEnv() will be invoked at first of BenchmarkBuild(). Does this treatment make sense?

alert-threshold: '200%'
comment-on-alert: true
fail-on-alert: true
alert-comment-cc-users: '@edithwuly'
Copy link
Member

Choose a reason for hiding this comment

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

Eventually we'll probably want this to be '@buildpacks/platform-maintainers' but this will be helpful to reduce noise while we're iterating on the benchmark suite

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, so I just leave @edithwuly here temporarily.

edithwuly and others added 4 commits April 27, 2023 14:31
Signed-off-by: edithwuly <edithwuly@163.com>
Signed-off-by: edithwuly <edithwuly@163.com>
Signed-off-by: edithwuly <edithwuly@163.com>
Signed-off-by: edithwuly <edithwuly@163.com>
Signed-off-by: edithwuly <edithwuly@163.com>
@jkutner jkutner enabled auto-merge April 27, 2023 16:42
@jkutner jkutner merged commit 12bc0e2 into buildpacks:main Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/chore Issue that requests non-user facing changes. type/enhancement Issue that requests a new feature or improvement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants