Problem description

When there are SEVERAL podTemplates defined in a pipeline and nothing is specified in the inheritFrom section of the plugin, the algorithm used will make each podTemplate to inherit from the podTemplates which are already running.

To reproduce this problem, you just need to create a pipeline with at very least 2 podTemplates running in series or parallel, and then in the Jenkins logs you could see that the plugin creates an inherit of the second pod respect the first one.

When you reproduce the problem, if you go to the config.xml of the node created in Jenkins, you will see that this inherit dependency is created as well.

The plugin does not seem to create a graph where you could correctly define the inheritance and just assume there is an inheritance.

Business impact

Users which have pod memory limitations will not be able to use this plugin correctly. As there is an inheritance, the parent pod will add the memory usage of the rest of the child pods. Then, you could easily go out of the memory of the pod limitation on the cluster.