It seems that the jenkinsParam is holding the output after escaping the special characters.
You are assuming that jenkinsParam = "test\ntest" and however it looks like it stores it as jenkinsParam = "test\\ntest"
See how it behaves if I use echo it these two different cases:
(I have tested this in groovy shell)
jenkinsParam = "test\ntest"
In order to pass masked credentials to your Jenkins job, do the following:
In Jenkins, install Credentials Binding plugin.
In your Jenkins, go to Credentials and click the global domain.
In the left pane, click "Add credential".
From the "Kind" dropdown, choose "Username with password".
Enter the username and password in the reflective boxes and choose an ...
The plugin that you are looking for is: https://github.com/jenkinsci/github-plugin.
You need to go in Manage Jenkins > Global Configuration to find the GitHub plugin configuration (according the documentation).
The error shows that you are using AWS ECR credentials to login to dockerhub which will not work. Dockerhub is a different registry(both public and private), however ECR is private registry only.
For pulling public images from dockerhub there is no need to login to dockerhub. You can simply use docker pull command and it will pull an image from dockerhub ...
The docker login failed.
Error response from daemon: Get https://https/v2/: dial tcp: lookup https: Temporary failure in name resolution
The url is invalid.
docker login -u AWS -p ******** https:/123456790.dkr.ecr.us-east-1.amazonaws.com
docker login -u AWS -p ******** 123456790.dkr.ecr.us-east-1.amazonaws.com
Do you run selenium as a separate process?
I had the same issue if you are not running selenium in the background.
Try java -jar selenium-XX.XX.jar in terminal.
After that run pabot or robot command to run the tests.
You can crate app through the Automator and use the same approach you describe to call it from the CI. That is what I end up using.
Attempting to run your validation on branches, before being integrated into the trunk won't get you very far. The reason is that fundamentally such validations are performed in isolation, most often they will not actually reflect the trunk picture after the branch is merged.
The only case in which the branch validation is, well, valid, is if no other ...
Log on on the master where you have the issue: ssh jenkins-machine
Shutdown the jenkins master (take care that nothing is running) sudo service jenkins stop
Find all erroneous directories: find /var/lib/jenkins/jobs -type d \( -name "last*Build" -o -name "lastStable" -o -name "lastSuccessful" \)
Review the list of erroneous directories