Open hutchic opened 5 months ago
Hi @hutchic. Thanks for your PR.
I'm waiting for a jenkins-x member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Someone can check this? The warning is VERY annoying.
/ok-to-test
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: msvticket
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@hutchic Can you take a look on this?
@jrx-sjg not really no -- sorry. My time got occupied elsewhere
@hutchic: The following test failed, say /retest
to rerun them all:
Test name | Commit | Details | Rerun command |
---|---|---|---|
pr | ca12c21018819b22e4deeac40ba8751ef4fc6d94 | link | /test |
Hi @hutchic , the PR build failed because an used import has been left on pkg/plugins/trigger/pull-request.go.
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 GO111MODULE=on go build -ldflags "-X github.com/jenkins-x/lighthouse/pkg/version.Version='-dev+b331b30'" -o bin/webhooks cmd/webhooks/main.go
# github.com/jenkins-x/lighthouse/pkg/plugins/trigger
pkg/plugins/trigger/pull-request.go:31:2: "github.com/pkg/errors" imported and not used
make: *** [Makefile:76: build-webhooks-linux] Error 1
Error: Process completed with exit code 2.
Can you please delete it and commit the changes so the PR can go on?
Based on what I've been able to discern from slack / github https://github.com/jenkins-x/jx/issues/8589 isn't an actionable warning. On top of that it seems backwards compatibility is going to be maintained.
With that in mind let's not create a non-actionable warning