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

User input when exec'ing Batch Task

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • batch-task-plugin
    • None
    • Platform: All, OS: All

      Sometimes user input is required for executing a Batch Task. It could be useful
      to be able to configure a Batch Task to first ask the user for all necessary
      input before executing the task.

      Unfortunately this raises a couple of questions:

      1) Input verification, yes or no?
      2) How to pass the input to the Batch Task?
      3) UI for configuring input values?
      4) UI for entering the required values?
      5) Defining input types?

      Perhaps starting small is a good idea:

      1) No
      2) Environment variables
      3) "Add value" button, adding a value name, short/long description in the
      configuration page
      4) Javascript popup (or something similarly simple) showing name, short/long
      description and an input field
      5) No, just plain text input that can be put into environment variables

          [JENKINS-1549] User input when exec'ing Batch Task

          canhuth added a comment -

          This might be a duplicate of issue 1914.

          canhuth added a comment - This might be a duplicate of issue 1914.

          renaudj added a comment -

          Actually, this is not the same issue. Issue #1914 is about parameterizing jobs.
          This one is to define specific parameters for batch tasks inside a job.

          A an example, you may want to create a Release task for a Maven2 build (as
          described here :
          http://hudson.gotdns.com/wiki//display/JENKINS/Batch+Task+Plugin). This task
          should ask for some parameters : scm username/password, name of the released
          version, name of the new version, tag to be created... But you don't want to
          define these parameters at the job level, as they are not relevant for
          continuous integration builds.

          renaudj added a comment - Actually, this is not the same issue. Issue #1914 is about parameterizing jobs. This one is to define specific parameters for batch tasks inside a job. A an example, you may want to create a Release task for a Maven2 build (as described here : http://hudson.gotdns.com/wiki//display/JENKINS/Batch+Task+Plugin ). This task should ask for some parameters : scm username/password, name of the released version, name of the new version, tag to be created... But you don't want to define these parameters at the job level, as they are not relevant for continuous integration builds.

            kohsuke Kohsuke Kawaguchi
            canhuth canhuth
            Votes:
            5 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: