Executing 'make help' will display a list of available targets
for building minikube. The output will look as follows
Available targets for minikube v1.4.1
--------------------------------------
iso-menuconfig Configure buildroot configuration
linux-menuconfig Configure Linux kernel configuration
all Build all different minikube component
drivers Build Hyperkit and KVM2 drivers
docker-machine-driver-hyperkit Build Hyperkit driver
integration Trigger minikube integration test
integration-none-driver Trigger minikube none driver test
integration-versioned Trigger minikube integration testing
...
...
...
The bash shell is not very good at playing init(1), let
tini handle this instead by doing `docker run --init`.
This makes it forward signals properly to e.g. make,
and also reaps processes for long-running containers.
However, we _need_ to override the entrypoint of the
karalabe/xgo image, since it'll self-destruct otherwise.
It (/build.sh) expects the command to be the import path
and cannot handle getting the bash command line to run.
When we are doing the "cross" compile targets, we
force rebuilding all packages (up-to-date or not).
For the default native target "out/minikube", we
can do a much faster build (10x!), for development.
Leaving all the cross target to rebuild, as before.
Also the _test.go files are only used for unit tests.
This service runs in a VM and is responsible for:
1. Determining which PRs need to be analyzed
2. Running mkcmp against each PR
3. Commenting the results on the PR via minikube-bot
This PR also moves the mkcmp code into its own directory.
This a pure build target, no test done (yet)
No virtualization supported on this platform
Adopt packaging to handle multiple arch, but
don't package anything extra by default yet.
This PR adds a skeleton for mkcmp, a binary to compare the performance
of two versions of minikube. It adds a Makefile rule out/mkcmp which
builds the binary.
Medya Ghazizadeh
tstromberg
Medya Gh
Anders F Björklund
Sharif Elgamal
priyawadhwa
Nanik T
tanjunchen