This is probably a longshot since it looks like this project is not updated often. We have automated our change management process and when a jenkins job fails before this plugin can create the change, the post step that usually closes or cancels the change is updating a random change on our servicenow account. The request reads in an environment variable that is "null" since it never got set in the previous steps for correlation_id. Somehow a random sys_id is used for correlation_id for a completely unrelated change (seems like whatever change is the most recent on the change table is the sys_id that gets used) and winds up updating the close note for a random change request.
This is probably a longshot since it looks like this project is not updated often. We have automated our change management process and when a jenkins job fails before this plugin can create the change, the post step that usually closes or cancels the change is updating a random change on our servicenow account. The request reads in an environment variable that is "null" since it never got set in the previous steps for correlation_id. Somehow a random sys_id is used for correlation_id for a completely unrelated change (seems like whatever change is the most recent on the change table is the sys_id that gets used) and winds up updating the close note for a random change request.
Version report
Jenkins and plugins versions report:
Reproduction steps
Results
Expected result:
Fail to update any change as an invalid correlation_id was passed
Actual result:
Seems to update a change request at random, not sure where it gets the sys_id from.