-
Bug
-
Resolution: Unresolved
-
Major
-
None
Plugin takes wrong build for validness of constraints evaluation. It always takes the last build for the pipeline instead the one that actually called plugin. The code issue is here builds.get(0) so if the build n called the plugin and there in build n+1 in pipeline the plugin will use build n+1 context to perform validations which results in errors like
Performance Plugin: Could't find a report specified in the performance constraints! Report: xxx.jlt