-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Remote jenkins running 2.164.32.0.1-fixed
For remote jekins that provides all lower-case HTTP headers, the parameterized remote trigger will fail with error such as
ERROR: Remote build failed with 'AbortException' for the following reason: 'Error triggering the remote job. The header of the response has an unexpected format:
{date=[Tue, 21 Apr 2020 02:26:47 GMT], null=[HTTP/1.1 201 Created], server=[envoy], content-length=[0], x-envoy-upstream-service-time=[15], x-content-type-options=[nosniff], location=[http://example.com/jenkins/myjenkins/queue/item/4848912/]}'.
It seems the plugin is looking for "Location" but only "location" is provided.
https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/68 has some test cases demonstrating the issue and a possible solution.
3.2. Header Fields
Each header field consists of a *case-insensitive* field name followed
by a colon (":"), optional leading whitespace, the field value, and
optional trailing whitespace.
https://tools.ietf.org/html/rfc7230#appendix-A.2
Looks like most things are expected to be case-insensitive...
Of course the wonderful thing about standards is that everyone can have their own!
The version of the invoker in this case is: Parameterized-Remote-Trigger:3.1.2