CI status and plans

[Gary Poster]

Hi.  Everybody.  Here's a quick update on our CI status and plans.

Benji landed a bin/test-charm Monday that is a first step towards our CI
story.  Diogo and I have been working on getting that set up in Jenkins.
 Meanwhile, Benji and I identified some improvements we want.  The first
three are on the kanban board, and the last one is open for discussion.

CI test script must be able to initialize and run with very minimal
access to outside world
https://bugs.launchpad.net/juju-gui/+bug/1116650

selenium/sauce labs tests should include link to video/images
https://bugs.launchpad.net/juju-gui/+bug/1116274

CI tests are inefficient if repeated for different browsers
https://bugs.launchpad.net/juju-gui/+bug/1116698

Provide a convenient automated way to set up a dev environment
https://bugs.launchpad.net/juju-gui/+bug/1116702

It turns out that we need the first one for Diogo and I to proceed in
Jenkins.  I made a stab at this during spare moments today in
lp:~gary/juju-gui/bug1116650 .  I haven't tested it yet.  I ran out of
time.  If someone wants to run with it or do their own, please feel free.

Benji thinks he knows how to get 1116274 done cheaply.
https://saucelabs.com/docs/jenkins might help too.  Not sure.  We may
need that jenkins plugin just to expose our canonistack charm to sauce labs.

So, in sum, we are making good progress on this.  There's room to help
out if you want to.  Hopefully we'll have something basic fully working
by the end of the week.

BTW, if you want to join me on juju canonistack adventures, there's a
helper page now:
https://wiki.canonical.com/InformationInfrastructure/IS/CanonicalOpenstack/QuickStart
.  I had to re-download my canonistack credentials, so you might need to
also if you've had them for awhile.

Thanks all

Gary