[JIRA] (JENKINS-42184) Unable to run pods in parallel due to template nesting

1 view
Skip to first unread message

lionelve@gmail.com (JIRA)

unread,
Feb 20, 2017, 12:56:01 AM2/20/17
to jenkinsc...@googlegroups.com
Lionel Orellana updated an issue
 
Jenkins / Bug JENKINS-42184
Unable to run pods in parallel due to template nesting
Change By: Lionel Orellana
Summary: All pod templates Unable to run pods in the pipeline are assumed parallel due to be nested   template nesting
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

4.silent.art@gmail.com (JIRA)

unread,
Mar 12, 2018, 4:41:02 AM3/12/18
to jenkinsc...@googlegroups.com
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

patrick.harboeck@tngtech.com (JIRA)

unread,
Jun 7, 2018, 12:19:04 PM6/7/18
to jenkinsc...@googlegroups.com

This is still a big issue for me when running with plugin version 1.7.1.

The workaround from Alex Varju still works, but is not 100% reliable when running many pods in parallel, which can lead to annoying and subtle bugs, because the pods template specs are merged randomly. Another workaround we have to do for this is to use some sleep calls and ugly locking to try to avoid this race-condition.

Carlos Sanchez Is there any idea on the root cause of this bug and how it could be fixed in the plugin?

jenkins-ci@carlossanchez.eu (JIRA)

unread,
Jun 7, 2018, 12:23:02 PM6/7/18
to jenkinsc...@googlegroups.com

the very first thing that would help is a test case like https://github.com/jenkinsci/kubernetes-plugin/pull/339/files
If you can put up one that shows the error in CI then it will be a lot easier to fix

sebglon@gmail.com (JIRA)

unread,
Jun 18, 2018, 9:44:02 AM6/18/18
to jenkinsc...@googlegroups.com

I have this error on parallel stage wher each one create a specific podTemplate.

And the workaround above not work for me. 

jglick@cloudbees.com (JIRA)

unread,
Jul 16, 2019, 3:43:22 PM7/16/19
to jenkinsc...@googlegroups.com
Jesse Glick assigned an issue to Unassigned
 
Change By: Jesse Glick
Assignee: Carlos Sanchez
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages