1541 Commits

Author SHA1 Message Date
Patrick Ohly
35ceaedcbd prow.sh: install dep if needed
"make test-vendor" depends on dep if the current project uses
dep. Without it, the vendor directory checking was skipped under Prow.
2019-08-29 15:28:21 +02:00
Kubernetes Prow Robot
f85ab5af1e
Merge pull request #26 from ddebroy/windows1
Add rule for building Windows binaries
2019-08-28 07:33:16 -07:00
Deep Debroy
9fba09b414 Add rule for building Windows binaries
Signed-off-by: Deep Debroy <ddebroy@docker.com>
2019-08-28 06:24:26 -07:00
Kubernetes Prow Robot
0400867645
Merge pull request #25 from msau42/fix-master-jobs
Update kind to v0.5.0
2019-08-27 12:23:11 -07:00
Michelle Au
dc0a5d8380 Update kind to v0.5.0 2019-08-21 15:19:39 -07:00
Kubernetes Prow Robot
adb36fc9cd
Merge pull request #16 from msau42/fake-mounter
Add ability to use other mounters for unit testing
2019-08-16 11:10:11 -07:00
Michelle Au
a7d05ccfc9 Add ability to use other mounters for unit testing 2019-08-15 17:41:53 -07:00
Kubernetes Prow Robot
48ce196cd8
Merge pull request #17 from msau42/set-node-server
Correctly set node server in nfs plugin object
2019-08-15 09:06:35 -07:00
Michelle Au
e11fe5f37b Correctly set node server in nfs plugin object 2019-08-14 17:43:14 -07:00
Michelle Au
790b67c89f Add more access modes to volume capabilities 2019-08-14 17:31:09 -07:00
Kubernetes Prow Robot
aa85b82ca7
Merge pull request #23 from msau42/fix-master-jobs
Fix CI jobs on Kubernetes master
2019-08-09 07:13:26 -07:00
Michelle Au
f46191d9a8 Kubernetes master changed the way that releases are tagged, which needed
changes to kind. There are 3 changes made to prow.sh:

1. Use a master commit of kind that includes the fix for Kubernetes
master.
2. Use git clone instead of git checkout (shallow) to source Kubernetes.
This lets kind correctly figure out the Kubernetes release tag.
3. Build kind with make install. The kind fix was not working correctly
when built with go build.
2019-08-08 22:21:41 -07:00
Kubernetes Prow Robot
1cac3af3f5
Merge pull request #22 from msau42/add-1.15-jobs
prow.sh: tag master images with a large version number
2019-07-15 22:57:23 -07:00
Michelle Au
0c0dc300ca prow.sh: tag master images with a large version number 2019-07-15 12:42:20 -07:00
Kubernetes Prow Robot
f4f73cefb9
Merge pull request #21 from msau42/add-1.15-jobs
Add 1.15 jobs
2019-07-11 23:53:04 -07:00
Michelle Au
4e31f078a2 Change default hostpath driver name to hostpath.csi.k8s.io 2019-07-11 17:45:28 -07:00
Michelle Au
4b6fa4a0bd Update hostpath version for sidecar testing to v1.2.0-rc2 2019-07-11 17:45:25 -07:00
Michelle Au
ecc79187c5 Update kind to v0.4.0. This requires overriding Kubernetes versions
with specific patch versions that kind 0.4.0 supports. Also, feature
gate setting is only supported on 1.15+ due to
kind.sigs.k8s.io/v1alpha3 and kubeadm.k8s.io/v1beta2 dependencies.
2019-07-11 14:49:07 -07:00
Michelle Au
a6f21d4054 Add variables for 1.15 2019-07-11 14:33:47 -07:00
Kubernetes Prow Robot
db8abb6e1b
Merge pull request #20 from pohly/test-driver-config
more flexible test driver config
2019-07-08 16:02:02 -07:00
Patrick Ohly
b2f4e051d4 prow.sh: flexible test driver config
By moving the code into a separate function, other CSI drivers have a
chance to overwrite it. For the hostpath driver itself we need the
ability to set the driver name depending on which revision is getting
installed.
2019-07-08 21:58:53 +02:00
Kubernetes Prow Robot
d74ee25bab
Merge pull request #12 from mathu97/remove-csi-common
Remove csi-common dependancies
2019-06-03 18:31:00 -07:00
Mathusan Selvarajah
cc481ceade remove csi-common dependencies 2019-05-30 17:01:07 -04:00
Mathusan Selvarajah
e88a4ea5d4 remove csi-common dependency from vendor files 2019-05-30 16:41:07 -04:00
Kubernetes Prow Robot
03999882f6
Merge pull request #19 from pohly/go-mod-vendor
build.make: allow repos to use 'go mod' for vendoring
2019-05-13 12:41:12 -07:00
Patrick Ohly
066143d146 build.make: allow repos to use 'go mod' for vendoring
How a repo does vendoring is detected based on the presence of
Gopkg.toml.

