search

juju-solutions / bundle-cwr-ci

Deploy the Juju Charm CI system
Other
2 stars 6 forks source link

Better error messages #16

Open merlijn-sebrechts opened 7 years ago

merlijn-sebrechts commented 7 years ago

Hi

The current Jenkins build output is quite hard to debug. An example: if a charm is using a layer that is not on interfaces.juju.solutions, you get the following error.

Fatal: could not read username for 'https //github.com' device not configured

Is it possible to maybe do some post-processing when an error occurs to guide the user to where the issue lies?

pengale commented 7 years ago

galgalesh: we were just having a conversation about more robust error reporting :-)

+1 to making this error more explicit.