The Deployment Environment Parser incorrectly assumes the environment exported object is created by the Jenkins counterpart add-on
Description
Environment
None
Activity
Show:
Mark Rekveld January 2, 2020 at 10:22 AM
Yeah, I could have thought about this since Jenkins doesn't have a structured API but lets every plugin define its own model and can thus cause overlap.
I have addressed this and am working towards a bugfix release.
Kalle Niemitalo December 30, 2019 at 12:54 PM
I got almost identical stack traces, although EnvInject is not installed here. The JSON API of Jenkins shows the following object in the "actions" array, which apparently confused the integration:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Unassigned
UnassignedReporter
Mark RekveldComponents
Fix versions
Affects versions
Priority
MajorZoom
Open Zoom
Created December 10, 2019 at 9:13 AM
Updated January 2, 2020 at 10:22 AM
Resolved December 23, 2019 at 1:10 PM
Zoom
The parser for the deployment environment incorrectly assumes that the
environmentis created by the Jenkins counterpart add-on () but this can also be created by another Jenkins plugin like EnvInject.This results in exceptions like the following:
The parser should also check the
__classattribute of the exported object to make sure it only parses the custom exported object created by the Jenkins counterpart add-on.