Hi James, We build our charms, push them to the store on the edge channel, and then our tests run against what is on edge. With this approach the team can sync on a specific build revision instead of each one separately trying to rebuild the charm locally and reproduce any unexpected behaviour. As soon as we are happy with a build we just promote it to the next channel (beta,candidate or stable). You can find our work here: https://github.com/juju-solutions/kubernetes-jenkins/tree/master/charms
Cheers, Konstantinos On Wed, Nov 22, 2017 at 2:21 AM, James Beedy <[email protected]> wrote: > I've a feeling that the majority of the CI/CD I've left in my trails that > attaches a resource from jenkins via juju bash cli are probably not working. > The latest CI/CD I've setup runs `juju attach` from jenkins, and I have to > login to the jenkins shell and su to the jenkins user and login to be able > to run my deploy step in jenkins. > > Is there a way that people are doing the jenkins<->juju dance without > lib-juju? > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
