Getting this error when running pipeline in Jenkins and running go test
docs/docs.go:11:2: github.com/alecthomas/template#v0.0.0-20190718012654-fb15b899a751: Get "https://proxy.golang.org/github.com/alecthomas/template/#v/v0.0.0-20190718012654-fb15b899a751.zip": x509: certificate signed by unknown authority
error pic
Related
While trying to execute some shell command to a remote server from Jenkins, I am getting "Host key verification failed." error.
I have installed Jenkins in a docker on my MAC. Now from the Jenkins browser, I want to run some shell command to a remote server (which is accessible).
To do that I already added the server (10.206.y.z) in the configure page of jenkins (by providing hostname i.e. 10.206.y.z, username & the key generated in 10.206.y.z server in the SSH Servers section) & tested the connection. The connection test passed & then I saved the configuration.
For executing shell command on 10.206.y.z, I created a FreeStyle project & in the Execute Shell section I am passing ssh root1#10.206.y.z 'hostname'.
If I run the project by clicking 'Build Now', I am getting the below error & the build fails.
Running as SYSTEM
Building in workspace /var/jenkins_home/workspace/TestProject
[TestProject] $ /bin/sh -xe /tmp/jenkins4234161871485451783.sh
+ ssh root1#10.206.y.z hostname
Host key verification failed.
Build step 'Execute shell' marked build as failure
Finished: FAILURE
Any help please?
I think that the problem is the key. You are using the key generated in the destination machine (10.206.y.z)
You should use the key generated on the jenkins server and pass it to the destination server. For that you could use ssh-copy-id
I am getting error while trying to login dtr from my pipeline groovy scrit. it is saying that that was a credential error.
docker.withRegistry('https://dtrlb-oe3ko7eumonjw.eastus.cloudapp.azure.com/','ddcadmin')
and my error is:
enter image description here
The docker.withRegistry can find credential in Global domain, not system domain.
I am trying to do a docker build from a Jenkins job and I am getting the below error. Any ideas what is causing this error.
11:10:32 Step 1 : FROM docker.xxxx.com/xx/pkg-ssl:7-jdk8
11:10:32 Get https://docker.xxxx.com/v2/xx/pkg-ssl/manifests/7-jdk8:
unauthorized: unable to get identity token from basic auth credentials:
invalid_grant: invalid authentication credentials given
11:10:32 Build step 'Docker Build and Publish' marked build as failure
I'm facing problem in creating a slave machine using jclouds plugin.
machine get added in slave list but as an off-line. And on relach-slave following error are coming.
Launching slave agent: cd /tmp && java -jar slave.jar
ERROR: Unexpected error in launching a slave. This is probably a bug in
INFO: <<
(ubuntu:rsa[fingerprint(43:1a:6e:3a:1b:9c:6f:67:4a:c3:e1:9c:1f:be:52:51),sha1(cf:17:36:58:2f:12:97:76:bf:cf:a7:10:97:1c:5e:c4:91:92:8d:3f)]#192.168.1.108:22)
error acquiring SFTPClient() (attempt 1 of 7): Timeout expired
I have a docker container with jenkins deployed using OpenShift Origin.
Now I want to use Jenkins to build/test and deploy other OpenShift apps.
So I try to login on my OpenShift-server (from inside my jenkins) but than I get the following error. Can someone help me?
Started by user Jenkins Admin
[EnvInject] - Loading node environment variables.
Building in workspace /var/lib/jenkins/jobs/s2i-build-deploy/workspace
[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - Injecting as environment variables the properties content
APP_HOSTNAME=http://test.apps.example.com
USER_NAME=admin
PASSWORD=admin
OSO_SERVER=ip.compute.internal:8443
DEVEL_PROJ_NAME=test
SERVICE=test
[EnvInject] - Variables injected successfully.
[workspace] $ /bin/sh -xe /tmp/hudson1352752763797328747.sh
+ oc login -uadmin -padmin --server=ip.compute.internal:8443
error: x509: certificate signed by unknown authority
Build step 'Execute shell' marked build as failure
Finished: FAILURE
The oc login-command is working when I'm performing directly in my server.
That error means you need to also specify the CA that was used to sign the API server's certificate. You will need to also specify --ca-file (check oc help options) with the ca.crt of the master in order to login.
As mentioned in this comment try:
oc login $OPENSHIFT_URL --insecure-skip-tls-verify=true