{"push_id":1291602683,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"64aac82fb6052cffa923b0971dce9951c8a8fdf0","before":"7588da9d9d643ad561b596e9be5ed51ba3a39962","commits":[{"sha":"3c680b08073ab7d4ae9f7f289201cda3bb7a4e8f","author":{"name":"John E. Moscato","email":"a7f9ee8e19723da935fe6471568e9c56c63dee3a@gmail.com"},"message":"Add Jenkins Pipelines support to Option Provider\n\nThe Jenkins Pipeline plugin introduces the need to use more generic\nclasses in certain cases when working with Pipelines and Multibranch\nPipelines vs other types of Jenkins projects.\n\nFor the Jenkins Rundeck Option Provider, a few uses of AbstractProject\nneeded to be changed to the more generic Job class, as described in\nthe Basic update section of the Jenkins Pipelines Plugin Developer\nGuide (see the Source reference below).\n\nTo aid with determination of Option Provider URLs, the error message\nin the case of an invalid project parameter in the Option Provider URL\nhas also been enhanced to display a complete Jenkins item tree showing\nthe full name of each item, which can then be used as a project\nparameter. This is especially helpful for Jenkins Multibranch\nPipelines which contain a partially URL encoded path.\n\nSource\nhttps://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#user-content-basic-update","distinct":true,"url":"https://api.github.com/repos/jenkinsci/rundeck-plugin/commits/3c680b08073ab7d4ae9f7f289201cda3bb7a4e8f"},{"sha":"64aac82fb6052cffa923b0971dce9951c8a8fdf0","author":{"name":"Greg Schueler","email":"06ea6d55d58540f8828f87d6f7ee28f0017e8906@gmail.com"},"message":"Merge pull request #28 from jmoscato/jmoscato/feature/pipeline-project-support\n\nAdd Jenkins Pipelines support to Option Provider","distinct":true,"url":"https://api.github.com/repos/jenkinsci/rundeck-plugin/commits/64aac82fb6052cffa923b0971dce9951c8a8fdf0"}]}
{"actor":{"display_login":"gschueler"}}