-
Bug
-
Resolution: Not A Defect
-
Blocker
-
Any OS, SVN
When trying to trigger builds remotely using the URL http://server/job/myjob/buildWithParameters?PARAMETER=Value, the following message comes up.
You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin.
There is a "Proceed" button which needs to be clicked on manually which causes (post-commit) remote triggering of builds via wget to fail.
This problem did not exist in 1.501, onlty started to notice this issue in versions 1.503 and 1.505.
[JENKINS-17221] "You must use POST method to trigger builds" warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParameters?PARAMETER=Value
| Description |
Original:
When trying to trigger builds remotely using the URL http://server/job/myjob/buildWithParameters?PARAMETER=Value, the following message comes up. {noformat} You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin. {noformat} There is a "Proceed" button which needs to be clicked on manually which causes (post-commit) remote triggering of builds via wget to fail. |
New:
When trying to trigger builds remotely using the URL http://server/job/myjob/buildWithParameters?PARAMETER=Value, the following message comes up. {noformat} You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin. {noformat} There is a "Proceed" button which needs to be clicked on manually which causes (post-commit) remote triggering of builds via wget to fail. This problem did not exist in 1.501, onlty started to notice this issue in versions 1.503 and 1.505. |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
I guess the page https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build needs to be updated since the following recommended method no longer works.
- A build can be started just by accessing
http://server/job/myjob/buildWithParameters?PARAMETER=Value
I manged to work around the issue by using build trigger authentication tokens as the warning message suggests.
Kevin Thieling
added a comment - What about when clicking on the "Build Now" link and this occurs? Is that a core issue, a plugin issue, or maybe a configuration issue?
Kevin Thieling
added a comment - What about when clicking on the "Build Now" link and this occurs? Is that a core issue, a plugin issue, or maybe a configuration issue? @kt said:
What about when clicking on the "Build Now" link and this occurs?
That would be a separate bug report, assuming you could reproduce from scratch in a current version of Jenkins and provide details.
Jenkins IRC Bot
made changes -
| Component/s | New: core [ 15593 ] | |
| Component/s | Original: parameters [ 15594 ] |
| Workflow | Original: JNJira [ 148053 ] | New: JNJira + In-Review [ 192698 ] |
As the message says, you must now use POST requests for things like this. Consult the documentation for wget or whatever you use. Pull requests with more emphatic/clearer messages welcome.