1. We can eliminate the dependency for CLI to be installed on the Jenkins slave. 2. Where do you store the credentials [to talk to aurora], clusters.json etc ? In Jenkins we can use credentials plugin[assuming auora plugin would use that] to safely store the password. 3. As you have mentioned , we can include the updater URL in build status page.
On Thu, Sep 1, 2016 at 7:32 PM, ben...@gmail.com <ben...@gmail.com> wrote: > What would the plugin do better than simply running the aurora CLI tool in > a small "run shell command" build step? We've been doing aurora updates as > part of jenkins build pipelines, but so far haven't found a need for more > than one or two CLI commands to do it. > > Picking up the updater URL and displaying it on the build status page could > be useful at least - but I suspect I am missing part of the point. > > On Mon, Aug 29, 2016 at 5:17 PM Manivannan <citizenm...@gmail.com> wrote: > > > Hi, > > > > I was thinking about implementing a Jenkins plugin to push updates to > > Aurora jobs. Something similar to > > https://github.com/jenkinsci/marathon-plugin. So that users can use this > > plugin to build pipeline along with CI to push updates to running jobs. > > > > I was wondering if it will be useful for aurora community ? > > > > Thanks, > > Mani > > >
