-
Notifications
You must be signed in to change notification settings - Fork 63
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
Add CI to verify hydration works. #50
Conversation
* Write a golang test to verify we can hydrate the manifests * Trigger go tests under prow * Related to GoogleCloudPlatform#42
This isn't ready for review yet; I need to verify that the tests actually run successfully. |
Logs show
I suspect the problem is that the name is too long so it gets rejected. Name is 67 characters long |
kubeflow/testing#683 was merged; lets see if that fixes the problem. /test all |
go tests actually failed even though the presubmit is reported as success; probably because we aren't probably taking the junit files into account in the github status. |
Thanks! This helps development a lot. |
/test all |
like that is what the go unittests task currently requires.
The test failure
Is because we are issuing "go test ./..." in the root of the repository which doesn't have a "go.mod" file. |
/hold cancel @Bobgy Tests are passing; this is ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
Thanks @jlewi! this is great for development
@@ -5,5 +5,5 @@ patchesStrategicMerge: | |||
- default-install-config.yaml | |||
- pipeline-minio-install-config.yaml | |||
resources: | |||
- ../../../upstream/manifests/stacks/gcp # {"type":"string","x-kustomize":{"setBy":"kpt","partialSetters":[{"name":"kustomize_manifests_path","value":"../../../upstream/manifests"}]}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not very related to this PR, but shall we add gcp stacks back to manifests, I'm making some gcp specific components and I think a gcp stacks is needed, we cannot compose all of them in instance/ folder
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Bobgy 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 |
Write a golang test to verify we can hydrate the manifests
Trigger go tests under prow
The name of the stack was changed from GCP to generic so we need to update it.
Related to Setup CI against blueprint deployments #42