Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: dcf824dfad72314a092e264e010d01c95b1d6876
https://github.com/WebKit/WebKit/commit/dcf824dfad72314a092e264e010d01c95b1d6876
Author: Aakash Jain <[email protected]>
Date: 2026-08-17 (Mon, 17 Aug 2026)
Changed paths:
M Tools/CISupport/ews-build/config.json
M Tools/CISupport/ews-build/events.py
M Tools/CISupport/ews-build/factories.py
M Tools/CISupport/ews-build/factories_unittest.py
M Tools/CISupport/ews-build/loadConfig.py
M Tools/CISupport/ews-build/loadConfig_unittest.py
M Tools/CISupport/ews-build/steps.py
M Tools/CISupport/ews-build/steps_unittest.py
Log Message:
-----------
[EWS] Remove Bugzilla patch workflow support from ews-build.webkit.org
https://bugs.webkit.org/show_bug.cgi?id=321805
<rdar://problem/184941032>
Reviewed by Ryan Haddad.
Patches were submitted to EWS by setting r? on a Bugzilla attachment, and
landed by the
Commit-Queue with cq+. Both are removed here, along with the steps and Bugzilla
API calls
which only ran for patches, so ews-build now only processes pull requests.
Every builder
which the patch scheduler fed is also fed by the pull request scheduler, and the
Commit-Queue's workers are shared with the merge queues, so no queue loses its
trigger or
its workers.
Bugzilla is still used for issue tracking: EWS keeps commenting on and closing
the bug of
a landed pull request.
* Tools/CISupport/ews-build/config.json:
* Tools/CISupport/ews-build/events.py:
* Tools/CISupport/ews-build/factories.py:
* Tools/CISupport/ews-build/factories_unittest.py:
* Tools/CISupport/ews-build/loadConfig.py:
* Tools/CISupport/ews-build/loadConfig_unittest.py:
* Tools/CISupport/ews-build/steps.py:
* Tools/CISupport/ews-build/steps_unittest.py:
Canonical link: https://commits.webkit.org/319303@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
