Help required: jenkins SSH connectivity issue

1,644 views
Skip to first unread message

Sakshi Rathore

unread,
Jul 20, 2020, 5:43:39 PM7/20/20
to Jenkins Users
0I have a bash script which connects and exexutes programs from my local to remote server and now this should be executed from jenkins build so for this jenkins is taking continous changes from git for this script but my build is failing with below error:

Warning: Identity file /c/Users/D35N/Downloads/GitHubProjeckt/Automation/GitHubProjeckt/newharbortestkey not accessible: No such file or directory. Host key verification failed. Build step 'Execute shell' marked build as failure

I have tried to set ssh connectivity in my jenkins server for this remote server incredentials and ssh plugins but using my key i am getting an error cant connect to the server.

when i run the script from local it works fine and my ssh connection gets established properly using SSH key.

jenkins server is also integrated or installed on my kuberenets cluster which is my remote server in this case and bash script should execute on this kuberenets cluster.

i generated ley for jenkins in remote server and using this key for ssh plugin setup but i am getting cant connect to the server error everytime.

jeremy mordkoff

unread,
Jul 21, 2020, 12:00:34 PM7/21/20
to Jenkins Users
Where is that file referenced? In your .ssh/config file? It sounds like a simple path issue -- the config file is referencing a location that is not available to jenkins. You can override this on the command line, e.g. something like -i /c/Users/jenkins/ssh/id_rsa

sakshira...@gmail.com

unread,
Jul 22, 2020, 2:53:02 AM7/22/20
to Jenkins Users
thanks, i tried in this way also by overrirding file but connection is not established. during more workaround i tried editing sshd config for parameter PermitRootLogin yes but after this change i am not able to login into server itself using ssh key. Is there any suggestion how can i revert back my changes now. i cant login to server and sshd config is server specific in my case. Please suggest.

jeremy mordkoff

unread,
Jul 22, 2020, 11:54:46 AM7/22/20
to Jenkins Users
ouch. I always keep one window open ssh'd in as root when I play with sshd_config. Hopefully you have console access and a username/password with sudo rights. 

On Monday, July 20, 2020 at 5:43:39 PM UTC-4, Sakshi Rathore wrote:

Sakshi Rathore

unread,
Jul 23, 2020, 2:07:28 AM7/23/20
to jenkins...@googlegroups.com
Unfortunately i dont hv duplicate instance open। I only have ssh-key to login to the server which was working before

Any other way to implement this?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/366717fe-86d5-4f83-8990-7584308b3a36o%40googlegroups.com.

Sakshi Rathore

unread,
Jul 23, 2020, 7:09:03 AM7/23/20
to jenkins...@googlegroups.com
i managed to resolve login problem but still facing issue while connecting my remote server using ssh key to jenkins.

i have shell script also where i am doing ssh connection from local to remote and normal execution is working fine without jenkins but when i schedule a build in jenkins it fails. seeking for the suggestions on this if step by step process can be suggested it will be great help. I am stuck in this problem from long time. 

i followed below steps to resolve it till now but didnt work:

* Create an SSH key pair (public/private)   Ran the command “ssh-keygen -t rsa -C "Jenkins agent key" -f "jenkinsAgent_rsa"  “

* Create an SSH credential in the Jenkins machine and put the private key there Created the credentials and put jenkinsAgent_rsa into it.

* Create an SSH agent see https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/CONFIGURE.md#configure-launch-agents-via-ssh – This is creating a node which I didn’t do before – so I created the node and selected the credential with the private key. The verification strategy slect is non-verifying.

  * Select the SSH credential created before as credentials

  * Chose the verification strategy that you want, see the documentation, if you have problems start with the "Non verifying Verification Strategy" you can change it later

* Add the public key on ~/.ssh/authorized_keys This was done

 

I tried to relaunch the node and got the following:


