Hi Abhishek, +1 to what you say. Any comments about the project proposal will be appreciated. Actually we expect students to make their own proposals, so do not consider the project idea description as a specification.
We just need to get input from YAML file and do things according to that. > > There is a java lib available to parse YAML file: > https://github.com/FasterXML/jackson-dataformats-text/tree/master/yaml > According to my experience, I would rather recommend Snake YAML. Actually we use FasterXML as well in many plugins... Generally we tend to package such libs as API plugins, like this one: https://github.com/jenkinsci/jackson2-api-plugin/blob/master/pom.xml . Any library can be used. Best regards, Oleg On Friday, March 16, 2018 at 3:22:31 AM UTC+1, martinda wrote: > > Hello Abhishek, > > Thanks for your interest in the Jenkins GSoC projects. > > > But then for every pull request administrator of the project needs to > create a job and then trigger a build. I think this will be cumbersome. > > Yes that is a model that I have seen. But there there is another model > which is to have a job that handles all the pull requests of a git repo to > a given branch. For example say there is a git repository called > jupiter/juno.git (jupiter is the name of the github org or of the bitbucket > project). Then the pull requests destined to the master branch of the juno > git repository could have a correspondig job called jupiter/juno/master. > There could be other models too. > > > pull request payloads have all of the above things, so we can extract > them from the pull request payload itself. > > I did not know this. How do the PR coordinates (source and destination > branches and repositories) get into the variables of a build if they are > not input parameters? Does this require the installation of plugins in > other systems? > > I would suggest that you consider preparing an application with your ideas > and suggestions in a google doc document. > > Best Regards, > Martin d'Anjou > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/887ad6fc-63aa-4a1b-a655-2eefaa0a78a9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
