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

API(s) for acknowledging request for user input in a pipeline

XMLWordPrintable

    • pacific, atlantic, 1.0-b05/b-06, indian, arctic, tasman, christmas

      A pipeline can pause and ask for user input at any point.

      This needs to be exposed via the blue ocean REST api - both that it is waiting, but also that it can take a POST of data to acknowledge it. The input may take the form of Yes/No or it may be a richer set of input.

      In Scope:

      • API to fetch any pipelines blocked on "input" (for current user)
      • API to fetch what input is required from user (so a form can be built up on the client)
      • API to post confirmation from user (binary yes/no)
      • API to take a post of data from user (for non yes/no)
        (these are not necessarily separate unrelated apis, just that there needs to be support for those types of features)

      Out of scope:
      (perhaps we should start with simple yes/no)

          [JENKINS-35795] API(s) for acknowledging request for user input in a pipeline

          James Dumay created issue -
          Michael Neale made changes -
          Epic Link New: UX-165 [ 25873 ]
          Michael Neale made changes -
          Link New: This issue blocks UX-390 [ UX-390 ]
          James Dumay made changes -
          Labels New: api
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Rank New: Ranked lower
          Michael Neale made changes -
          Description Original: A pipeline can pause and ask for user input at any point.

          This needs to be exposed somehow via the blue ocean REST api - both that it is waiting, but also that it can take a POST of data to acknowlege it. The input may take the form of Yes/No or it may be a richer set of input.           		New: A pipeline can pause and ask for user input at any point.

          This needs to be exposed via the blue ocean REST api - both that it is waiting, but also that it can take a POST of data to acknowledge it. The input may take the form of Yes/No or it may be a richer set of input.

          In Scope:
             * API to fetch any pipelines blocked on "input" (for current user)
             * API to
          Michael Neale made changes -
          Description Original: A pipeline can pause and ask for user input at any point.

          This needs to be exposed via the blue ocean REST api - both that it is waiting, but also that it can take a POST of data to acknowledge it. The input may take the form of Yes/No or it may be a richer set of input.

          In Scope:
             * API to fetch any pipelines blocked on "input" (for current user)
             * API to           		New: A pipeline can pause and ask for user input at any point.

          This needs to be exposed via the blue ocean REST api - both that it is waiting, but also that it can take a POST of data to acknowledge it. The input may take the form of Yes/No or it may be a richer set of input.

          In Scope:
             * API to fetch any pipelines blocked on "input" (for current user)
             * API to fetch what input is required from user
             * API to post confirmation from user (binary yes/no)
             * API to take a post of data from user (for non yes/no)

          Out of scope:
             (perhaps we should start with simple yes/no)
          James Dumay made changes -
          Epic Link Original: UX-165 [ 25873 ] New: UX-70 [ 25240 ]
          V R made changes -
          Project Import New: Tue Jun 14 12:50:41 JST 2016 [ 1465876241198 ]
          R. Tyler Croy made changes -
          Project Import New: Wed Jun 15 02:53:18 UTC 2016 [ 1465959198925 ]

            vivek Vivek Pandey
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: