Closed bac closed 8 years ago
QA:
deploy charm
ensure you can hit the GUI in the browser
juju run --unit juju-gui/0 'cat /usr/local/bin/runserver.sh'
ensure no gisf
juju set-config juju-gui gisf-enabled=true
juju run --unit juju-gui/0 'cat /usr/local/bin/runserver.sh'
ensure --gisf
:+1:
I'm wondering how this got past QA previously, since that should have caught this issue. Did we accidentally not QA your previous PR?
This definitely supports the idea that we need to rethink the process of adding options to the gui charm; there's a lot of possible break points.
QAing now.
:+1:
QA OK.
:shipit:
Status: merge request accepted. Url: http://ci.jujugui.org:8080/job/juju-gui-charm-merge
Fixed Issue #53
The QA on the previous branch was incomplete. It focused on seeing that the option was written to runserver.sh but didn't actually hit the GUI to see that it had started.
Yes @hatched we need a suite of tests that ensure the options we are setting are actually accepted.
Test PASSed. Refer to this link for build results (access rights to CI server needed): http://ci.jujugui.org:8080//job/juju-gui-charm/95/ Test PASSed.