Im getting a series of 'def' errors in the jenkins pipeline.
I have defined all the variables with def, updated the plugins with latest version, still im getting a whole bunch of warnings like these. 
I have no fields like the ones which are stated below.

[Pipeline] Start of PipelineDid you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Closure_0_1188384533{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Agent_1_2121869484{} (to a value of type {}model{}Agent_1_2121869484{}) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Variable_2_1006086506{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Stage_3_1336556875{} (to a value of type {}model{}Stage_3_1336556875{}) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Variable_4_1006086568{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Variable_5_1006086599{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Variable_6_1006086630{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Variable_7_1006086661{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}listExpression_9_977338109{} (to a value of type {}model{}listExpression_9_977338109{}) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Parallel_10_295940307{} (to a value of type {}model{}Parallel_10_295940307{}) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Variable_11_1006086785{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Variable_12_1006086816{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Closure_13_1188384130{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Closure_14_1188384099{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Closure_15_1188384068{} (to a value of type CpsClosure2) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named {}model{}Environment_16_1418187955{} (to a value of type {}model{}Environment_16_1418187955{}) which could lead to memory leaks or other issues.