Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-27249

Quiet period is not considered when triggering remotely

      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.

          [JENKINS-27249] Quiet period is not considered when triggering remotely

          Stefan Cordes created issue -
          Daniel Beck made changes -
          Component/s New: parameterized-remote-trigger-plugin [ 18159 ]
          Component/s Original: remoting [ 15489 ]
          Assignee New: Maurice W. [ morficus ]
          Maurice W. made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          Daniel Beck made changes -
          Resolution Original: Won't Fix [ 2 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]
          Mark Waite made changes -
          Summary Original: Quite Period is not considered when triggering remotely New: Quiet period is not considered when triggering remotely
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 161450 ] New: JNJira + In-Review [ 186274 ]

            morficus Maurice W.
            sc_rsc Stefan Cordes
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: