Best way to create CI pipeline for Charms

[Rick Harding]

Merlijn, this is great and exactly what I've been hoping someone would do
for charms with the new tooling that's been put together.

Personally, we're a heavy jenkins shop internally and know that the best.
Charles did some good work with Drone, but I've not tried it out.

One other thing to think about is I wonder if the Cloud Weather Report tool
provides output to gate CI on. It might be interesting because you'll get a
good visual output of the history, the tests are already there and it runs
against multiple clouds. You'd just trigger CWR from Jenkins and if that
passes, do the push to the store.

I've coped in Seman and Fabrice in as I think the two questions there are
if the CWR can provide good pass/fail error codes to Jenkins and the one
trick you'll need to be able to push the charm update to the store is a bot
based auth token to get the push to work properly.

 Hopefully they can speak to that more explicitly.

On Mon, Jun 6, 2016 at 5:14 AM Merlijn Sebrechts <
merlijn.sebrechts at gmail.com> wrote:

> Hi
>
>
> I'd like to setup a CI pipeline for Charms. Something that pulls code from
> Github after a push and runs unit and integration tests. When the tests
> succeed, it publishes the result to a personal namespace in the charms
> store.
>
> What's the best way to do this? I'm currently evaluating two options.
>
> - Charles' blogpost about Drone seems the most promising, but the project
> seems unmaintained.
> https://insights.ubuntu.com/2015/07/15/continuous-integration-with-juju-and-drone-ci/
>
> - Or I can just build it myself using Jenkins and bundletester.
>
>
>
> Kind regards
> Merlijn Sebrechts
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160606/7ad19616/attachment.html>