WEBVTT

00:00.270 --> 00:06.840
And if I could show you is how much, Lindsay, and this is really useful if something's missing or

00:06.840 --> 00:09.720
something that would break Helme from templating.

00:11.740 --> 00:17.350
If I set my deployment name to this and then get into the directory, so sitting to my first chance,

00:17.350 --> 00:23.200
I'm on helm linked, it comes back fine and no error reported, there was no trick.

00:23.200 --> 00:26.320
I'm going to show you so you can spot and resolve issues like that.

00:26.500 --> 00:31.870
If I were, for example, missing a curly brace, I know we can see it here on our terminal.

00:31.870 --> 00:35.980
And Ron Helminths again, this time it returns an error.

00:36.830 --> 00:38.950
I can see I'm missing a curly brace.

00:43.680 --> 00:49.530
She was not very wise that we run helplines again, we'll see that as an issue is a useful trick for

00:49.530 --> 00:53.400
spotting things, and I really recommend adding this as a step.

00:53.400 --> 00:59.580
If you're using Jenkins' to build your Helmholtz or as part of your secedes process, it's well worth

00:59.580 --> 01:04.200
it if you're using help to add Helminths, because then before you package it and try and deploy, you'll

01:04.200 --> 01:05.180
know it as an issue.

01:05.520 --> 01:06.960
So as one troubleshooting technique.

01:07.320 --> 01:08.790
Let me show you another.