- Updates travis to run karma
- Adds some actual tests
Sample build success: https://travis-ci.org/djvirgen/kubernetes/jobs/61567253
Note: My branch is currently up to date with master but all the Go stuff is failing in Travis. Not sure why Go is failing, but the Karma stuff is running OK. I've also verified that when a Jasmine test fails, Travis will fail the build (see [this build](https://travis-ci.org/djvirgen/kubernetes/jobs/61567666) here).
remove node modules
make new data file for web ui
initial commit of dashboard
switch back to non SSL request
move port splitting to common place; add to node resource location
Signed-off-by: Patrick Reilly <patrick@kismatic.io>
various path fixes
make svg path relative
work around missing mime type
Signed-off-by: Patrick Reilly <patrick@kismatic.io>
fix paths
fix karma path
remove bad protractor test
Use ginkgo's native support for JUnit in order to generate the XML file.
This is a first step in better integration of our e2e tests with
Jenkins. In order to improve the logged information, we will probably
need to have more native ginkgo tests but this step allows us to see
what Jenkins can already do with this information and what we need to
tweak to improve it.
Tested by running the full e2e tests and inspecting the contents of
junit.xml on the top of the tree.
Textual output is still generated on the console to keep the current
goe2e.sh logs available until the full conversion of our Jenkins
instance to use the JUnit XML is completed.
* Rewrite a bunch of the hack/ directory with modular reusable bash libraries.
* Have 'build/*' build on 'hack/*'. The stuff in build now just runs hack/* in a docker container.
* Use a docker data container to enable faster incremental builds.
* Standardize output to _output/{local,dockerized}/bin/OS/ARCH/*. This regularized placement makes cross compilation work.
* Move travis specific scripts under hack/travis
With new dockerized incremental builds, I can do a no-op `make quick-release` in ~30s. This is a significant improvement.
Otherwise the tree looks "dirty" after hack/install-etcd.sh is executed.
Tested:
- Ran `git status` after running `hack/install-etcd.sh`.
Signed-off-by: Filipe Brandenburger <filbranden@google.com>
In particular, .gitignore, *.go, *.sls and etcd.conf are files that
should not be marked as executable.
Tested: built it with hack/build-go.sh, called all binaries with
the -version flag to confirm they work.
Signed-off-by: Filipe Brandenburger <filbranden@google.com>
Fixed up some scripts to be more robust. Changed the e2e test setup to use g1-small instances. Fixed up documentation to reflect the new script locations. Disabled the "curl | bash" cluster launch as it hasn't been well tested and doesn't include the cloudcfg tool yet.
