Hi Tilman,
People typically run juju tests with bundletester right now (despite its
name, it can be used to run a test on a single charm -- you'll need to
build the charm first if it is a layered charm). There's a section in the
docs about bundletester here:
https://jujucharms.com/docs/devel/devel
On 31.05.2017 14:39, Tim Van Steenburgh wrote:
> But, I couldn't. The review form at https://review.jujucharms.com/ will
> respond with a empty response (Firefox says https protocol error. Chrome
> says empty response.)
> Where would I report that as a bug?
>
>
> There's a "report
>
> But, I couldn't. The review form at https://review.jujucharms.com/ will
> respond with a empty response (Firefox says https protocol error. Chrome
> says empty response.)
> Where would I report that as a bug?
>
>
There's a "report bug" link at the bottom of the review queue web pages. I
went ah
On 31.05.2017 10:45, John Meinel wrote:
> I'm pretty sure 'charm' tools have moved over to using 'snap install
> charm' as the preferred method for getting the charm tools. I'm not sure
> that there is a way to deprecate/remove the versions that are in the
> archives. For something like Zesty, it p
Those are subordninate charms that can be used like plugins to load
> custom configurations in logstash (/etc/logstash/conf.d/)
> Or to connect logstash to elasticsearch via relations.
>
> During this development I found a number of bugs that made it quite hard
> to be productive.
&g
://bugs.launchpad.net/ubuntu/+source/charm-tools/+bug/1660004
And juju test doesn't work. That is why my charms don't have tests yet.
https://bugs.launchpad.net/juju/+bug/1608723
I felt quite confident about my manual tests and I see no reason to
believe #1608723 will be gone soon, so I
