How to solve the jenkins expiration request of Code Cloud webhook?

Code Cloud webhook request jenkins expiration

Automated deployment of Jenkins and Gitee (plug-ins) has been going on for the past two days, but can only be built manually on Jenkins. The
network basically uses Jenkins"s Generic Webhook Trigger plug-in, but in the last step, when testing, refusing to connect
to find this plug-in can be said to be very happy. After all, it is official to do it step by step according to the documentation, or to refuse to connect to the final test

.

first, let"s put down the configuration on the jenkins side



webhook

.

questions

I"ve tested it over and over again. I submit code that triggers the hook and only displays excution expired but if you click build on jenkins, you can get the updated code and automatically deploy it to the server.
therefore, I think the processes on both sides are the same, only webhook

May.02,2021

in Gitee plugin and after two days of various searches, it turns out that it is because the webhook url in Ciyun needs to be configured with a public network ip, which means" system settings "in jenkins's system management

.


ip

po


really solves a big problem. Also drunk, the official website wrote 127.0.0.1 local ip, made a big hole

Menu