No such file or directory error when building in Jenkins

[zhang...@gmail.com]

Hello guys, I'm using fabric8-jenkins:2.2.288 and met a problem. When I created a microservice app and waited for jenkins building, I got errors as follows:

NOTE: running pipelines for the first time will take longer as build and base docker images are pulled onto the node
[Pipeline] withPod
[Pipeline] {
[Pipeline] stage (Canary Release)
Entering stage Canary Release
Proceeding
[Pipeline] sh
[zzz] Running shell script
sh -c echo $$ > '/var/jenkins_home/workspace/zzz/.5a95e017/pid'; jsc=durable-f49fd2510e6ae54cff79b789f16df677; JENKINS_SERVER_COOKIE=$jsc '/var/jenkins_home/workspace/zzz/.5a95e017/script.sh' > '/var/jenkins_home/workspace/zzz/.5a95e017/jenkins-log.txt' 2>&1; echo $? > '/var/jenkins_home/workspace/zzz/.5a95e017/jenkins-result.txt' 
exit
 [?1034hsh-4.2# sh -c echo $$ > '/var/jenkins_home/workspace/zzz/.5a95e017/pid'; jsc=dur 
able-f49fd2510e6ae54cff79b789f16df677; JENKINS_SERVER_COOKIE=$jsc '/var/jenkins_ 
home/workspace/zzz/.5a95e017/script.sh' > '/var/jenkins_home/workspace/zzz/.5a95 
e017/jenkins-log.txt' 2>&1; echo $? > '/var/jenkins_home/workspace/zzz/.5a95e017 
/jenkins-result.txt' 
sh: /var/jenkins_home/workspace/zzz/.5a95e017/pid: No such file or directory
sh: /var/jenkins_home/workspace/zzz/.5a95e017/jenkins-log.txt: No such file or directory
sh: /var/jenkins_home/workspace/zzz/.5a95e017/jenkins-result.txt: No such file or directory
sh-4.2# exit


And the Jenkinsfile was generated by fabric8 automatically.

AFAK, the code in `kubernetes.pod(...).inside{}` block will be executed in maven-builder pod (which do start properly), so it seems that the No-such-file error occurs in the maven-builder pod?

Could you please help me?

Thank you very much.

[James Rawlings]

Are you running on GKE?  I wonder if you've hit this https://github.com/fabric8io/fabric8/issues/6505

If not there's a FAQ entry that might also be worth looking at  https://github.com/jenkinsci/kubernetes-pipeline-plugin/blob/master/kubernetes-steps/readme.md#technical-notes

FWIW we're moving away from the use of a shared host path Jenkins workspace in the next release.  We're hoping to make available very soon, maybe even later today.  This should avoid the error all together.

James.

--
James Rawlings
Engineering
Red Hat, Inc.
Blog: https://medium.com/@jdrawlings
Twitter: @jdrawlings

https://fabric8.io/
https://blog.fabric8.io/

--
You received this message because you are subscribed to the Google Groups "fabric8" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabric8+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[zhang...@gmail.com]

I'm using AWS, not GKE, but they are almost same, I think. I do be going to upgrade the version of fabric8 to latest.

In past a few weeks, I'm trying to build up our ci platform based on fabric8 and I’m almost there. Thank you for your team's excellent work!

在 2016年11月7日星期一 UTC+8下午5:36:34，James Rawlings写道：

[James Rawlings]

That sounds great!

You might want to hold off upgrading until this new release is available as we've made a lot of improvements especially around our use of Jenkins.  We've upgraded to a Jenkins2 base image, updated all plugins and included Blue Ocean.

Hopefully we'll be sending an update later today when the new release is available.

[zhang...@gmail.com]

I'm really looking forward to seeing the improvements and hope I can share more actual production experience with you soon.

在 2016年11月7日星期一 UTC+8下午5:48:59，James Rawlings写道：