This enables cases like `docker build --output=bin/
https://github.com/Azure/aks-engine.git` without having to manually
check out code and everything.
It supports cross compilation so a user can set
`--platform=darwin/amd64` or `--platform=local`, etc. to get a binary
for whatever they need.
These scripts/Dockerfiles are either unused by CI or are not actively being maintained, so I assume these are safe to remove.
Signed-off-by: Matthew Fisher <matt.fisher@microsoft.com>
* chore(ci): use circle-ci as CI platform
* ref(Dockerfile): cache make bootstrap step
* chore(ci): separate e2e tests into separate step
* ref(ci): require manual approval to start e2e tests
* ref(ci): use microsoft/acs-engine:latest as base test image
* chore(kubectl): bump kubectl to v1.6.6
* fix(setup): install gometalinter as part of bootstrap
* ref(CI): remove docker build, refactor e2e test step
Circle CI runs all steps in the microsoft/acs-engine:latest container
and clones the latest code into the container, so no explicit need to
build an image
* fix(ci): explicitly run bootstrap at each step
* fix(ci): add GOPATH env
* fix(ci): bootstrap once. maybe?
* ref(e2e): set default ENV vars, remove cruft
* ref(ci): don't hold e2e pending on unit tests
* docs(ci): add CI badge
* fix(e2e): fix env vars
* fix(e2e): run e2e in docker container
* Revert "fix(e2e): run e2e in docker container"
This reverts commit 9e7e4765257d6a7e52d5af5eb547da6f74f9fea1.
* ref(e2e): remove Jenkins groovy scripts
* ref(ci): run subset of e2e tests for PRs, remove KV tests
- acse-pr.json becomes acse-feature-validation.json that we can use for
integration testing at a later stage (merge to master, releases, etc.)
- New acse-pr.json runs 4 e2e tests, one for each orchestrator
- Remove Key Vault setup in PR tests.
* chore(e2e): run full set of feature validation tests on master branch
* fix(vendor): fix file permissions via glide install
* chore(vendor): add JiangtianLi/gettext, hardcode vers, bump Azure vers
- Add github.com/JiangtianLi/gettext as a dependency of the project
- Change all third-party dependencies from "^" (automatic minor bumps) to
hardcoded versions which require explicit version changes in glide.yaml.
This is because we (Microsoft) need to re-register every OSS version we
use, even if the project at a certain point of time was approved by MSFT
OSS.
- Allow patch level upgrades of github.com/Azure/go-autorest and
github.com/Azure/azure-sdk-for-go
- Bump github.com/Azure/go-autorest from v8.1.0 to v8.1.1
- Bump github.com/Azure/azure-sdk-for-go from v10.1.0-beta to v10.1.1-beta
- Running `glide update` is now a lot safer.
* First round of i18n in acs-engine based on gettext. Subsequent changes will replace and extract resource strings in acs-engine and make acsengine/api package's i18n used by other go program.
* Update acs-engine go source to use translation functions. Generate translation resource files.
* Vendor github.com/leonelquinteros/gotext package using glide
* Rebase and update translation for update and deploy command
* Move test translation files so that translations directory is used for go-bindata
* Use go-bindata to add resource strings to acs-engine binary
* Fix reading bindata and unit test
* Update translation files
* More fix/refactor after rebase and add README
* Update resource files
* Add LCG files converted from PO files.
* Update translation bindata
* Remove go generated translation bindata