Looks cool Merlijn -- I may use this in the near future as I have some similar scripts I have cobbled together as well. :)
On Thu, Nov 3, 2016 at 11:46 AM, Merlijn Sebrechts < merlijn.sebrec...@gmail.com> wrote: > Hi all > > > I wrote my own python script to test and publish bundles and their charms. > It's very specialized for our use-case so I doubt it's useful for you guys > although I like the idea of a reference script. I'd like to follow the > development of that script to make sure it also fits our use-case. > > > *For reference, our script does the following:* > > 1. *The script receives a number of bundles as commandline arguments.* > 2. *It checks which of our Charms are in the bundles.* > 3. *It pushes those charms to unpublished channel* > 4. *It rewrites the bundles so they point to the unpublished charms* > 5. *It spins up a Juju client in an lxc container and run cwr inside > that container to test the bundles* > 6. *if tests succeed, it publishes both the bundles and our charms.* > > > *Script source > (agplv3): > https://github.com/IBCNServices/tengu-charms/blob/master/cihelpers.py > <https://github.com/IBCNServices/tengu-charms/blob/master/cihelpers.py>* > > > > Kind regards > Merlijn > > 2016-11-02 13:42 GMT+01:00 Stuart Bishop <stuart.bis...@canonical.com>: > >> >> >> On 2 November 2016 at 18:24, Konstantinos Tsakalozos < >> kos.tsakalo...@canonical.com> wrote: >> >>> 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? >>> >>> >> It could be much, much more elegant. I've got open issues on getting >> 'charm push' to report the revision better (so you can publish or tag), or >> even having 'charm push --channel' do what you want. I personally would >> rather see this improved so it helps everyone, to the point you don't need >> a Jenkins plugin. >> >> An automated system needs to deal with the auth problem, which is >> unfortunate (someone typing 'charm login' and entering their SSO password >> and a token on a possibly untrusted system, or manufacturing an auth token >> and installing it somehow). Snappy has this sorted better, with Launchpad >> able to build snaps from a branch and upload them to the snap store on your >> behalf. >> >> >> -- >> Stuart Bishop <stuart.bis...@canonical.com> >> >> -- >> 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 > > -- David Britton <david.brit...@canonical.com>
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju