[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title
trejkaz commented on JENKINS-46831
Re: Not able to use a normal agent on stage when agent docker is declared globally
We hit this one today, but the issue linked in the description (JENKINS-33510) is marked as resolved. I assume it's now a different issue? I get the same error as above ("No such container: --").
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title Andrew Bayer commented on JENKINS-46831 Re: Not able to use a normal agent on stage when agent docker is declared globally Martin Sander - Yeah, it's the same issue, basically. What I'd recommend is that you do agent any at the top level, then docker agents for each stage with reuseNode true - should get you the behavior you're looking for. 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.
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-46831 Not able to use a normal agent on stage when agent docker is declared globally Change By: Andrew Bayer Priority: Critical Major 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.
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title
Martin Sander edited a comment on JENKINS-46831
Re: Not able to use a normal agent on stage when agent docker is declared globally
[~abayer]:I have a problem that might be this one or another issue:{code}pipeline {agent {docker {image 'microsoft/azure-cli:2.0.28'args '-u 0:0'}}options { timestamps() }stages {stage('azure-cli') {steps {sh 'az --version'}}stage('dotnet') {agent {docker {image 'microsoft/dotnet:2.0-runtime-stretch'args '-u 0:0'}}steps {sh 'ls /usr/share/dotnet'}}}}{code} ` {{ stage('azure-cli') ` }} works, ` {{ stage('dotnet') ` }} fails with: ` {{ Error: No such container: c0ffeec0de ` }} (which is actually the container that runs ' {{ microsoft/azure-cli:2.0.28 ' }} , but is running on a completely different node).Using ` {{ reuseNode ` }} for the dotnet container docker agent leads to a different error: Jenkins tries to start the second docker container *from within* the first one.Is this the same issue as this or a new one? Plugin version 1.2.7.
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.
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title
Martin Sander commented on JENKINS-46831
Re: Not able to use a normal agent on stage when agent docker is declared globally
Andrew Bayer: I have a problem that might be this one or another issue:
pipeline {
agent {
docker {
image 'microsoft/azure-cli:2.0.28'
args '-u 0:0'
}
}
options { timestamps() }
stages {
stage('azure-cli') {
steps {
sh 'az --version'
}
}
stage('dotnet') {
agent {
docker {
image 'microsoft/dotnet:2.0-runtime-stretch'
args '-u 0:0'
}
}
steps {
sh 'ls /usr/share/dotnet'
}
}
}
}
`stage('azure-cli')` works, `stage('dotnet')` fails with: `Error: No such container: c0ffeec0de` (which is actually the container that runs 'microsoft/azure-cli:2.0.28', but is running on a completely different node). Using `reuseNode` for the dotnet container leads to a different error: Jenkins tries to start the second docker container from within the first one. Is this the same issue as this or a new one? Plugin version 1.2.7.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to t
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title wknapik wknapik commented on JENKINS-46831 Re: Not able to use a normal agent on stage when agent docker is declared globally Andrew Bayer I tried doing that (as described in JENKINS-47103), but it didn't work back then. Has something changed ? 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.
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title wknapik wknapik commented on JENKINS-46831 Re: Not able to use a normal agent on stage when agent docker is declared globally Andrew Bayer thanks for the response. I don't really care where/how the agents are specified - I just need to run all the stages in docker containers. Are you saying that it's possible to run parallel stages in containers (on multiple slaves at the same time), if I change how the agents are specified in the Jenkinsfile ? 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.
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title Andrew Bayer commented on JENKINS-46831 Re: Not able to use a normal agent on stage when agent docker is declared globally It's due to an inherent aspect of the Docker Pipeline plugin - we're working on a successor to Docker Pipeline over in JENKINS-48050, but I don't have a specific timeframe. For now, you just have to not use a top-level docker agent if you want to run stages, parallel or otherwise, on a different agent. 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.
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title wknapik wknapik commented on JENKINS-46831 Re: Not able to use a normal agent on stage when agent docker is declared globally Andrew Bayer ping? 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.
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title wknapik wknapik commented on JENKINS-46831 Re: Not able to use a normal agent on stage when agent docker is declared globally This issue, marked as critical, has been open for 6 months with no apparent progress. Making it impossible for users to run stages in parallel goes against the core purpose of this software, which is providing rapid feedback. It's as if `ls' stopped listing some files and for half a year no one got around to fixing it. Andrew Bayer - can you please comment ? When can we expect this to be resolved ? How can users, who have built their pipelines using docker-based agents, run stages in parallel ? Is there some workaround/hack that can be used now ? 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.
[JIRA] (JENKINS-46831) Not able to use a normal agent on stage when agent docker is declared globally
Title: Message Title wknapik wknapik commented on JENKINS-46831 Re: Not able to use a normal agent on stage when agent docker is declared globally What's the state of this issue ? When will it be possible to run stages in parallel with docker agents ? 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.
