[JIRA] (JENKINS-51488) ZIp step on jenkins slave duplicates full pah and fails
Title: Message Title Nico Navarrete created an issue Jenkins / JENKINS-51488 ZIp step on jenkins slave duplicates full pah and fails Issue Type: Bug Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2018-05-22 16:30 Environment: Jenkins (docker) 2.107.3 docker ssh slave pipeline-utility-steps 2.1.0 Priority: Major Reporter: Nico Navarrete Building a zip works when running in "master" but when running in docker slave. it duplicates full path and fails // fails //def tmp = pwd tmp:true // works on slave def tmp = './@tmp' zip zipFile:"$tmp/file.zip" , archive:true, dir:"$dest/package/dist" java.nio.file.NoSuchFileException: /home/jenkins/workspace/Integration/accesoproveedor/home/jenkins/workspace/Integration/accesoproveedor@tmp/accesoproveedor-2017.0.4-abe2418.zip at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileAttributeViews$Posix.readAttributes(UnixFileAttributeViews.java:218) at sun.nio.fs.UnixFileAttributeViews$Posix.readAttributes(UnixFileAttributeViews.java:131) at
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title
Nico Navarrete edited a comment on JENKINS-38018
Re: withDockerRegistry fails to authenticate with DockerHub
Just to comment, probably, as commented , there are multiple issues here, and first of all thank you all or the work and efforts done to make jenkins works with docker. In my case I don't this think it's an environment (only) problem, it works perfectly with plugin version 1.15.1 and it doesn't work at all with plugin version 1.16. What I'm doing is a docker development cycle pipeline, that builds dockers inside a jenkins-ssh-slave (dockerized) running from a dockerized jenkins master (2.107.3). This pipeline builds the docker images in the slave, connecting to the remote dockerd, and push the image to the private docker registry (nexus). Well in this scenario, the `docker` command should take the DOCKER_HOST from the environment and authenticate to the docker private registry. With the update this stopped to work {code:java} // run from base dir for folder builds and from tmp for url builds dir ("$runPwd") { echo "Build with server ${env.DOCKER_HOST} and registry ${env.CP_DOCKER_RELEASE}" docker.withServer(env.DOCKER_HOST) { docker.withRegistry(env.CP_DOCKER_RELEASE,env.DOCKER_CREDENTIALS ){ echo "Execute docker build -t $name:$version $params" sh "docker build -t $name:$version $params"// def image = docker.build ("$name:$version", params) } } }{code}After I downgrade version to 1.15.1 this works again with no other change. If it's required a change in configuration or parameters I suppose it should be documented or have sensitive defaults to act as previous versions and continue to work as expected or be "adapted" with the new/changed configuration/parameters. I f you need any help on variable values or Dockerfile's or conatiner o whatever may help don't hesitate to ask, I'll give whatever may help. Thanks again,Nico
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51397) docker login being called without server-related environment variables
Title: Message Title
Nico Navarrete commented on JENKINS-51397
Re: docker login being called without server-related environment variables
This works with
docker-plugin
1.1.4
docker-workflow
1.15.1
but not with
docker-plugin
1.1.4
docker-workflow
1.6
// run from base dir for folder builds and from tmp for url builds
dir ("$runPwd") {
echo "Build with server ${env.DOCKER_HOST} and registry ${env.CP_DOCKER_RELEASE}"
docker.withServer(env.DOCKER_HOST) {
docker.withRegistry(env.CP_DOCKER_RELEASE,env.DOCKER_CREDENTIALS ){
echo "Execute docker build -t $name:$version $params"
sh "docker build -t $name:$version $params"
// def image = docker.build ("$name:$version", params)
}
}
}
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title
Nico Navarrete commented on JENKINS-38018
Re: withDockerRegistry fails to authenticate with DockerHub
Just to comment, probably, as commented , there are multiple issues here, and first of all thank you all or the work and efforts done to make jenkins works with docker. In my case I don't this it's an environment problem, it works perfectly with plugin version 1.15.1 and it doesn't work at all with plugin version 1.16. What I'm doing is a docker development cycle pipeline, that builds dockers inside a jenkins-ssh-slave (dockerized) running from a dockerized jenkins master (2.107.3). This pipeline builds the docker images in the slave, connecting to the remote dockerd, and push the image to the private docker registry (nexus). Well in this scenario, the `docker` command should take the DOCKER_HOST from the environment and authenticate to the docker private registry. With the update this stopped to work
// run from base dir for folder builds and from tmp for url builds
dir ("$runPwd") {
echo "Build with server ${env.DOCKER_HOST} and registry ${env.CP_DOCKER_RELEASE}"
docker.withServer(env.DOCKER_HOST) {
docker.withRegistry(env.CP_DOCKER_RELEASE,env.DOCKER_CREDENTIALS ){
echo "Execute docker build -t $name:$version $params"
sh "docker build -t $name:$version $params"
// def image = docker.build ("$name:$version", params)
}
}
}
After I downgrade version to 1.15.1 this works again with no other change. If it's required a change in configuration or parameters I suppose it should be documented or have sensitive defaults to act as previous versions and continue to work as expected or be "adapted" with the new/changed configuration/parameters. I f you need any help on variable values or Dockerfile's or conatiner o whatever may help don't hesitate to ask, I'll give whatever may help. Thanks again, Nico
Add Comment
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title
Nico Navarrete commented on JENKINS-38018
Re: withDockerRegistry fails to authenticate with DockerHub
1.16 break builds, with 1.15.1 this was working but not with 1.16
docker.withServer(host) {
docker.withRegistry(repo, credentialsId ){
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
