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

Define a plan of what can be achieved by May 23

XMLWordPrintable

    • GSoC - Coding Phase 1, GSoC - Coding Phase 2

      We need to know what is going to be achieved by May 23 (first week of coding)

      ETA: May 17

      • Implement basic steps support
        • git clone/checkout (basic wrapper for the Git Plugin)
        • user is able to select a node to run the job via YAML
        • call user script [...TBD..extend multi-branch]
          • Support sh() and batch() invocations
          • User selected the type of invocation (sh and batch, other invocations will be taken care after 23 may like Jenkinsfile)
          • User select where the file is located (we provide a default)
        • git push [to target]
        • harvest results and reports [and post in the PR]
          • junit()
          • archiveArtifacts()

          [JENKINS-51373] Define a plan of what can be achieved by May 23

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Epic Link New: JENKINS-51371 [ 190718 ]
          Oleg Nenashev made changes -
          Summary Original: Define a plan of what can be achieved by May 15 New: Define a plan of what can be achieved by May 23
          Abhishek Gautam made changes -
          Description Original: We need to know what is going to be achieved by May 23 (first week of coding)

          ETA: May 17           		New: We need to know what is going to be achieved by May 23 (first week of coding)

          ETA: May 17
           * Design a proper YAML format, using which users will be able to write specifications for the build
           * Implement basic steps support
           ** git clone/checkout (basic wrapper for the Git Plugin)
           ** user is able to select a node to run the job via YAML
           ** call user script [...TBD..extend multi-branch]
           *** Support sh() and batch() invocations
           *** User selected the type of invocation (sh and batch, other invocations will be taken care after 23 may like Jenkinsfile)
           *** User select where the file is located (we provide a default)
           ** git push [to target]
           ** harvest results and reports [and post in the PR]
           *** junit()
           *** findbugs()
           *** archiveArtifacts()
           * Implement an interface to parse and get build specifications from YAML file.
          Abhishek Gautam made changes -
          Description Original: We need to know what is going to be achieved by May 23 (first week of coding)

          ETA: May 17
           * Design a proper YAML format, using which users will be able to write specifications for the build
           * Implement basic steps support
           ** git clone/checkout (basic wrapper for the Git Plugin)
           ** user is able to select a node to run the job via YAML
           ** call user script [...TBD..extend multi-branch]
           *** Support sh() and batch() invocations
           *** User selected the type of invocation (sh and batch, other invocations will be taken care after 23 may like Jenkinsfile)
           *** User select where the file is located (we provide a default)
           ** git push [to target]
           ** harvest results and reports [and post in the PR]
           *** junit()
           *** findbugs()
           *** archiveArtifacts()
           * Implement an interface to parse and get build specifications from YAML file.           		New: We need to know what is going to be achieved by May 23 (first week of coding)

          ETA: May 17
           * Design a proper YAML format, using which users will be able to write specifications for the build
           * Implement basic steps support
           ** git clone/checkout (basic wrapper for the Git Plugin)
           ** user is able to select a node to run the job via YAML
           ** call user script [...TBD..extend multi-branch]
           *** Support sh() and batch() invocations
           *** User selected the type of invocation (sh and batch, other invocations will be taken care after 23 may like Jenkinsfile)
           *** User select where the file is located (we provide a default)
           ** git push [to target]
           ** harvest results and reports [and post in the PR]
           *** junit()
           *** archiveArtifacts()
           * Implement an interface to parse and get build specifications from YAML file.
          Oleg Nenashev made changes -
          Sprint New: GSoC - Coding Phase 1 [ 556 ]
          Oleg Nenashev made changes -
          Rank New: Ranked higher

          J Knurek added a comment -

          gautamabhishek46 I think these goals are a bit too ambitious to accomplish for Wednesday. It seems you've already started on JENKINS-51374, and so at the minimum I'd suggest removing the yaml configuration from this weeks plan.

           

          It's much better to under promise and do more work, than to over promise and not reach your goals

          J Knurek added a comment - gautamabhishek46 I think these goals are a bit too ambitious to accomplish for Wednesday. It seems you've already started on JENKINS-51374 , and so at the minimum I'd suggest removing the yaml configuration from this weeks plan.   It's much better to under promise and do more work, than to over promise and not reach your goals
          Abhishek Gautam made changes -
          Description Original: We need to know what is going to be achieved by May 23 (first week of coding)

          ETA: May 17
           * Design a proper YAML format, using which users will be able to write specifications for the build
           * Implement basic steps support
           ** git clone/checkout (basic wrapper for the Git Plugin)
           ** user is able to select a node to run the job via YAML
           ** call user script [...TBD..extend multi-branch]
           *** Support sh() and batch() invocations
           *** User selected the type of invocation (sh and batch, other invocations will be taken care after 23 may like Jenkinsfile)
           *** User select where the file is located (we provide a default)
           ** git push [to target]
           ** harvest results and reports [and post in the PR]
           *** junit()
           *** archiveArtifacts()
           * Implement an interface to parse and get build specifications from YAML file.           		New: We need to know what is going to be achieved by May 23 (first week of coding)

          ETA: May 17
           * Implement basic steps support
           ** git clone/checkout (basic wrapper for the Git Plugin)
           ** user is able to select a node to run the job via YAML
           ** call user script [...TBD..extend multi-branch]
           *** Support sh() and batch() invocations
           *** User selected the type of invocation (sh and batch, other invocations will be taken care after 23 may like Jenkinsfile)
           *** User select where the file is located (we provide a default)
           ** git push [to target]
           ** harvest results and reports [and post in the PR]
           *** junit()
           *** archiveArtifacts()
           * Implement an interface to parse and get build specifications from YAML file.
          Abhishek Gautam made changes -
          Description Original: We need to know what is going to be achieved by May 23 (first week of coding)

          ETA: May 17
           * Implement basic steps support
           ** git clone/checkout (basic wrapper for the Git Plugin)
           ** user is able to select a node to run the job via YAML
           ** call user script [...TBD..extend multi-branch]
           *** Support sh() and batch() invocations
           *** User selected the type of invocation (sh and batch, other invocations will be taken care after 23 may like Jenkinsfile)
           *** User select where the file is located (we provide a default)
           ** git push [to target]
           ** harvest results and reports [and post in the PR]
           *** junit()
           *** archiveArtifacts()
           * Implement an interface to parse and get build specifications from YAML file.           		New: We need to know what is going to be achieved by May 23 (first week of coding)

          ETA: May 17
           * Implement basic steps support
           ** git clone/checkout (basic wrapper for the Git Plugin)
           ** user is able to select a node to run the job via YAML
           ** call user script [...TBD..extend multi-branch]
           *** Support sh() and batch() invocations
           *** User selected the type of invocation (sh and batch, other invocations will be taken care after 23 may like Jenkinsfile)
           *** User select where the file is located (we provide a default)
           ** git push [to target]
           ** harvest results and reports [and post in the PR]
           *** junit()
           *** archiveArtifacts()

            gautamabhishek46 Abhishek Gautam
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: