functional tests with Firefox 35 are broken due this open FF issue:
https://code.google.com/p/selenium/issues/detail?id=8390
Chrome and FF 34 works well, but need to use Chrome because
we cannot pin FF to 34.0 in test instances. Chrome must be added
to test jobs also.
Change-Id: I53d819b78aca26fddbebfc250d2f4dfb4e29ec74
This patch includes two fixes. First, it disables our functional tests
because of a bug in grunt-connect-proxy, which is fixed by an
as-yet-not-accepted patch here:
81631b20c5
Secondly, it includes a temporary fix for the recent NPM CA chain update
explained here:
http://blog.npmjs.org/post/78085451721/npms-self-signed-certificate-is-no-more
The basic premise is that the node package manager no longer supports
their self-signed certificate. This is good! Unfortunately, the
released version of npm is 1.4.4, but the one packaged with nodejs
0.10.26(stable) is 1.4.3. Until nodejs updates itself, we need to
temporarily bork the ca chain to update npm.
Since we're using throwaway slaves, and it's a temporary fix, and
node is only used for builds, I feel this is an acceptable risk.
Change-Id: Ic510e55355966591affbe25ce3f831ca424b2afa
This contains the initial commit for the storyboard web client
project, consisting of the basic build & testing harnesses,
simple set of routes, and a list of basic dependencies
necessary to run an application. It's purpose is to be
reference Javascript/Angular project to test out the build
images.