-
Epic
-
Resolution: Fixed
-
Major
-
None
-
GSoC Phase 1 - Simple Pull request Job Project
-
Design:
- Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit
- Do we build the plugin on the top of Multi-Branch? *Yes*
- We build the solution as a separate plugin using extension points
End date: June 14th
Goals and deadlines are defined in the design doc
- 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/batch/Jenkinsfile/etc)
- 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.
- Decide how to pass required build parameters to build process and implement it.
- Implement the plugin prototype
- Present the plugin prototype at office hours to the public
- Write a blogpost with project introduction and the prototype overview/demo
[JENKINS-51371] GSoC Phase 1 - Simple Pull request Job Project
| Description |
Original:
Goals: * Prepare a proper format, using which users will be able to write specifications for the build, while discussing it with mentor. * Implement an interface to parse and get build specifications from YAML file. * Decide how to pass required build parameters to build process and implement it. * Implement the plugin prototype |
New:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points Goals and deadlines are defined in the design doc |
| Epic Child |
New:
|
| Description |
Original:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points Goals and deadlines are defined in the design doc |
New:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points Goals and deadlines are defined in the design doc * Prepare a proper format, using which users will be able to write specifications for the build ** git clone ** 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/batch/Jenkinsfile/etc) *User select where the file is located (we provide a default) ** git push [to target] ** harvest results and reports [and post in the PR] * Implement an interface to parse and get build specifications from YAML file. * Decide how to pass required build parameters to build process and implement it. * Implement the plugin prototype * Present the plugin prototype at office hours to the public * Write a blogpost with project introduction and the prototype overview/demo |
| Epic Child |
New:
|
| Description |
Original:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points Goals and deadlines are defined in the design doc * Prepare a proper format, using which users will be able to write specifications for the build ** git clone ** 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/batch/Jenkinsfile/etc) *User select where the file is located (we provide a default) ** git push [to target] ** harvest results and reports [and post in the PR] * Implement an interface to parse and get build specifications from YAML file. * Decide how to pass required build parameters to build process and implement it. * Implement the plugin prototype * Present the plugin prototype at office hours to the public * Write a blogpost with project introduction and the prototype overview/demo |
New:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points Goals and deadlines are defined in the design doc * Prepare a proper format, using which users will be able to write specifications for the build ** 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/batch/Jenkinsfile/etc) *** 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. * Decide how to pass required build parameters to build process and implement it. * Implement the plugin prototype * Present the plugin prototype at office hours to the public * Write a blogpost with project introduction and the prototype overview/demo |
| Description |
Original:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points Goals and deadlines are defined in the design doc * Prepare a proper format, using which users will be able to write specifications for the build ** 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/batch/Jenkinsfile/etc) *** 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. * Decide how to pass required build parameters to build process and implement it. * Implement the plugin prototype * Present the plugin prototype at office hours to the public * Write a blogpost with project introduction and the prototype overview/demo |
New:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points Goals and deadlines are defined in the design doc * Design a proper YAML format, using which users will be able to write specifications for the build * Implement basic steps supporrt ** 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/batch/Jenkinsfile/etc) *** 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. * Decide how to pass required build parameters to build process and implement it. * Implement the plugin prototype * Present the plugin prototype at office hours to the public * Write a blogpost with project introduction and the prototype overview/demo |
| Description |
Original:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points Goals and deadlines are defined in the design doc * Design a proper YAML format, using which users will be able to write specifications for the build * Implement basic steps supporrt ** 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/batch/Jenkinsfile/etc) *** 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. * Decide how to pass required build parameters to build process and implement it. * Implement the plugin prototype * Present the plugin prototype at office hours to the public * Write a blogpost with project introduction and the prototype overview/demo |
New:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points Goals and deadlines are defined in the design doc * 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/batch/Jenkinsfile/etc) *** 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. * Decide how to pass required build parameters to build process and implement it. * Implement the plugin prototype * Present the plugin prototype at office hours to the public * Write a blogpost with project introduction and the prototype overview/demo |
| Description |
Original:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points Goals and deadlines are defined in the design doc * 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/batch/Jenkinsfile/etc) *** 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. * Decide how to pass required build parameters to build process and implement it. * Implement the plugin prototype * Present the plugin prototype at office hours to the public * Write a blogpost with project introduction and the prototype overview/demo |
New:
Design: * Base design: https://docs.google.com/document/d/1cuC0AvQG3e4GCjIoCwK3J0tcJVAz1eNDKV8d_zXxlO8/edit * Do we build the plugin on the top of Multi-Branch? **Yes** * We build the solution as a separate plugin using extension points End date: June 14th Goals and deadlines are defined in the design doc * 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/batch/Jenkinsfile/etc) *** 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. * Decide how to pass required build parameters to build process and implement it. * Implement the plugin prototype * Present the plugin prototype at office hours to the public * Write a blogpost with project introduction and the prototype overview/demo |
| Epic Child |
New:
|