SSH Connection failed with IOException: "Key exchange was not finished, connection is closed.", retrying in 15 seconds. There are 1 more retries left.
[07/23/20 11:03:50] [SSH] WARNING: The SSH key for this host does not match the key required in the connection configuration. Connections will be denied until the host key matches the configuration key.
Key exchange was not finished, connection is closed.
ERROR: Connection is not established!
java.lang.IllegalStateException: Connection is not established!
	at com.trilead.ssh2.Connection.getRemainingAuthMethods(Connection.java:988)
	at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.getRemainingAuthMethods(TrileadSSHPublicKeyAuthenticator.java:88)
	at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.canAuthenticate(TrileadSSHPublicKeyAuthenticator.java:80)
	at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:218)
	at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:171)
	at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:863)
	at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:435)
	at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
[07/23/20 11:04:05] Launch failed - cleaning up connection
[07/23/20 11:04:05] [SSH] Connection closed.

Dirk Heinrichs

unread,
Jul 23, 2020, 8:28:34 AM7/23/20
to jenkins...@googlegroups.com
Am Donnerstag, den 23.07.2020, 13:08 +0200 schrieb Sakshi Rathore:

* Add the public key on ~/.ssh/authorized_keys This was done


You did that on the agent, I guess, and "~" here means "the /home of the user" you try to connect as?

HTH...

Dirk
-- 
Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.
signature.asc

Dirk Heinrichs

unread,
Jul 23, 2020, 8:32:11 AM7/23/20
to jenkins...@googlegroups.com
Am Donnerstag, den 23.07.2020, 13:08 +0200 schrieb Sakshi Rathore:

[07/23/20 11:03:50] [SSH] WARNING: The SSH key for this host does not match the key required in the connection configuration. Connections will be denied until the host key matches the configuration key.

You're sure you selected non-verifying strategy? Looks to me like it's still trying to verify the host key.
signature.asc

Sakshi Rathore

unread,
Jul 23, 2020, 9:10:02 AM7/23/20
to jenkins...@googlegroups.com
Yes /home/user/.ssh/authorized_keys is complete path 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

jeremy mordkoff

unread,
Jul 23, 2020, 9:47:16 AM7/23/20
to Jenkins Users
I think the issue is that the client does not trust the server's host key. These keys are stored by the client in ~/.ssh/known_hosts  Try copying/appending your .ssh/known_hosts file to jenkins'



On Monday, July 20, 2020 at 5:43:39 PM UTC-4, Sakshi Rathore wrote:

Sakshi Rathore

unread,
Jul 27, 2020, 3:38:17 AM7/27/20
to jenkins...@googlegroups.com
thanks , can you please suggest how can i change it to non verifying one?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

Sakshi Rathore

unread,
Jul 27, 2020, 3:39:45 AM7/27/20
to jenkins...@googlegroups.com
thanks , i tried this as well but while getting connection encountring below error:

Permission denied (publickey,password,keyboard-interactive) 
build marked as failed. 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

Dirk Heinrichs

unread,
Jul 27, 2020, 3:54:27 AM7/27/20
to jenkins...@googlegroups.com
Am Montag, den 27.07.2020, 09:37 +0200 schrieb Sakshi Rathore:

thanks , can you please suggest how can i change it to non verifying one?

Click on your agent, select "Configure", look for "Host Key Verification Strategy" and select "Non verifying Verification Strategy".
signature.asc

Sakshi Rathore

unread,
Jul 29, 2020, 2:35:56 AM7/29/20
to jenkins...@googlegroups.com
I tried a lot of things but my ssh connection is not working from jenkins to ssh server.

One more thing my Jenkins and ssh server is hosting on same IP address is there anyway i can resolve this issue?

Sakshi Rathore

unread,
Jul 29, 2020, 2:50:04 AM7/29/20
to jenkins...@googlegroups.com
below is the part of my script where i am doing ssh and it works fine in local.

scp -i $SSHKEY_PATH $CERT_PATH ccp...@10.32.141.35:/home/ccpuser
scp -i $SSHKEY_PATH $KEY_FILE ccp...@10.32.141.35:/home/ccpuser
scp -i $SSHKEY_PATH $CRT_FILE ccp...@10.32.141.35:/home/ccpuser
scp -i $SSHKEY_PATH ./check.sh ccp...@10.32.141.35:/home/ccpuser
scp -i $SSHKEY_PATH ./old_server.sh ccp...@10.32.141.35:/home/ccpuser
scp -i $SSHKEY_PATH ./cert_status1.sh ccp...@10.32.141.35:/home/ccpuser
scp -i $SSHKEY_PATH ./new_server_cert.sh ccp...@10.32.141.35:/home/ccpuser

sed -i -e 's/\r$//' ./check.sh
sed -i -e 's/\r$//' ./old_server.sh
sed -i -e 's/\r$//'  ./cert_status1.sh
sed -i -e 's/\r$//' ./old_server.sh
sed -i -e 's/\r$//' ./new_server_cert.sh


echo "check1"

ssh -i $SSHKEY_PATH ccp...@10.32.141.35 /bin/bash <<EOF

this ssh key belongs to server login

when i try to execute this using jenkins build:

Warning: Identity file /c/Users/D35N/Downloads/GitHubProjeckt/Automation/GitHubProjeckt/newharbortestkey not accessible: No such file or directory.
Host key verification failed.
lost connection
I have generated ssh key in ssh server for jenkins and put public key into home/.ssh/authorized_keys location  and private key for ssh setup in jenkins but i am not able to connect to the ssh server
i also tried simple ssh to the server in build step but it is not working. Please advise where I am wrong.

jeremy mordkoff

unread,
Jul 29, 2020, 9:46:41 AM7/29/20
to Jenkins Users
There are two SSH keys involved when establishing a session 

The one you are setting here is the key used ti identify the client to the server (host). There is also the key that the server (host) sends down to the client. You can see this the first time you ssh to a host and it asks you if you want to accept the key. Once you do accept it, it is stored in .ssh/known_hosts and subsequent connections are verified automatically. 

You have two choices. Disable host key verification or add the host key manually to jenkins' known_hosts file.

to disable host key checking, add this to your .ssh/config 
StrictHostKeyChecking no
This can also be done on the commandline .. something like 
-o StrictHostKeyChecking=no

or you can pre-create the known_hosts file. One way would be to delete it, ssh to the host manually and then examine the known_hosts file. There should be one line in it something like this
jenkins7,10.64.10.74 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNiUivaQ4skdl0sc0A/a0aFxA1p/Sd/6AcYpZcjC0UA9YaO5ADJT+Ercb9fHrcuQdiEOMi36LVNdS5TY1EeFYzs=
copy that into jenkins' known_hosts file 
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins...@googlegroups.com.

sakshira...@gmail.com

unread,
Jul 31, 2020, 4:09:19 AM7/31/20
to Jenkins Users

thanks very much for all the advice , i tried in the given way but while conencting to the server to the client using manual ssh 

i get below error everytime:

ccpuser@harbortest-master-gro-a7c3cedfab:~$ ssh ccp...@10.32.141.35
The authenticity of host '10.32.141.35 (10.32.141.35)' can't be established.
ECDSA key fingerprint is SHA256:bSeIr7zG7863687fvTDsZrG3Kc77pUXMLZKwu4YMRfrY.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.32.141.35' (ECDSA) to the list of known hosts.
ccp...@10.32.141.35: Permission denied (publickey,keyboard-interactive). 
respective keys have been already added , public key to /home/.ssh/authorized_key 
ialso tried to add private key identity as part of troubleshoot

ccpuser@harbortest-master-gro-a7c3cedfab:~/.ssh$ ssh-add ~/.ssh/id_rsa
Identity added: /home/ccpuser/.ssh/id_rsa (/home/ccpuser/.ssh/id_rsa)


i have also tried to disable host key checking in etc/ssh/ssh_config file
StrictHostKeyChecking no

if i try to avoid permission denied error google suggestion leads me to password authentication and i want to do ssh login 

I have tried everything to get it owkr adding ssh key authentication tojenkins server in credentials section and ssh-sites but nothing seems working for me  , i am not able to conenct to jenkins client to my remote server. 


my humble request to suggest a way forward or any approach so i can proceed further. It will be great help.

jeremy mordkoff

unread,
Jul 31, 2020, 9:18:01 AM7/31/20
to Jenkins Users
ssh is picky about permissions. 

make sure the .ssh directory itself has perms 770 and any files in that folder have perms 660 and that they are all owned by the correct user on both the client and server. 

try adding -o identitiesOnly=yes on the ssh client command line. There is a server config that limits the number of failed connects. 

try running the client in verbose mode (-v or -vv) -- every now and then a message shows up there with a hint. 

