Bug #10130

Cache / mirror PhantomJS

Added by Tom Morris over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
09/27/2016
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

I've seen a couple of build failures in the last few days related to failure to download PhantomJS, which appears to be hosted on a rate-limited site:
https://github.com/ariya/phantomjs/issues/13953

Given all the other problems that we have with the build, it seems like it would be worth caching a local copy of PhantomJS to make that one less thing to worry about.

Associated revisions

Revision eec17149 (diff)
Added by Ward Vandewege over 4 years ago

Use our cached copy of phantomjs-1.9.7 instead of pulling it from https
upstream with flakey connectivity.

closes #10130

History

#1 Updated by Tom Morris over 4 years ago

  • Target version set to Arvados Future Sprints

#2 Updated by Ward Vandewege over 4 years ago

  • Status changed from New to Resolved
  • Assigned To set to Ward Vandewege
  • Target version changed from Arvados Future Sprints to 2016-09-28 sprint

We have a cached copy at

http://cache.arvados.org/phantomjs-1.9.7-linux-x86_64.tar.bz2

And I've updated the arvbox Dockerfile to pull that one in. Using http means that our caching proxy on the ci box will cache it, as well.

Also available in: Atom PDF