reuseNode in docker-plugin

61 views
Skip to first unread message

Kirk Fitzsimons

unread,
Jan 7, 2025, 10:11:51 AMJan 7
to Jenkins Developers
Hi,

Apologies if this has been asked/answered already, but it there an ability to reuse docker nodes between stages using the docker-plugin, I know you can do it using the docker-pipeline

My use case is I have a parent pipeline job, which triggers child pipeline jobs, each child job ends up cloning the same git repo in a stage, this takes too much time, and I would like to somehow persist the workspace/reuse the node.

If this is not possible with the plugin, is there a workaround, perhaps using a volume for the workspace which can be shared across the jobs?

Kirk

Baptiste Mathus

unread,
Jan 7, 2025, 2:00:39 PMJan 7
to jenkin...@googlegroups.com
Hi, unless this question is about how to contribute such a code change to this plugin, this question should be posted on the jenkins-users ML, not on the dev list here that's designed for the development of Jenkins core and plugins themselves.
Cheers

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/eeedb4c0-d48f-433d-8f21-41f0d1c4f04cn%40googlegroups.com.

Kirk Fitzsimons

unread,
Jan 7, 2025, 2:08:09 PMJan 7
to jenkin...@googlegroups.com

Apologies for posting, i was hoping to see if a developer of the plugin would know, and if a code change was required, i could assist


Jesse Glick

unread,
Jan 8, 2025, 4:12:45 PMJan 8
to jenkin...@googlegroups.com
On Tue, Jan 7, 2025 at 9:08 AM Kirk Fitzsimons <fitzsim...@gmail.com> wrote:

i was hoping to see if a developer of the plugin would know, and if a code change was required


I am not a developer of the plugin, but my offhand opinion is that this is an invalid scenario: either consolidate your build steps into one pipeline using a single `node` step, or if the child pipelines really need to be triggered independently in other circumstances, deal with your problem differently. (Cache upload/download; more efficient Git clone options; etc.)
Reply all
Reply to author
Forward
0 new messages