Hi Tom, Yes, I have my own script right now. It is not elegant.
Instead of each one of us maintaining their own scripts, we could have a single point of reference. In the Jenkins world I thought that would be a plugin, but a script would also work. Is there anyone open sourcing his CI <--> juju integration scripts? Thanks, Konstantinos On Wed, Nov 2, 2016 at 1:12 PM, Tom Barber <t...@analytical-labs.com> wrote: > I'm pretty sure you can write that in 4 lines of bash at the end of the > build/test process! ;) > > Sure you could write a plugin, but is it worth the effort I guess? > > Tom > > -------------- > > Director Meteorite.bi - Saiku Analytics Founder > Tel: +44(0)5603641316 > > (Thanks to the Saiku community we reached our Kickstart > <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/> > goal, but you can always help by sponsoring the project > <http://www.meteorite.bi/products/saiku/sponsorship>) > > On 2 November 2016 at 11:01, Konstantinos Tsakalozos < > kos.tsakalo...@canonical.com> wrote: > >> Hi everyone, >> >> After a successful build and (bundle)test of a charm I would like the >> output charm to be automatically uploaded to the store (edge channel for >> now). Is there a Jenkins plugin to ease the interaction with the Juju store >> (login/push/grant/release)? >> >> Thanks, >> Konstantinos >> >> >> -- >> Juju mailing list >> Juju@lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/juju >> >> >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