if you're still stuck, set the server logging to debug and check there. Always keep one ssh session open as root to the server when changing the ssh server config file (usually /etc/ssh/sshd_config)

Sakshi Rathore

unread,
Jul 31, 2020, 9:52:41 AM7/31/20
to jenkins...@googlegroups.com
 thanks a lot, i just solved permission denied issue and able to ssh from client to host
1. 
jenkins@harbortest-master-gro-a7c3cedfab:~/.ssh$ ssh ccpuser@harbortest-master-gro-a7c3cedfab
Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 4.15.0-64-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://www.microk8s.io/ has docs and details.
This system has been minimized by removing packages and content that are
not required on a system that users do not log into.

To restore this content, you can run the 'unminimize' command.
Last login: Fri Jul 31 13:31:29 2020 from 10.36.174.37
ccpuser@harbortest-master-gro-a7c3cedfab:~$ cd .ssh/

 2. But in jenkins console i am still getting cant connect to the server :

image.png


image.png

and still from my local system to host i cant ssh directly:

sakshi_rathore@MCN234 MINGW64 ~/.ssh (master)
$ ssh ccp...@10.32.141.35
ccp...@10.32.141.35: Permission denied (publickey,keyboard-interactive).

Could you please also suggest for this. 

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/63ed9be4-f2d4-4d32-9157-c90e18d2420fo%40googlegroups.com.

Sakshi Rathore

unread,
Aug 3, 2020, 2:14:59 AM8/3/20
to jenkins...@googlegroups.com
could you please help here? 

jeremy mordkoff

unread,
Aug 3, 2020, 9:05:21 AM8/3/20
to Jenkins Users
The same solutions offered for client to host should apply for local system to host. Did you add the local system's public ssh key to the host's authorized key file? 

I have no clue what a "crumb" is

Sakshi Rathore

unread,
Aug 4, 2020, 11:03:28 AM8/4/20
to jenkins...@googlegroups.com
yes thanks, it worked but after successful installation and execution of script  i am getting status as Build failure: Could you please advise here.

Below are the logs:
Started by user Sakshi Rathore
Running as SYSTEM
Building in workspace /var/lib/jenkins/workspace/test9
No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/sakshirathorebgw/GitHubProjeckt.git
 > git init /var/lib/jenkins/workspace/test9 # timeout=10
Fetching upstream changes from https://github.com/sakshirathorebgw/GitHubProjeckt.git
 > git --version # timeout=10
 > git fetch --tags --progress -- https://github.com/sakshirathorebgw/GitHubProjeckt.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/sakshirathorebgw/GitHubProjeckt.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/sakshirathorebgw/GitHubProjeckt.git # timeout=10
Fetching upstream changes from https://github.com/sakshirathorebgw/GitHubProjeckt.git
 > git fetch --tags --progress -- https://github.com/sakshirathorebgw/GitHubProjeckt.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 5dd43192426415f540b687697f6ef436acf60600 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 5dd43192426415f540b687697f6ef436acf60600 # timeout=10
Commit message: "added from server"
First time build. Skipping changelog.
[test9] $ /bin/sh -xe /tmp/jenkins4883353382832852402.sh
+ ./piecebypiece.sh
./test2-harbor.pfx is certpath
test2-harbor is basename
test2-harbor is new secret name for harbor
this is password  start01
./test2-harbor.key key file generated
./test2-harbor.crt crt file generated
key filename is test2-harbor.key
crt filename is test2-harbor.crt
address for certificate is : test2-harbor.tank.local
core: core.harbor.domain
core: test2-harbor.tank.local
notary: notary.harbor.domain
notary: test2-harbor.tank.local
secretName:
secretName: test2-harbor
check1
/home/ccpuser
harbortest-master-gro-a7c3cedfab
ccp_kibana_ingress_setup.sh
cert_status1.sh
check.sh
docker
harbor
harbor_bkp
jenkins-cli.jar
jenkins-namespace.yaml
jenkins-volume.yaml
kibana_ingress.yaml
new_server_cert.sh
newharbortestkey
old_server.sh
piecebypiece.sh
test2-harbor.crt
test2-harbor.key
test2-harbor.pfx
test2-harbor123.crt
test2-harbor123.key
test2-harbor123.pfx
test2-harbor12345.crt
test2-harbor12345.key
test2-harbor12345.pfx
test2-harbor54321.crt
test2-harbor54321.key
test2-harbor54321.pfx
value.yaml
value1.yaml
further run
execute check.sh now
namespace is harbor
 harbor is NOT NULL
