I install the Gitea plugin for Jenkins and try to add Gitea server in Configuration
My Gitea URL:
But I get HTTP 403/Forbidden warning.
I find a similar question: How to connect Jenkins and Gieta
And I don't know clearly how to "make Jenkins to send the entire certificate chain" at the end of that answer, if this way works.
It should be fine as official documentation says-
Hint: you can ignore a "HTTP 403/Forbidden" error here in case your gitea instance is private.
https://plugins.jenkins.io/gitea/
Related
When I try to link a jenkins project to my gitlab project, I have the following error :
Here is the form and the error message.
The jenkins project "test" does exists and the credentials are good.
The issue is probably not about the credentials but that gitlab seem to not be able to read the fields.
I tried with both chrome and Firefox.
I also tried to use webhook, but for services hosted on the same network, doc says it may be hazardous. So I'd rather use the first method.
Some information about my environment:
Linux Centos 7
jenkins and gitlab are built by docker-compose
hosted on localhost
jenkins and gitlab use different ports (8080 and 8081)
I found only one thread on the internet about it here but no answer were given.
Any ideas?
Thanks
This is my first post, I hope I did not make any mistake.\
On openshift cluster i deployed gitea v1.9.0 and i added a webhook for triggering the pipeline, now i'm getting the following error:
Delivery: Post
https://ip#:8443/apis/build.openshift.io/v1/namespaces/jenkins/buildconfigs/pipeline6/webhooks/somesecret/generic:
x509: certificate signed by unknown authority
How can i disable ssl verification in Gitea ? And is there another way to trigger the build in openshift's pipeline ?
No, there is no possibility to disable the ssl verification in Gitea AFAIK.
I had the same error by the integration with Jenkins. The problem was that Gitea does not support the "certificate discovery" feature (as for example a browser like Firefox does, see here) and Jenkins was misconfigured and was sending only the end entity certificate.
After making Jenkins to send the entire certificate chain, the problem disappeared.
Hi iam trying to integrate jenkins with Udeploy server.
When i test the connection using IBM UrbanCode Deploy Pipeline Plugin Configuration and the test connection option iam getting the below error
Error connecting to IBM UrbanCode Deploy: 503using URI: https://udeploy.oe.company/rest/state
I could confirm there is no issue with firewall. i am able to do a curl successfully to the url.
Iam not able to see anything in jenkins logs.
https://jenkinsurl.org/log/all
is there anyway i could check the logs of the plugin to see what is happening during connection?
Any help appreciated.
You might have an SSL issue. If using self-signed certs, try swapping the self signed certs. Note that Urbancode might be using the IBM JDK which has its own truststore, and you'll need to store the Jenkins certs there.
I am trying to trigger jenkins build whenever there is a push to GitLab.
I am referring to https://github.com/jenkinsci/gitlab-plugin.
When I test the connection for webhook it shows execution expired.
I am using:
Jenkins ver. 2.60.1
GitLab version 9.4.0-rc2-ee
Git lab plugin 1.4.6
The exact error message, clicking "Test setting" from GitLab:
We tried to send a request to the provided URL but an error occurred: execution expired
As mentioned in issue 128:
This looks and sounds like a configuration or network error.
Maybe your machine is not publicly available on the webhook address (firewall etc).
For instance, on Digital Ocean server, you would need to open up the port (mentioned in git-auto-deploy.conf.json) in the firewall:
sudo ufw allow 8866/tcp
Double-check though what you put in Manage Jenkins > Configure in term of Gitlab information (connection name, host url, credentials), as mentioned in jenkinsci/gitlab-plugin issue 391.
See GitLab Integration Jenkins: Configure the Jenkins server
It means issues in between jenkins server and gitlab or github server.
Like what I did:
I have set my local-IP:port/project/jenkins_project_name
http://192.168.1.21:8080/project/jenkins_project_name
and set the above URL in the gitlab webhook, it shouldn't work - right?
Because it's an IP that's private and not routable.
SO later I realized and set the public-IP and then hook worked.
http://public_IP:8080/project/jenkins_project_name
Note: To routable public-IP, you should expose port in your router [e.g. 8080 was for me or anything want ]
Hope this works.
I have faced the same issue.
In my case Jenkins is running in an AWS EC2 instance. I have resolved the issue by whitelisting the Public IP addresses of Gitlab on port 443 into the instance security group.
In BitBucket, I have a POST service setup with hopes to remotely trigger a build on my jenkins CI server but when I push to my BitBucket account, it appears to not work.
I have windows auth enabled on the server that hosts jenkins.
I tried supplying the POST service with this url:
http://username:password#CiBuilderServer.com/job/MyProject/build
This url works in my browser. I tried curl and received this error:
curl: (47) Maximum (50) redirects followed
I'm guessing however BitBucket makes the request, the credentials are not sent correctly.
IIS Log:
x.x.x.x POST /job/MyProj/build - 80 - x.x.x.x Bitbucket.org 401 2 5 62
Any ideas or workarounds?
Enabling both basic auth and windows auth did the trick. I know bitbucket is written in Python. Maybe Python and Windows Auth don't play well together?