Conversation
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
fejta
left a comment
There was a problem hiding this comment.
/hold
What produces the images?
Do a /hold cancel when you're ready for it to merge
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fejta, PiotrSikora The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
|
No idea who/what produces the images. I believe it's a manual step, but I don't have permissions to push the images, so I don't have the details. cc @utka |
|
/lgtm |
|
So we should cancel the hold and once it's merged we should get prow on-call to build & push the image? I that correct? |
|
This is my understanding how prow on call works |
|
/hold cancel |
|
I've built and pushed the image. |
|
This isn't really a prow service. I suspect But we should have access to the Ideally we create postsubmits to build and push these images, like we do for kubernets/test-infra images. Then we can make sure prow is running those correctly. Examples of these jobs:
|
* Update prowbazel in proxy/master and proxy/wasm to 0.5.8. Signed-off-by: Piotr Sikora <piotrsikora@google.com> * review: don't change VERSION here (do it in #1493 instead). Signed-off-by: Piotr Sikora <piotrsikora@google.com>
Signed-off-by: Piotr Sikora piotrsikora@google.com