Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update release tools #68

Merged
merged 38 commits into from
Jan 2, 2020

Conversation

saad-ali
Copy link
Member

@saad-ali saad-ali commented Jan 2, 2020

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Update release-tools to head of https://github.com/kubernetes-csi/csi-release-tools/ master branch

Changes go build version from 1.12.4 to 1.13.3

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

msau42 and others added 30 commits October 30, 2019 18:08
Add new variables for 1.16 and remove 1.13
This is the latest release. Updating is useful to ensure that we have
all of the latest fixes and enhancements.
Some operations are sensitive to the version of Go that is used. In
the past, formatting of source differed depending on the
version. Right now it is the content of the vendor directory which
changes when switch back and forth between 1.12 and 1.13.

We don't want to impose a certain workflow on developers, like forcing
all invocations of Go to run inside a container. If developers want
that, they can set up their development environment accordingly.

But we should warn about this aspect to raise awareness. "make"
invocations which involve Go now compare against the projects Go
version (specified in travis.yml) once at the beginning. This is only
a warning because we don't know which future version will be
compatible with the project.

Vendor directory handling gets updated, too: verification is now a
separate script (became too complex for make) and there is a
corresponding "update-vendor.sh". In contrast to verification,
updating vendor is not integrated into make and thus itself invokes
the go version check.
This avoids dependencies on the Go module cache or the upstream code
hosting.
prow.sh: use vendor directory if available
Depending on the error, those logs are needed to debug failures.
prow.sh: also log output of system containers
Inside a real Prow job it is better to clean up at runtime instead of leaving that to the Prow job cleanup code because the later sometimes times out.

Signed-off-by: Mucahit Kurt <[email protected]>
…eanup

delete kind cluster after tests run
kind v0.6.0 appends the kubeconfig with the default config at
~/.kube/config.
…ure can be tested. Test cases that test accessing volumes from multiple nodes need to be skipped
Enable topology testing with hostpath driver
…ersion_gt

Improve snapshot-controller running check and version_gt to support multiple formats
Improve README by adding an explicit Kubernetes dependency section
This requires adding one more parallel e2e test run with
a special focus flag because snapshot tests are still guarded
with a "[Feature:VolumeSnapshotDataSource]" tag. The setting that
skips all tests with "[Feature:.*]" has to be removed because it
overrides the focus.

We don't have serial snapshot tests yet. This needs to be modified
again if we add any in the future.
Enable snapshot tests in 1.17 to be run in non-alpha jobs.
…netes_fix

Fix version_gt to work with Kubernetes prefix
@k8s-ci-robot k8s-ci-robot requested a review from pohly January 2, 2020 19:41
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 2, 2020
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jan 2, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saad-ali

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 2, 2020
@msau42
Copy link
Collaborator

msau42 commented Jan 2, 2020

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 2, 2020
@saad-ali
Copy link
Member Author

saad-ali commented Jan 2, 2020

/test pull-kubernetes-csi-external-resizer-1-16-on-kubernetes-1-16

@msau42
Copy link
Collaborator

msau42 commented Jan 2, 2020

CI failure is due to two reasons:

  1. resizer has overridden e2e versions to use k8s latest. I think we should remove it.
  2. hostpath deployment version is fixed to 1.2.0 which doesn't support beta snapshots yet. We can cut an rc tag and update the hostpath version that the test uses

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 2, 2020
@@ -183,7 +187,7 @@ configvar CSI_PROW_WORK "$(mkdir -p "$GOPATH/pkg" && mktemp -d "$GOPATH/pkg/csip
#
# When no deploy script is found (nothing in `deploy` directory,
# CSI_PROW_HOSTPATH_REPO=none), nothing gets deployed.
configvar CSI_PROW_HOSTPATH_VERSION "v1.2.0-rc8" "hostpath driver"
configvar CSI_PROW_HOSTPATH_VERSION "v1.2.0" "hostpath driver"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just tagged an rc for hostpath repo which has the beta snapshots changes. Can you try setting v1.3.0-rc2 here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do!

@msau42
Copy link
Collaborator

msau42 commented Jan 2, 2020

The tests ran but results got clobbered. Investigating...

@saad-ali saad-ali force-pushed the updateReleaseTools branch from 936ef9a to d8fef29 Compare January 2, 2020 22:44
@saad-ali
Copy link
Member Author

saad-ali commented Jan 2, 2020

Rebased with kubernetes-csi/csi-release-tools#60 and kubernetes-csi/csi-release-tools#61 merged.

All green now.

PTAL

@msau42
Copy link
Collaborator

msau42 commented Jan 2, 2020

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 2, 2020
@k8s-ci-robot k8s-ci-robot merged commit 2adce74 into kubernetes-csi:master Jan 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants