| Summary: | [ews] Add build step to generate commit message | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Aakash Jain <aakash_jain> | ||||
| Component: | Tools / Tests | Assignee: | Aakash Jain <aakash_jain> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | aakash_jain, ap, jbedard | ||||
| Priority: | P2 | ||||||
| Version: | Other | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=208514 | ||||||
| Attachments: |
|
||||||
|
Description
Aakash Jain
2020-03-03 13:48:20 PST
Created attachment 392326 [details]
Patch
Comment on attachment 392326 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=392326&action=review > Tools/BuildSlaveSupport/ews-build/steps.py:2482 > + self.command = 'perl Tools/Scripts/commit-log-editor --print-log {} > {}'.format(modified_changelogs, commit_message_filename) It feels wrong to place the commit message in a temp file only to be used in the next step. Was this what the previous code did? How do we know that tmp won't be cleared out between this step and the next? Any reason we can't stick this output in property to be used by the next step? Included this change in https://bugs.webkit.org/show_bug.cgi?id=208539 |