-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Make release notes generation concurrent #8817
🌱 Make release notes generation concurrent #8817
Conversation
/hold |
/area release |
a51a1e4
to
1892cfd
Compare
rebased after #8780 merged |
/lgtm |
LGTM label has been added. Git tree hash: b4d2f25aa8e74c88f890791ead315886544ee4be
|
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an amazing update @g-gaston ! Thanks 🚀
Just a minor nit, can we add any more comments around results
, jobs
and go routines
for helping anyone reading this the first time?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working at this!
/lgtm |
LGTM label has been added. Git tree hash: a03a782499a6ce4cc394c9d53a9397dabe45dd64
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking this on - nice speedup 🙂
/lgmt
/approve
/check-cla |
@g-gaston You might want to force-push on top of this to see if that kicks easyCLA into action. |
24cb6b7
to
fd00dfd
Compare
Now that we retrieve the area labels from the PRs, the release notes generation can take up to 2 minutes for big releases like 1.5. Although in general this is not a problem since it should be a one time process, it does slow down the comms release team when iterating in the notes, adding missing labels, etc. It also makes development of the script painful when testing it manually. The default is 10 concurrent routines, but this can be changed with command flag. The default value of 10 doesn't seem to run into rate limiting problems. I had to bump it to a 100 and run the command multiple times in a row to be able to get rate limited.
fd00dfd
to
c472b28
Compare
@killianmuldoon squashed and rebased :) |
/lgtm |
LGTM label has been added. Git tree hash: 3b885f0fa93934f926aa7a011e29f4770788c666
|
Thanks /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: killianmuldoon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Now that we retrieve the area labels from the PRs, the release notes generation can take up to 2 minutes for big releases like 1.5. Although in general this is not a problem since it should be a one time process, it does slow down the comms release team when iterating in the notes, adding missing labels, etc. It also makes development of the script painful when testing it manually.
The default is 10 concurrent routines, but this can be changed with command flag.
The default value of 10 doesn't seem to run into rate limiting problems. I had to bump it to a 100 and run the command multiple times in a row to be able to get rate limited.