We just upgraded from Jenkins 2.176.3 -> 2.204.1 and also updated to latest plugin versions.

We have a freestyle job that quit working after the upgrade that uses the urltrigger plugin.  The freestyle job has a simple string parameter and its value should be injected into the job as an environment variable.

Running urltrigger 0.47, the string parameter is not getting injected when the urltrigger fires the job.  This was working using urltrigger 0.45.    We downgraded to 0.45 and this job started working again.

The URLTrigger log from 0.47 when failing:

 Polling started on Jan 29, 2020 10:43:04 AM
 Polling for the job testfoo
 Looking nodes where the poll can be run. 
 Looking for a candidate node to run the poll. 
 Trying to find an eligible node with the assigned project label coord.
 Polling remotely on jenkinsserver 
 *Resolving environment variables using global values*
 Using Basic Authentication with the user 'build' 
 Invoking the url: [https://jenkinsserver.foo.com/job/test/job/test/job/testing/lastSuccessfulBuild/buildNumber/]
 [https://gen4cc-os.virtd.deere.com/job/gen4cc-os/job/gen4os/job/release-20-1/lastSuccessfulBuild/buildNumber/]
 Inspecting the content The content of the URL has changed.
 The content has changed.
 Polling complete.
 Took 0.61 sec.
 Changes found. 
 Scheduling a build.
 

When running with the working 0.45 plugin, the urltrigger log shows slightly different behavior.  It logs "Resolving environment variables using last build values" instead of when it is failing as above "Resolving environment variables using global values"
 
Looks like recent changes with the code emitting the message commented out:

https://github.com/jenkinsci/urltrigger-plugin/blob/63b65488e3cf89d1c40840fe881d5b2b59233ed7/src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java#L229
 
As a workaround, we downgraded to 0.45 for now.