EWS Updates

by Dean Johnson

• Many requests for improvements
• Since last year…
  • Added EWS for Security Patches
• What’s Next?
  • Run API tests
  • Abandon on obsolete patch
  • Retry patches
  • Errors in EWS bubbles
  • Run webkitperl tests
  • Process faster
  • Historical build logs
  • More…
• Architectural Limitations
  • 1 test = 1 build
  • 1 OS per queue config
  • Very basic UI
  • Missing usual CI features
  • Stability issues
• Existing System
  • Requires dedicated hardware per queue
• New System
  • Separate building and testing
    • Build (Mac-EWS-32bit, Mac-EWS-64bit, iOS-EWS…)
    • Datastore
    • Tests (Mac WK1, Mac WK2, iOS sim WK1…)
• Benefits
  • Production-level CI system
  • Lots of shared code with build.webkit.org
  • Framework built for EWS-type tasks
  • Easy to add new configurations
  • Automattically get: real-time and historical logs, retries, easy bot management
• Tradeoffs
  • Throwing out a lot of code and hard work
  • Time could be spent on improving the existing system
  • Buildbot UI can be less than ideal
• Tentative Plans
  • Basic implementation for EWS server (in progress) + Buildbot (done)
  • Complete implémentation for EWS server + buildbot
  • Run in parallel with existing EWS, serving some new bubbles
• Features @ Launch
  • Feature-parity including Security EWS
  • Easy to add new configurations
  • API tests, webkitperl tests, arm64 JSC tests
  • Build + test logs in real-time