CI status and plans

Gary Poster gary.poster at canonical.com
Thu Feb 7 01:59:19 UTC 2013


On 02/05/2013 09:32 PM, Gary Poster wrote:
> 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.

We also need to poke a firewall hole so that our build machine can get
to saucelabs (I filed RT 59209), and we need to associate a public IP
with our canonistack charm instance so saucelabs can get to the GUI (I
filed https://bugs.launchpad.net/juju-gui/+bug/1117888 and made a card;
please read the bug).

Gary



More information about the Juju-GUI mailing list