-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 Image Push Job For Kubernetes CSI #16942
Add Image Push Job For Kubernetes CSI #16942
Conversation
Welcome @vitt-bagal! |
Hi @vitt-bagal. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@pohly Could you please have a look ? |
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.
Just one minor comment. Overall this looks like it might work, as far as I understand the process.
testgrid-dashboards: sig-storage-csi-node-driver-registrar | ||
decorate: true | ||
branches: | ||
- ^master$ |
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.
Can you add a comment explaining that this is for publishing the "canary" images, something that we only do on the master branch?
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.
Added comment
@@ -0,0 +1,29 @@ | |||
postsubmits: | |||
# This is the github repo we'll build from. This block needs to be repeated | |||
# for each repo. |
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.
Eventually we'll probably want to have a generator script for all the various repos. There are too many to of them to create and maintain this file manually. But for now as a test it's okay.
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.
Looks good to me.
/ok-to-test |
/approve |
/assign @BenTheElder |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Katharine, pohly, spiffxp, vitt-bagal 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 |
@vitt-bagal: Updated the
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@pohly @Katharine Looking at prow it seems that postsubmit job for nodedriver registrar is not executed. Do we need to wait for a commit to be merged to node driver registrar master ? |
Yes. Postsubmits run post submit (after a merge), there's also a branch regex optionally that would restrict to only certain pushes. |
Thanks @BenTheElder @pohly As Postsubmit job runs after a merge, Is it possible for us to commit something in node driver registrar master ? e.g. sync release tool ? |
I created kubernetes-csi/node-driver-registrar#71 |
@pohly @BenTheElder Image push job for node-driver-registrar got triggered after PR#71, however it fails: https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/post-node-driver-registrar-push-images/1247569283886616576 Could you please check once? |
Hi, please check the "artifacts" link to see more logs. I unfortunately really don't have the bandwidth to debug everyone's CI. |
The build.log from artifacts point to a url 'https://console.cloud.google.com/cloud-build/builds/ac677e83-ad64-4ec3-8204-f0727b714682?project=874328413592' which gives us error You do not have sufficient permissions to view this page. @pohly Can you access the logs? |
the CI robot has permissions and the tooling should be downloading all logs.
someone in wg-k8s-infra owns this project.
…On Mon, Apr 13, 2020 at 3:19 AM vitt-bagal ***@***.***> wrote:
The build.log
<https://storage.googleapis.com/kubernetes-jenkins/logs/post-node-driver-registrar-push-images/1247569283886616576/artifacts/build.log>
from artifacts point to a url '
https://console.cloud.google.com/cloud-build/builds/ac677e83-ad64-4ec3-8204-f0727b714682?project=874328413592'
which gives us error *You do not have sufficient permissions to view this
page*. @pohly <https://github.com/pohly> Can you access the logs?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16942 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHADK4WSCNZ4ROLKJQMUHDRMLRMJANCNFSM4LTNDMSA>
.
|
@pohly @vitt-bagal you should probably open a PR against https://github.com/kubernetes/k8s.io/blob/master/groups/groups.yaml#L705-L712, I'm not aware of the history of how that group was created, but I doubt it should be just @dims. That would let you view the cloud-build link. But I agree I'm confused why the logs weren't downloaded to Here's what I'm able to see
|
This was way before we had automation: It was mostly created as a placeholder to try things and no one got added afterwards. +1 to update the list of folks |
So who should be on that list? |
/uncc |
the build is failing as we have a older docker version, see full log : https://paste.centos.org/view/raw/f725c290 i have a PR in test-infra for bumping gcb-docker-gcloud image to newer golang and docker - #17299 As for the list of people for that ACL for the job, please add all the leads for sig-storage, technical leads and any one that takes care of the csi images |
Right now, none of the people involved with SIG-Storage have access to logs when staging fails (kubernetes/test-infra#16942 (comment)). As suggested in that discussion (kubernetes/test-infra#16942 (comment)), I am adding the current SIG chairs and tech leads plus myself as someone who has been working on image publishing.
Adding image push job for the Kubernetes CSI packages for automating Image build, push(to staging area) process .