RESOLVED FIXED Bug 179453
Add Windows powershell EWS script
https://bugs.webkit.org/show_bug.cgi?id=179453
Summary Add Windows powershell EWS script
Don Olmstead
Reported 2017-11-08 15:53:28 PST
Currently everything runs through shell scripts which requires cygwin. Add a Powershell equivalent for Windows
Attachments
Patch (3.80 KB, patch)
2017-11-08 16:07 PST, Don Olmstead
no flags
Don Olmstead
Comment 1 2017-11-08 16:07:58 PST
Brent Fulgham
Comment 2 2017-11-08 16:27:00 PST
Comment on attachment 326399 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=326399&action=review I think this looks fine as a new direction, especially since it doesn't affect or existing tooling at all. I had a couple of minor questions about paths that I'd like you to confirm before landing. > Tools/EWSTools/Start-Queue.ps1:47 > + git clean -f; # Remove any left-over layout test results, added files, etc. Does Powershell know where to find 'git'? Or do we need to make sure it's now part of the user's path? Can this script complain if 'git' is not in the path? > Tools/EWSTools/Start-Queue.ps1:88 > + python /Tools/BuildSlaveSupport/kill-old-processes Ditto my 'git' comments about 'perl' and 'python'. Is Powershell smart enough to find them if you installed ActiveState stuff, or do we need to document for the user that they should add relevant paths to the system environment?
Brent Fulgham
Comment 3 2017-11-08 16:27:40 PST
Comment on attachment 326399 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=326399&action=review > Tools/EWSTools/Start-Queue.ps1:86 > + perl ./Tools/Scripts/update-webkit --no-auxiliary-libs; Does Powershell always do the right thing with Unix-style paths? That's a very nice feature!
Don Olmstead
Comment 4 2017-11-08 16:29:05 PST
(In reply to Brent Fulgham from comment #2) > Comment on attachment 326399 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=326399&action=review > > I think this looks fine as a new direction, especially since it doesn't > affect or existing tooling at all. I had a couple of minor questions about > paths that I'd like you to confirm before landing. > > > Tools/EWSTools/Start-Queue.ps1:47 > > + git clean -f; # Remove any left-over layout test results, added files, etc. > > Does Powershell know where to find 'git'? Or do we need to make sure it's > now part of the user's path? Can this script complain if 'git' is not in the > path? > > > Tools/EWSTools/Start-Queue.ps1:88 > > + python /Tools/BuildSlaveSupport/kill-old-processes > > Ditto my 'git' comments about 'perl' and 'python'. Is Powershell smart > enough to find them if you installed ActiveState stuff, or do we need to > document for the user that they should add relevant paths to the system > environment? We're assuming that its on the path and accessible. (In reply to Brent Fulgham from comment #3) > Comment on attachment 326399 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=326399&action=review > > > Tools/EWSTools/Start-Queue.ps1:86 > > + perl ./Tools/Scripts/update-webkit --no-auxiliary-libs; > > Does Powershell always do the right thing with Unix-style paths? That's a > very nice feature! Yep it works fine.
WebKit Commit Bot
Comment 5 2017-11-08 16:54:02 PST
Comment on attachment 326399 [details] Patch Clearing flags on attachment: 326399 Committed r224610: <https://trac.webkit.org/changeset/224610>
WebKit Commit Bot
Comment 6 2017-11-08 16:54:03 PST
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 7 2017-11-15 09:39:45 PST
Note You need to log in before you can comment on or make changes to this bug.