-
Bug
-
Resolution: Unresolved
-
Minor
-
Windows 2000 Server Jenkins 1.580.3
2 Jenkins Servers: build and integrate
integrate has a deploy job with a "Quiet period" of 1800 (seconds)
build triggers via "Parameterized Remote Trigger Plugin" Verison 2.1.3
with "Trigger a remote parameterized job" that job.
The deploy job starts immediately.
Expected is that the deploy job on integrate is queued and waits for 30 minutes.
Seems to be that
"Trigger builds remotely (e.g., from scripts)" with "Authentication Token"
akts like pressing on the "Build" link.
Should be like other build triggers.
This plugin does all of its interactions by making API calls to the remote Jenkins server.
If triggering a build via the API does not acknowledge the quite period... maybe this is an issue with core?