./test2-harbor54321.crt
test2-harbor54321.crt
 
The certificate of
   
expires on
   Thu Jun  3 07:54:16 UTC 2021
which is in 302 days from now!
 
WARNING - Expiration date is near!
 
edit properties file and run the job to install the new cert
mv: cannot move 'harbor' to 'harbor_bkp/harbor': Directory not empty
namespace "harbor" deleted
"harbor" has been added to your repositories
total 232
drwxr-xr-x 15 ccpuser ccpadmin  4096 Jul 30 11:00 templates
drwxr-xr-x  2 ccpuser ccpadmin  4096 Jul 30 11:00 conf
drwxr-xr-x  2 ccpuser ccpadmin  4096 Jul 30 11:00 cert
-rw-r--r--  1 ccpuser ccpadmin 24523 Aug  4 14:58 values.yaml
-rw-r--r--  1 ccpuser ccpadmin   561 Aug  4 14:58 Chart.yaml
-rw-r--r--  1 ccpuser ccpadmin 83889 Aug  4 14:58 README.md
-rw-r--r--  1 ccpuser ccpadmin 11357 Aug  4 14:58 LICENSE
-rw-r--r--  1 ccpuser ccpadmin  5418 Aug  4 14:58 test2-harbor54321.pfx
-rw-r--r--  1 ccpuser ccpadmin  7382 Aug  4 14:58 test2-harbor54321.key
-rw-r--r--  1 ccpuser ccpadmin  5465 Aug  4 14:58 test2-harbor54321.crt
-rw-r--r--  1 ccpuser ccpadmin  5418 Aug  4 14:58 test2-harbor12345.pfx
-rw-r--r--  1 ccpuser ccpadmin  7382 Aug  4 14:58 test2-harbor12345.key
-rw-r--r--  1 ccpuser ccpadmin  5465 Aug  4 14:58 test2-harbor12345.crt
-rw-r--r--  1 ccpuser ccpadmin  5418 Aug  4 14:58 test2-harbor123.pfx
-rw-r--r--  1 ccpuser ccpadmin  7382 Aug  4 14:58 test2-harbor123.key
-rw-r--r--  1 ccpuser ccpadmin  5465 Aug  4 14:58 test2-harbor123.crt
-rw-r--r--  1 ccpuser ccpadmin  5418 Aug  4 14:58 test2-harbor.pfx
-rw-r--r--  1 ccpuser ccpadmin  7382 Aug  4 14:58 test2-harbor.key
-rw-r--r--  1 ccpuser ccpadmin  5465 Aug  4 14:58 test2-harbor.crt
namespace/harbor created
./test2-harbor54321.pfx is certpath
test2-harbor54321 is basename
test2-harbor54321 is new secret name for harbor
./test2-harbor54321.key key file generated
./test2-harbor54321.crt crt file generated
key filename is test2-harbor54321.key
crt filename is test2-harbor54321.crt
core: test2-harbor.tank.local
notary: test2-harbor.tank.local
secretName: test2-harbor54321
values.yaml is updated
secret/test2-harbor54321 created
NAME: harbor
LAST DEPLOYED: Tue Aug  4 14:58:39 2020
NAMESPACE: harbor
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Please wait for several minutes for Harbor deployment to complete.
Then you should be able to visit the Harbor portal at https://core.harbor.domain
For more details, please visit https://github.com/goharbor/harbor
Harbor certificate isntallation done
Mail notification sent
 
Build step 'Execute shell' marked build as failure
Finished: FAILURE
 

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ec42ce3b-6d97-4415-9a7a-ab7b06e78377o%40googlegroups.com.

jeremy mordkoff

unread,
Aug 4, 2020, 12:19:11 PM8/4/20
to Jenkins Users
You should start a new thread 

I cannot tell what is happening from this. You should also post the code 
Reply all
Reply to author
Forward
0 new messages