Which might indicate that it can't launch because it lack memory to fit the pod in. The maven-builder pod status claims that it is exiting the pods execution by the exitcode of "137": Sh: /home/jenkins/workspace/workspace/springboot/.53a00905/script.sh: Permission denied Ome/jenkins/workspace/workspace/springboot/.53a00905/jenkins-result.txt' home/jenkins/workspace/workspace/springboot/.53a00905/script.sh' > '/home/jenki Sh -c echo $$ > '/home/jenkins/workspace/workspace/springboot/.53a00905/pid' jsc=durable-8457be19abea4d08ebd419f363d8212c JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/workspace/springboot/.53a00905/script.sh' > '/home/jenkins/workspace/workspace/springboot/.53a00905/jenkins-log.txt' 2>&1 echo $? > '/home/jenkins/workspace/workspace/springboot/.53a00905/jenkins-result.txt' The jenkins-jnlp slave can also as instructed by the workflow script launch the "fabric8io/maven-builder" but the pod launched with the "fabric8/maven-builder" docker image fails quite fast complaining about a lack of permissions to run the jenkins injects script.sh: I can launch the jenkins-jnlp slave and it can connect to back to the fabric8 jenkins instance also running on the OpenShift environment. Sh "chmod +x docker-compose.I am trying to get the fabric8 jenkins-pipeline-library to work on an OpenShift Origin version 1.2.0 installation. ScmSteps.cloneRepository(gitURL, env.BRANCH_NAME, credentialsId) Log.outputBanner("Checking out from the SCM") I have checked the ownership of the file, and also tried changing the permissions, but this hasn't worked. I'm getting a "permission denied" error for the file on the Jenkins agent (not the remote host). I have set up SSH to the remote server, and I'm able to connect to it. I'm trying to copy a file (created during SCM Checkout) from my Jenkins agent to a remote server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |