generate/update CIPD module for chrome, chromedriver, xvfb, wct.go test harness binaries |
|||
Issue descriptionchromedriver can be distributed with this single binary (singe file in a zip file): https://sites.google.com/a/chromium.org/chromedriver/downloads I *think* we already have xvfb on linux builders but should double check. Distributing a chrome binary with CIPD is apparently not so straightforward. From vadimsh@ comments in go/chops-fe-ci : "(this is essentially what we do when testing Chrome), but will require some time to setup the automated packaging. We'd want real signed release binaries, perhaps from all 3 channels (canary, beta, stable)." The wct.go test harness binary can be built from infra/go/src/infra/tools/wct/wct.go All of the can probably go in the same CIPD package.
,
Mar 27 2018
whesse@: How are you packaging Chrome with CIPD today?
,
Mar 27 2018
I am taking a chrome runtime directory, which contains an executable like google_chrome or Google Chrome.exe, putting it in another directory, and uploading the contents of the parent directory as the CIPD package. I do this by hand, with the stable Chrome on Linux and Windows, haven't done MacOS yet. So the CIPD package contains a single directory, which contains the executable and all support files. I had to break some links to pepper flash or something on Linux, but it seems to work. I'm on vacation this week, until next Tuesday (April 3?) So things are going well with the system as is, but we would like a more automated system in the long run.
,
Mar 28 2018
,
Apr 12 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by vadimsh@chromium.org
, Mar 22 2018