Hi Martin, Are we going to rewrite codes by using any one of the 3 plugins or write from scratch?? If its going to be from scratch, I find that its always best to cover all aspects of Jenkins to be covered under REST API. Similar to Bitbucket APIs, like connecting the configuration till enabling and building pipeline or proceeding via the APIs. As it will make the Jenkins more powerful and easier to integrate it with third-parties.
On Saturday, December 22, 2018 at 8:58:11 PM UTC+5:30, martinda wrote: > > Hi, > > We currently have a Google Summer of Code proposal > <https://docs.google.com/document/d/1Xz3I02T-QxlJW-1nt_CofF2I6se3hztF9ZsHqxu55nU/edit?usp=sharing> > > aimed at wrapping a Jenkins REST API Client into a Jenkins Pipeline Plugin. > There are a few jenkins rest api clients which can be used to make this > possible: > > > 1. https://github.com/cdancy/jenkins-rest > 2. https://github.com/jenkinsci/java-client-api > 3. https://github.com/cliffano/swaggy-jenkins > > > I am reaching out to the community to probe interest, feedback on the > proposal, comments and to recruit mentors for this project. Being a mentor > is open to everyone. > > Thanks, > Martin d'Anjou > Jenkins GSoC 2019 Org Admin > -- 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/bda3c756-cc8f-4b7f-b666-87bd4c6231bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
