[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Ad commented on JENKINS-49278 Re: cat command in docker agents not detected correctly For specialized use cases like this you should not use withDockerContainer. Just run whatever docker commands you need directly from a sh (or indirectly via some script). We are revisiting our use of docker agents in our CI pipeline. Jesse Glick we are considering following your advice above, thus removing the docker agents and instead run `docker` commands in `sh` steps directly on the master. Yet, our current setup is that we have a stage with many steps running on the agent (having the different steps showing nicely in Jenkins UI). How could we get the same result by executing the docker command directly? (i.e. executing discrete Jenkins `steps` in the same docker container, without restarting the container since it would loose its state). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4506.1570702621287%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Ad edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
Well, we are using the Docker agent syntax:{code:java}agent { docker { image 'ag/ubuntu-conan' args '''-v $DOCKERCONFIG_FOLDER/ag/ubuntu-conan.env:/dockerconfig.env } }stage('Use the tool') { steps {sh 'conan install whatever' }}{code}Is not that the exact intended "tool-only" use case you were mentioning above? If not, what is the expected use-case for these kind of agents then?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4210.1564502582311%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Ad commented on JENKINS-49278
Re: cat command in docker agents not detected correctly
Well, we are using the Docker agent syntax:
agent {
docker {
image 'ag/ubuntu-conan'
args '''-v $DOCKERCONFIG_FOLDER/ag/ubuntu-conan.env:/dockerconfig.env
}
}
stage('Use the tool') {
steps {
sh 'conan install whatever'
}
}
Is not that the exact intended "tool-only" use case you were mentioning above? If not, what is the expected use-case for these kind of agents then?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4208.1564502582248%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Ad commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Jesse Glick It is very undestandable that `withDockerContainer` is expected for tool-only images, and as a matter of fact that is exactly what our organization uses it for. Yet, such tool-only container can very easily have an ` ENTRYPOINT` which needs to completely run before the actual sh steps are executed. In our case, we have a Docker container that we use as a Conan (https://conan.io/) tool. Yet, this container has a entrypoint which runs the usual `docker-entrypoint.sh` that is notably responsible for setting up the different remote repositories and log-in to use them. Yet, we observe spurious failure because of the race condition: sometimes the entrypoint had time to complete before the sh steps are executed, sometimes it did not. The problem is clearly addressed by the Docker guidelines: `ENTRYPOINT` is for the container steps that should not be replaced by the client, and `CMD` is exactly for client override. It does not seem reasonable for Docker to execute commands while racing with `ENTRYPOINT`, and it is becoming such a major problem for us that we will have to walk away from this solution if the situation remains as it currently is. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.4105.1564501801974%40Atlassian.JIRA.
[JIRA] (JENKINS-41225) durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd.
Title: Message Title Ad commented on JENKINS-41225 Re: durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd. This seems to be due to the escape(envVars) call. Quick-fix proposed in PR: https://github.com/jenkinsci/durable-task-plugin/pull/36 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-41225) durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd.
Title: Message Title Ad updated an issue Jenkins / JENKINS-41225 durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd. Change By: Ad Environment: Jenkins 2. 32.1 (also tried on 2. 19.1 ), running on OS XWindows remote: Windows 10 x64, Cygwin 2.6.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-41225) durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd.
Title: Message Title Ad created an issue Jenkins / JENKINS-41225 durable-task 1.13 is failing with remote Windows accessed through Cygwin sshd. Issue Type: Bug Assignee: Jesse Glick Components: durable-task-plugin Created: 2017/Jan/19 5:42 PM Environment: Jenkins 2.19.1 running on OS X Windows remote: Windows 10 x64, Cygwin 2.6.1 Priority: Major Reporter: Ad The previous version of durable-task plugin as failing at the 'sh' pipeline step, with error: sh: C:[...]\durable-a739272f\script.sh: command not found The fork from blatinville - https://github.com/blatinville/durable-task-plugin - adresses this issue, as this version is able to actually run the 'sh' tasks (succeeding for some; but mysteriously fails returning -1 for some other, when there is actually no failure in the commands). The 1.13 release, which merges the PR from the above fork, fails on my setup with the following error: nohup: failed to run command 'sh': No such file or directory As it stands, I am not aware of any workarounds to actually run bash scripts on Windows remotes connected through Cygwin's sshd.
