Skip to content

Added Sha-1 to report output #36

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

Merged
merged 1 commit into from
Oct 8, 2020
Merged

Added Sha-1 to report output #36

merged 1 commit into from
Oct 8, 2020

Conversation

smithdc1
Copy link
Member

@smithdc1 smithdc1 commented Oct 8, 2020

Hi @adamchainz hope all is well.

I've been thinking about this and made some progress. What I have in mind is setting up a GitHub Action on a schedule to run the benchmark suite and store the outputs in a datasette.

I'd like to add the commit hash to the output from djangobench and this pull request proposes this change. The commit hash is needed so we can easily identify which commit caused a performance regression.

I've already managed to automate a process that creates a datasette of the commit history of Django and is published at heroku, here is the source repo. I wanted to do this, so we can provide a description of the commit. It also exposes other data that may be of interest. Simon's existing tools made this fairly straight forward.

@adamchainz
Copy link
Member

Nice one! LGTM.

@adamchainz adamchainz merged commit 6305731 into django:master Oct 8, 2020
@smithdc1 smithdc1 deleted the sha1 branch October 8, 2020 18:33
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