The vendor check with `dep` was all done locally, but the
corresponding check for `go mod` requires network access. The check
therefore gets skipped when running in the Prow CI in situations where
we are sure that it isn't needed (for example, in a periodic job).
2019-05-11 17:07:14 +02:00
Kubernetes Prow Robot
2c5c9bcd62
Merge pull request #10 from mathu97/nfs-e2e-tests
add Kubernetes End to End tests to the NFS Driver
2019-05-02 16:16:18 -07:00
Mathusan Selvarajah
193faa0f2a create e2e test binary and update docs 2019-04-25 09:05:55 -04:00
Mathusan Selvarajah
7e584f4972 add instructions on how to run e2e tests 2019-04-23 15:43:27 -04:00
Mathusan Selvarajah
959bfe4201 update nfs driver for kube 1.14 2019-04-23 15:43:27 -04:00
Mathusan Selvarajah
f55eb4f5cb add e2e test files 2019-04-23 15:43:21 -04:00
Mathusan Selvarajah
04b68cc678 update vendor files to kube 1.14 2019-04-23 15:42:44 -04:00
Kubernetes Prow Robot
25ef469f69
Merge pull request #9 from jsafrane/add-pr-template
Add PR template
2019-04-15 07:50:18 -07:00
Kubernetes Prow Robot
0bee749334
Merge pull request #18 from pohly/go-version
update to Go 1.12.4
2019-04-15 07:44:09 -07:00
Jan Safranek
17d9131673 Add PR template 2019-04-15 14:07:11 +02:00
Patrick Ohly
e157b6b514 update to Go 1.12.4
Kubernetes also requires 1.12. We pick the latest stable release
for CI builds.
2019-04-15 09:45:23 +02:00
Kubernetes Prow Robot
88dc9a47e5
Merge pull request #17 from pohly/prow
prow.sh: skip sanity testing if component doesn't support it
2019-04-11 13:38:45 -07:00
Patrick Ohly
0fafc663dc prow.sh: skip sanity testing if component doesn't support it
Whether a component supports sanity testing depends on the
component. For example, csi-driver-host-path enables it because it
makes sense there (and only there). Letting the prow.sh script decide
whether it actually runs simplifies the job definitions in test-infra.
2019-04-11 22:32:01 +02:00
Kubernetes Prow Robot
bcac1c1fb6
Merge pull request #16 from pohly/prow
prow.sh: update csi-driver-host-path
2019-04-11 07:06:14 -07:00
Patrick Ohly
0b10f6a4b0 prow.sh: update csi-driver-host-path
This pulls in
https://github.com/kubernetes-csi/csi-driver-host-path/pull/37, which
turned out to be necessary for pre-submit testing of the
livenessprobe.
2019-04-11 13:37:43 +02:00
Kubernetes Prow Robot
0c2677e8fe
Merge pull request #15 from pengzhisun/master
build.make: Replace 'return' to 'exit' to fix shellcheck error
2019-04-11 03:04:14 -07:00
Pengzhi Sun
ff9bce4a71 Replace 'return' to 'exit' to fix shellcheck error 2019-04-11 17:42:44 +08:00
Kubernetes Prow Robot
c60f3823c0
Merge pull request #14 from pohly/prow
prow.sh: remove AllAlpha=all, part II
2019-04-10 07:08:16 -07:00
Patrick Ohly
7aaac22571 prow.sh: remove AllAlpha=all, part II
This was already meant to be done earlier in cda2fc5874b42ed68b.
While at it, extend the permanent TODO with guidance on future feature
gates.
2019-04-10 08:44:54 +02:00
Kubernetes Prow Robot
66177736d7
Merge pull request #13 from pohly/prow
prow enhancements
2019-04-09 14:26:46 -07:00
Patrick Ohly
cda2fc5874 prow.sh: avoid AllAlpha=true
It turned out to not work. Instead of reverting the commit which
introduced this, let's better document this explicitly.
2019-04-09 10:48:37 +02:00
Patrick Ohly
546d5504a1 prow.sh: debug failing KinD cluster creation
When KinD fails in a Prow job, we need additional information to
understand why it failed.
2019-04-09 10:48:37 +02:00
Patrick Ohly
9b0d9cd743 build.make: skip shellcheck if Docker is not available
Not all environments have Docker. The simplifying assumption here is
that if the Docker command is available, it's also usable.
2019-04-09 10:48:37 +02:00
Patrick Ohly
aa45a1cd9b prow.sh: more efficient execution of individual tests
When running only some tests, sometimes extra, unnecessarily work was
done, like bringing up the cluster without alpha gates.
2019-04-09 10:48:37 +02:00
Patrick Ohly
f3d1d2df5c prow.sh: fix hostpath driver version check
The previous logic failed for canary jobs, those also deploy a recent
driver. Instead of guessing what driver gets installed based on job
parameters, check what really runs in the cluster and base the
decision on that.

We only need to maintain this blacklist for 1.0.x until we replace it
with 1.1.0, then this entire hostpath_supports_block can be removed.
2019-04-08 16:39:58 +02:00