[JIRA] (JENKINS-51373) Define a plan of what can be achieved by May 23
Title: Message Title J Knurek commented on JENKINS-51373 Re: Define a plan of what can be achieved by May 23 based on the notes from yesterday's meeting, I would think that this ticket should be closed, and a new one created for the next weeks' goals? and/or maybe we should review from this what has been accomplished? at the very least, it'd be nice to see the next weeks goals defined out Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51373) Define a plan of what can be achieved by May 23
Title: Message Title Abhishek Gautam updated an issue Jenkins / JENKINS-51373 Define a plan of what can be achieved by May 23 Change By: Abhishek Gautam 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51373) Define a plan of what can be achieved by May 23
Title: Message Title Abhishek Gautam updated an issue Jenkins / JENKINS-51373 Define a plan of what can be achieved by May 23 Change By: Abhishek Gautam 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-51373) Define a plan of what can be achieved by May 23
Title: Message Title Abhishek Gautam commented on JENKINS-51373 Re: Define a plan of what can be achieved by May 23 J Knurek Thanks for the suggestion. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51373) Define a plan of what can be achieved by May 23
Title: Message Title J Knurek commented on JENKINS-51373 Re: Define a plan of what can be achieved by May 23 Abhishek Gautam 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 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51373) Define a plan of what can be achieved by May 23
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51373 Define a plan of what can be achieved by May 23 Change By: Oleg Nenashev Sprint: GSoC - Coding Phase 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51373) Define a plan of what can be achieved by May 23
Title: Message Title Abhishek Gautam updated an issue Jenkins / JENKINS-51373 Define a plan of what can be achieved by May 23 Change By: Abhishek Gautam 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51373) Define a plan of what can be achieved by May 23
Title: Message Title Abhishek Gautam updated an issue Jenkins / JENKINS-51373 Define a plan of what can be achieved by May 23 Change By: Abhishek Gautam 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51373) Define a plan of what can be achieved by May 23
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51373 Define a plan of what can be achieved by May 23 Change By: Oleg Nenashev Summary: Define a plan of what can be achieved by May 15 23 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
