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

User can add a new step from the list of available steps and edit it

    XMLWordPrintable

    Details

    • Sprint:
      atlantic, arctic, tasman, frank
    • Similar Issues:

      Description

      In Scope

      • User clicks "Add Step" and the dialog appears showing a list of steps
      • Clicking "Use Step" adds a the step to the end of the step list
      • User can see the form for the step in the editor
      • List of available steps is driven by the API provided by JENKINS-38584
      • An extension point for a step editor to plug into
      • Implement for at least 2 different steps (so we know what a step editor form looks like)
      • User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)

      Out of Scope

      • Adding a step which doesn't have an editor (handled in another ticket)

      Some more details:

      A chunk of steps in the model/json looks like this:

      "steps":       [
                      {
                "name": "sh",
                "arguments":           {
                  "value": "cat /usr/local/apache2/conf/extra/httpd-userdir.conf"
                }
              },
                      {
                "name": "sh",
                "arguments":           {            
                  "value": "echo \"The answer is 42\""
                }
              }
            ]
      

      (referring to https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/test/resources/json/agentDocker.json - details may change a bit).

      Note that each step object has a name (which can be looked up to see if there is an editor for it). In this case it is the most common sh step - the arguments here is a simple object which has a "value" of the script.

      This AST/model is formally defined here: https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/main/resources/ast-schema.json. This is an example of a "named argument" - there are few ways arguments for steps can be expressed but this is most common (and fairly simple).
      Different steps may have different representations: one of namedArgumentList, positionalArgumentList or singleArgument.

        Attachments

          Issue Links

            Activity

            jamesdumay James Dumay created issue -
            jamesdumay James Dumay made changes -
            Field Original Value New Value
            Epic Link JENKINS-36291 [ 172300 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Issue Type Task [ 3 ] Story [ 10002 ]
            jamesdumay James Dumay made changes -
            Description *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * List of available steps is driven by the API provided by JENKINS-38584
            *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            jamesdumay James Dumay made changes -
            Sprint atlantic [ 106 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Assignee Keith Zantow [ kzantow ]
            michaelneale Michael Neale made changes -
            Description *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            michaelneale Michael Neale made changes -
            Description *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)
            michaelneale Michael Neale made changes -
            Summary User can add a new step from the list of available steps User can add a new step from the list of available steps and edit it
            michaelneale Michael Neale made changes -
            Description *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)
            *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            * User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)
            michaelneale Michael Neale made changes -
            Description *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            * User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)
            *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            * User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)

            Some more details:

            michaelneale Michael Neale made changes -
            Link This issue relates to JENKINS-35856 [ JENKINS-35856 ]
            michaelneale Michael Neale made changes -
            Description *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            * User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)

            Some more details:

            *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            * User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)

            Some more details:

            A chunk of steps in the model/json looks like this:
            {noformat}
            "steps": [
                            {
                      "name": "sh",
                      "arguments": {
                        "value": "cat /usr/local/apache2/conf/extra/httpd-userdir.conf"
                      }
                    },
                            {
                      "name": "sh",
                      "arguments": {
                        "value": "echo \"The answer is 42\""
                      }
                    }
                  ]
            {noformat}

            (referring to https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/test/resources/json/agentDocker.json - details may change a bit).

            Note that each step object has a name (which can be looked up to see if there is an editor for it). In this case it is the most common sh step - the arguments here is a simple object which has a "value" of the script. This AST/model is formalled defined here: https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/main/resources/ast-schema.json. This is an example of a "named argument" - there are few ways arguments for steps can be expressed but this is most common (and fairly simple).

            Different steps may have different representations, but always defined by the JSON AST (most are this simple)

            michaelneale Michael Neale made changes -
            Description *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            * User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)

            Some more details:

            A chunk of steps in the model/json looks like this:
            {noformat}
            "steps": [
                            {
                      "name": "sh",
                      "arguments": {
                        "value": "cat /usr/local/apache2/conf/extra/httpd-userdir.conf"
                      }
                    },
                            {
                      "name": "sh",
                      "arguments": {
                        "value": "echo \"The answer is 42\""
                      }
                    }
                  ]
            {noformat}

            (referring to https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/test/resources/json/agentDocker.json - details may change a bit).

            Note that each step object has a name (which can be looked up to see if there is an editor for it). In this case it is the most common sh step - the arguments here is a simple object which has a "value" of the script. This AST/model is formalled defined here: https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/main/resources/ast-schema.json. This is an example of a "named argument" - there are few ways arguments for steps can be expressed but this is most common (and fairly simple).

            Different steps may have different representations, but always defined by the JSON AST (most are this simple)

            *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            * User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)

            Some more details:

            A chunk of steps in the model/json looks like this:
            {noformat}
            "steps": [
                            {
                      "name": "sh",
                      "arguments": {
                        "value": "cat /usr/local/apache2/conf/extra/httpd-userdir.conf"
                      }
                    },
                            {
                      "name": "sh",
                      "arguments": {
                        "value": "echo \"The answer is 42\""
                      }
                    }
                  ]
            {noformat}

            (referring to https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/test/resources/json/agentDocker.json - details may change a bit).

            Note that each step object has a name (which can be looked up to see if there is an editor for it). In this case it is the most common sh step - the arguments here is a simple object which has a "value" of the script. This AST/model is formalled defined here: https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/main/resources/ast-schema.json. This is an example of a "named argument" - there are few ways arguments for steps can be expressed but this is most common (and fairly simple).

            Different steps may have different representations: one of namedArgumentList, positionalArgumentList or singleArgument.

            michaelneale Michael Neale made changes -
            Description *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            * User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)

            Some more details:

            A chunk of steps in the model/json looks like this:
            {noformat}
            "steps": [
                            {
                      "name": "sh",
                      "arguments": {
                        "value": "cat /usr/local/apache2/conf/extra/httpd-userdir.conf"
                      }
                    },
                            {
                      "name": "sh",
                      "arguments": {
                        "value": "echo \"The answer is 42\""
                      }
                    }
                  ]
            {noformat}

            (referring to https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/test/resources/json/agentDocker.json - details may change a bit).

            Note that each step object has a name (which can be looked up to see if there is an editor for it). In this case it is the most common sh step - the arguments here is a simple object which has a "value" of the script. This AST/model is formalled defined here: https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/main/resources/ast-schema.json. This is an example of a "named argument" - there are few ways arguments for steps can be expressed but this is most common (and fairly simple).

            Different steps may have different representations: one of namedArgumentList, positionalArgumentList or singleArgument.

            *In Scope*
            * User clicks "Add Step" and the dialog appears showing a list of steps
            * Clicking "Use Step" adds a the step to the end of the step list
            * User can see the form for the step in the editor
            * List of available steps is driven by the API provided by JENKINS-38584
            * An extension point for a step editor to plug into
            * Implement for at least 2 different steps (so we know what a step editor form looks like)
            * User can click on a step after it has been added and edit contents (via its editor, unless it is "unsupported" type see https://issues.jenkins-ci.org/browse/JENKINS-38590)

            *Out of Scope*
            * Adding a step which doesn't have an editor (handled in another ticket)

            Some more details:

            A chunk of steps in the model/json looks like this:
            {noformat}
            "steps": [
                            {
                      "name": "sh",
                      "arguments": {
                        "value": "cat /usr/local/apache2/conf/extra/httpd-userdir.conf"
                      }
                    },
                            {
                      "name": "sh",
                      "arguments": {
                        "value": "echo \"The answer is 42\""
                      }
                    }
                  ]
            {noformat}

            (referring to https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/test/resources/json/agentDocker.json - details may change a bit).

            Note that each step object has a name (which can be looked up to see if there is an editor for it). In this case it is the most common sh step - the arguments here is a simple object which has a "value" of the script.

            This AST/model is formally defined here: https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/src/main/resources/ast-schema.json. This is an example of a "named argument" - there are few ways arguments for steps can be expressed but this is most common (and fairly simple).
            Different steps may have different representations: one of namedArgumentList, positionalArgumentList or singleArgument.

            michaelneale Michael Neale made changes -
            Link This issue blocks JENKINS-38587 [ JENKINS-38587 ]
            jamesdumay James Dumay made changes -
            Sprint atlantic [ 106 ] atlantic, indian [ 106, 126 ]
            jamesdumay James Dumay made changes -
            Link This issue relates to JENKINS-35856 [ JENKINS-35856 ]
            jamesdumay James Dumay made changes -
            Link This issue is blocked by JENKINS-39371 [ JENKINS-39371 ]
            jamesdumay James Dumay made changes -
            Sprint atlantic, indian [ 106, 126 ] atlantic, arctic [ 106, 131 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Priority Minor [ 4 ] Critical [ 2 ]
            jamesdumay James Dumay made changes -
            Link This issue is blocked by JENKINS-38584 [ JENKINS-38584 ]
            jamesdumay James Dumay made changes -
            Priority Critical [ 2 ] Major [ 3 ]
            kzantow Keith Zantow made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jamesdumay James Dumay made changes -
            Sprint atlantic, arctic [ 106, 131 ] atlantic, arctic, tasman [ 106, 131, 136 ]
            jamesdumay James Dumay made changes -
            Sprint atlantic, arctic, tasman [ 106, 131, 136 ] atlantic, arctic, tasman, frank [ 106, 131, 136, 156 ]
            kzantow Keith Zantow made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            kzantow Keith Zantow made changes -
            Status In Review [ 10005 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]

              People

              • Assignee:
                kzantow Keith Zantow
                Reporter:
                jamesdumay James Dumay
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: