Juju Charm store submission and functional tests using Amulet

[Marco Ceppi]

Hi Bruno,

When I search the charm store, https://jujucharms.com/u/3-bruno/, I don't
see any of these charms. However, they are properly uploaded to bzr. We're
very close to switching over to a new (more direct) way to publish charms
to the store, one where the process is a lot more transparent and direct.
However, in the meantime I've looked at your charms and I don't see any
issue which would prevent ingestion. I'll speak with our web team to figure
out if something else is wrong which isn't catching my eye.

As for your Amulet bug, it's not directly related to this, the error is
indicating that the websocket is timing out on deployment. I've kicked off
another round of tests on the review for the registry charm:
http://review.juju.solutions/review/2398 it seems to be the only one
failing of the ~5 you've submitted. I'll respond and take the Amulet
question off list and onto the bug report.

Thanks,
Marco Ceppi

On Mon, Jan 4, 2016 at 9:04 AM Bruno Ranieri <bruno at quobyte.com> wrote:

> Hello,
>
> I run into some problems when trying to bring some new charms through the
> charm store process
>
> https://bugs.launchpad.net/~3-bruno
>
> I submitted the charms, following the instructions on
> https://jujucharms.com/docs/stable/authors-charm-store, unfortunately the
> charms never showed up as name spaced charms. Thus
>
> juju deploy cs:~3-bruno/trusty/quobyte-registry
>> ERROR cannot resolve charm URL "cs:~3-bruno/trusty/quobyte-registry":
>> charm not found
>>
>
> while deployment using the local repository works fine.
>
> Another problem occurred, when I started to port my functional test from
> external scripts to <charmdir>/tests. Deployment is successful when using
> the local provider, but fails using a cloud provider (amazon):
>
> https://bugs.launchpad.net/amulet/+bug/1528582
>>
>
> Maybe this is related to the issue about name spaced charms described
> above? Unfortunately the uncaught Exception from Amulet does not provide
> further details.
>
> The problem is that my local environment does not provide enough
> resources, so I depend on using a cloud provider to port and test this
> functional tests. Just for completeness: my juju amazon environment is
> working fine. I can witness instances and volumes start-up and tear-down,
> when running my external functional tests or invoke tests using 'juju test'.
>
>
> regards
>  Bruno
>
>
> --
> *Quobyte* GmbH
> Hardenbergplatz 2 - 10623 Berlin - Germany
>
>
>
> --
> *Quobyte* GmbH
> Hardenbergplatz 2 - 10623 Berlin - Germany
> +49-30-814 591 800 - www.quobyte.com
> Amtsgericht Berlin-Charlottenburg, HRB 149012B
> management board: Dr. Felix Hupfeld, Dr. Björn Kolbeck, Dr. Jan Stender
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160104/5db63e2b/attachment.html>