CI: track binary size changes over time #2634
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a step in the CI that shows the size
difference for each PR.
This requires keeping track of previous
sizes, so also add a step that pushes
sizes.log to a data repository when
merging PRs to develop.
There is a small window where two jobs
can push at the same time. Instead of adding
some complicated locking, just let one of
the jobs fail with the push, but make the job
green.
This requires a new repository to be created,
and an access token with write permissions
for that repository. The access token also needs
to be added as a secret to this CI with the name
DATA_PUSH_TOKEN
.Here's a screenshot of what it looks like when saving the output from "date":