Continuous Delivery Foundation CDF Twitch Channel, 25 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Twitch Stream number 4 2020-08-25

Description

Adam and JJ try the happy path using tekton.cd triggers on GitHub.

spoiler, we have some issues.

A

There we go we're gonna, I'm not gonna mess with that and we're live um hello. How are you.

B

Very good thanks how you doing jj.

A

Good, um who are you.

B

I'm adam roberts, I work well. I used to work quite a lot on techton, I'm an ambassador for cdot foundation and I like to kill things of tecton and jenkins x. Another kind of you know coordinate your project to do ci cd. Who are you, though,.

A

All right, yes, hi, I'm jj, uh j.j asgar, I'm a developer advocate for the ibm cloud um and I'm helping run this little uh stream for us because of the amount of streaming I've been doing for other stuff, and uh I've been I'm helping out with the tecton docs and um basically user experience in essence, um trying to get people to realize the power of tecton and things like that. But we are actually at the cd foundation stream, um so so adam.

A

How about you give a kind of quick little rundown of what the goal of this stream? Not this specific stream, but what our actual stream is, because we've started to get some unique views on to make sure everyone understands why we're here and what we're doing.

B

Yeah so essentially at cd.foundation, there's kind of you know four central projects that are supposed to be quite good and quite useful for doing uh continuous integration and use delivery, and it's basically jenkins x, jenkins, uh techton and spinnaker, and the idea is when I try these projects out.

B

I know a little bit about texan already, but we're going to try and show some cool things, basically the wider world, and if you find any issues, document them or fix them upstream them and make sure things run smoothly, so there's them quite a few on tecton already, I think going forward. You may try jenkins x out, and you know, use interactions encouraged if you've got any cool ideas hit us up on the twix chat. You can join with cd foundation slack or just you know, um fans, I guess things in our twitter. That's pretty.

A

Much it yeah awesome and uh today today is, as adam, maybe implied or explicitly said. uh It's gonna be one of my last times on actual tecton, because we found some interesting issues a couple weeks ago. We're doing this about every other week, just to make sure that you know we also have day jobs, um but we are going to go through a happy path of the triggers narrative, because, honestly, um we had a hard time last time it was it wasn't, uh it wasn't just like drop in and go.

A

It could have been uh due to some of our cloud or ibm cloud number nuances. I guess is a good word for it. Maybe I don't know sure, let's go with nuances, um but we are. uh We are going to walk through it and also upstream the the changes we saw from the documentation and then and then um yeah, hopefully, hopefully, that'll be just kind of a simple goal for us today.

A

We want to pay it back as they say to make sure that um future people who go down this path, because, honestly, if you're using tekton, there's a very strong possibility, um you want github triggers to work to be able to make the things happen, and this is only one of the different ways we do it, but this seems to be.

A

This seems to be the de facto way. Is that a good way of saying it or not? Yeah.

B

I would say so I think the first thing I do is read the triggers read me and go through a getting started guide and when we did it two weeks ago we did a lot of things and basically it didn't work and we spent maybe an hour or so debugging it. So if we can just do like, you know, 10 minutes where they just run it from scratch right things first and for any gaps, give us a pull request and then kind of wrap things up. That'd be amazing.

B

I say 10 minutes, there's a last minute says you know when you estimate something times up by two for the real duration.

B

So that's a fast reveal. Oh, but I've heard it somewhere. So why don't we give the main triggers getting started a try, let's try and get red hooks working again, but remember last time we did this jj you had to set the ingress secret. Didn't you.

A

That was that was the uh that was the the uh the lynch pin of getting the thing to actually talk to it.

B

And, as andrew said, we need the basics to foreign code, uh the secrets, don't we.

A

Yes, no no already. I do want to mention, because this is a good opportunity to capture this, as you saw, I scrolled through this whole readme looking for getting started, and it's actually at the very bottom like what to want to start using teton triggers, and it's one link here.

A

So that's already a little weird, I'm not gonna lie but yeah. I want to start using this. Oh, I have to read all of this stuff that I don't understand why.

B

Don't we do this? Why don't we do split screen? Why don't you do your notes on the right? We do terminal on the left and basically we're gonna write down things. We need to fix in a moment and go as a game on the other. So I think today delete the existing web book because I think I'm working and.

C

A

Notes, I can't type because everyone's watching me, I can't type, I'm sorry. Okay, first thing: first, move the getting started to a more prominent location.

D

A

um And then, because, obviously like I mean it's also kind of weird to have the background here, like I don't know is, is that is that right like like it feels like if I'm, if I'm coming in from the outside world and I'm like okay, so I got tr, I got tekton up and running sweet. I even have like um what is it that thing um kenneco working that I'm pushing my containers and everything's great, but now I want the automation of it. I go so I'm going to use triggers first thing.

A

I come to okay, that's important to know that's important. What like I want to use it like. What do I need to know this? So so maybe that's worth worth capturing too. So, okay, so getting started and just to prove okay get uh tr. I believe I actually still have them in there.

A

Yes yeah, so we actually need to trash in the bin get ready. Do you mind just taking care of that real quick? While I get.

B

This one yep okay, so I'm gonna do so. Basically, um okay gets yeah. These are let's see. We've got different. Crds that come with triggers they've got get trigger, template. I've also got get actually binding. Obviously, k is basically cube ctl.

B

A

Should we should we do the reverse of the configure cluster here? The installation would that.

B

Be a better way of doing it cluster. What's the reverse of configure cluster.

A

Well, yeah, it would be like k, delete right, dash, f, the file yeah. It's okay, delete, dash, f, docs.

B

ah The only thing is sometimes it's very dangerous when you do this in case thing called a name space reference name space. So what's in our name, space surfing juicy.

B

If I do k get secret, do you want to keep any of these jj? I quite.

A

B

Secret personally,.

A

Yes, that's true well, it gets created for us, though, if I were correctly right, if we should get a pro as soon as we get it configured correctly, the web hook secret and all that all the web hooks actually kick off and tell github to do the thing from correctly. Why.

B

Don't we do the entire name space, then? That seems like a reasonable.

A

Thing to do, oh, that's just so crazy! I mean this is this is a dev environment right. So if it breaks.

B

It's not a big deal. Assay goes in the bin, all right.

A

There we go ns, and this is um what do we call it.

B

Really orcs using the ox one.

A

Yeah tech, town pipelines: no, we don't want to delete that.

B

No okay: where did we get? Where did you do web folks? Did we do their name space? I think we did.

C

B

Yeah, so anything 30 days old goes in the bin. I say so. It means that book secret can go.

A

You go anytime, I trust you right.

B

Okey doke, so let's do red book secret um did k get to our earlier. As a reminder, that's okay!

B

So I'm going to delete all those test runs and we do have tasks for creating ingresses and web hooks by the way I've got any pipeline runs. Okay, get pr! We do, let's three, all of them and have we got any tasks.

B

We got plenty tell you what jj this won't be changing. um What about keep we keep these tasks.

A

Yeah, because we need to create the ingress and the web hook, and we know.

D

A

Were those are configured correctly now, so I wouldn't I'd be interested if you do a get diff on this repo, real quick to see the changes we've made because it'd be probably a good idea to see what we've done.

B

Yep, so we've changed the external domain when we create the ingress to use this one and we've got that value, I believe one sec from. Why do you get ingress and if I do a get deaf.

A

You no remember what to do. They pulled the ingress from the ibm cloud. Cli command. It's like get ibm cloud. Ks cluster get cluster name safely,.

B

Okay, so I could, if I had ibm cr.

B

ah I'd like to see a ghost of the correct command to do. No uh do.

A

You want exactly yeah, I got it.

B

I got it yeah, so this is your an ibm cloud. I'm gonna put into our notes when we do this.

A

Poster I can't type this.

B

A

There we go so this is our ingress sub domain, ah but this is. This is unique to the ibm cloud, though right um other other clouds wouldn't have this. They would assume that you would find it somewhere else. No.

B

But but uh I think most cars will have their own specific way of doing it, but people will need to figure out. Basically you know whether you're on google cloud or azure or aws. This will be, like you know, a canonical way of getting your external ip address right.

B

So we can say an ibm cloud. Is this, but you know your cloud experience may vary. Maybe it takes a lotion or heroic you and they've got their own little cli.

A

A

Yeah, if I were correctly, that is actually not mentioned at all in this thing and also because, as we saw earlier, the way we changed it, we just take the default stuff right like create the web hook right here. We'd have to actually add it and configure cluster to be like hey, um so this is configure.

A

Cluster cluster- and this is, I mean, lead me: okay, what else all.

B

Right next thing is: there's an inverse secret. That's being spewed out from your console output. Do we need to take a note of that secret or is it a reference to the secret? Is that a reference or is it actual value.

A

um So I I learned uh between our streams that it turns out because of the way um okay get secret screw up, because it's an opaque um secret is correct me from wrong. It's cluster wide. So all we have to do is reference it, because it's in every single name space already or is that wrong.

B

I got no idea, let's look it up. Should we get the official native secret docs up, um I find it hard to believe. Breadboard search is also inevitable. Names are the triggers one's eminem space either.

A

Yeah, I guess you're right vegas.

B

Means the contents are like visible. No, no, let's have a look.

C

A

On um good secret, no, it's behind by you name, space! Isn't it oh yeah.

A

If you want to steal the secret, live camera people you're more than welcome to just be sure to make sure that that is capital easy, oh, you just got to make sure, got to make sure it's not going to work. Unless you do that.

B

There'll be a bot network intact on the dusting people.

A

C

A

Yeah so yeah it is, it is bound by any choice, so you do have to export it and then import it. And who would somebody lied to me? Then? I swear yes.

B

So, okay, so we need to make a note of the secret name or the secret value.

A

Figure cluster make note of secret name from above step: okay and export the secret to a yaml file. Yaml then.

A

In um edit namespace line to namespace and import secret back.

B

In it from one name spaces, another right.

A

In essence, but you there is no like copy command, you have to export it out as a yaml file. Then you've got to edit this name space and then re-import.

B

It fiddly okay, so we've got that secret in the namespan to use in. um We know our ingress root. Now, don't we so we've also got the cluster roll and binding from last week. I think so, if I do k get nope all right.

B

If I would do oh take me over okay, can you get cr for cluster roll? Oh that's that would be nice, so k customer. What's it supposed to be called jj, do you remember, would you agree on triggers figures admin? Maybe it's a normal rule. I do k, get roll and again grip triggers okay. These two look familiar take time. Shots.

A

B

Work: yeah, okay, so we've got that cluster roll already and is there a binding as well? So if I do get roll binding part get triggers okay, so we've got create red pop roll and binding. Now do we have to change anything? Let's make that work? If I do it get diff, I don't think so.

B

So this is where we got the route. Oh, we changed the service name, but that was actually like made things a bit difficult for us to remember, because the names we have changed, your name space that also made it quite difficult.

A

No, it's because we we're trying to be cute, we're.

B

Trying to put us in the bottom so.

A

It's a good way to describe it.

B

Yep so so we took out that uh we changed the pipeline image. Url.

A

That's actually put inside the docs right here, yeah.

B

That's already documented: that's the replacement bit. How else did we do? Let's see webhook run, we changed all the github coordinates to point to your repo.

A

Here, that's that is actually put in here: oh yeah, wasn't it I believe it was here. We go uh ingress, run to a file to adjust the settings, and I believe that was what that is scroll back up.

A

No that's web hook run where the hell's workforce.

B

If you do a search on that page jj you just oh there, you go update web poke task from the bottom. Now, let's update the github test run yep there we go okay, cool, so that's done as well. That's good!

B

We can leave that as it is, and then we put in the excel domain in there as well is our fourth field actually in the update webpoint test run.

A

Yes, good eye good.

B

Answer: let's see these are the minimum, but hello. Your snow domain probably won't be.

C

Demo.Eancoffee.Com.

A

C

B

Right done now.

A

um Add the value of.

C

External domain has a minimum.

A

B

We've got it's time for the fun part. Now now we need to basically go and delete the web hook in uh not jenkins.

B

And the event listener will still have the trigger inside of it, so we may want to distribute the event listening as well.

A

All right, so I'm deleting the webhook on the public github.

B

If you do that, through there yeah, I don't think, there's a delete. Webhook tell you what jj before you do.

C

B

um Go back to the main readme: is there a way to trash your environment? Basically, so um the english tweet.

A

Says delete the namespace, but we don't want to delete the.

B

Name so, if you're putting the ingress task up, um I remember doing a pra just go where I did uh delete. I did a mode on the creation of the ingress, it's sort of a mode on this resource, so this one could just do k apply task run to delete the web port. They have removed from the event listener as well. I'm just wondering otherwise. You've got to event, delete the event listing, I think or manually.

A

B

Know manually remove the trigger bit, which may be a little bit awkward to do.

C

B

I think the docs help us, if that do they.

A

No, I don't think so that doesn't even doesn't even mention and also my one pass, isn't working. That's annoying.

B

Yeah well, while you do that, I'm going to tell people what I mean so yeah, the bigger references go into this event. Listener object. So if I do kg event list or yaml you'll see uh a little file, I'm just going to do my listener.yaml and let's just do more on that, I'm going to take you through what it does there's a normal kubernetes fields and then there's basically I'm expecting a triggers section.

B

Have you gone all the way down here we go so we do get started pipeline binding and when that's kind of you know activated somehow the thing it will run is the trigger template and that's using the address here. The internally available address of the uh the event listener itself, which we basically have a route that points to this. Now. What I'm trying to say is when we delete the web block in github that won't automatically have a callback to our cluster one, because you know there's no two-way communication.

B

um Now there is, but in most setups there may not be it's like when you change it over here. It changes it. Let's say over there when you do a new task run, but if you just use the ui and doing that web block this will this will stay the same, so we can delete the entire event nester or can do a little bit of surgery.

B

We can, basically, you know, cut out a little bit of the trigger from the event listener and that's actually quite awkward to do.

A

Yes, let's well, we want. We want to ha we're doing a happy path right, we're making updating the doc to be the best way to do it. So we want the least awkward, the most straightforward, because um I want to be able to put this in front of my five-year-old daughter and something she can read and she can make it this happen.

B

Yeah, well, I do as well so who creates the event listener. You.

A

Have a five-year-old daughter too,.

B

A

I said, I hope that she reads.

B

So we need to what does the doc say. Let's say manually, delete that.

A

It doesn't say the create install the event listener. It actually sends us to another page where the event listener is put inside of the triggers.yml. So.

B

It's in the docs getting started and then is there age figures: dot yaml there isn't there.

A

And that is, that is where the we set up the event listener to accept and process the push events.

B

And that's why we created here. I see right how lovely now, what I could probably do is copy get started, triggers.yaml and just call it uh triggers.yellow, and what I could then do for what I do is take out the little bit on triggers and then apply this channel, and I then have the same event listener with no triggers anymore.

B

The watch is what's in that file, though, so, if I do like a cat on that.

A

Side, but this isn't a way that we'd want someone to do it, though, right like that, seems a little bit of a smell, saying: hey, you need a copy of this file and then yeah I've removed the movies like that seems a little weird.

B

Yeah but I don't think there's an existing delete trigger from event listener.

B

Okay, so that's kind of like, uh but let's put in our notes, we've put side thought it'd, be nice to be able to delete a name trigger from the event.

B

Let's say by name I guess if that is even unique,.

A

We should probably just put that as an issue, but this is an issue saying hey yeah. It seems like it seems like a usability thing that should exist.

B

A

B

Okay, okay! So what's in this file, is it safe for me to do a cube, delete mysef that file.

A

uh Yes, but don't you want to edit the other one first and then diff them to make sure we haven't missed something right? uh What other one! So you made that other yaml file right, the the it's from the.

B

Dots, I think I thought it was a good idea at the time. Oh.

A

Yeah, okay, so we're we're, throwing things a lot, but throwing things back and forth pretty quickly here. So I thought I thought I thought you did my bad.

B

Now I'm sad, it wasn't a good idea, because I want to tell people copy the yaml, I guess and then a pie over yammer you'd. Basically change my mind. I was like no sorry.

A

Well then, yeah uh cuba, pi or cube delete, dash, f.

B

um Oh, I've got a bad feeling about this jj.

A

It's all right, you can always. We always run it again.

B

Okay, that's good only dated those three not narrow space cool. So now I'm going to do a that's just oh, no type it in oh.

A

Yeah, I use the vi bindings on the thing.

B

Right so we've run everything, and what did that even do that created the trigger template pipeline, binding and the event listener? It didn't create a good pocket, though, did it jj.

A

Correct the web hook is oh actually.

A

No, it did not because there is a create web hook, camera.

B

Yeah yeah now we've already got the tasks, don't we so that's sorted. We've updated the ingress tasks, one already, so that's probably sorted um and then run the ingress tasks. Shall we do that? Next, we'll do the opposite. Why don't we delete? Did that create an ingress? You may already have one that it made. Okay, let's see this is from last week. So I'll do the opposite and I'll do delete uh getting started and then create ingress.yaml.

B

A

So we go get ingress again.

B

Please, where are you where.

A

Did you go joe? Where did you come from? Oh.

B

That's that's it is that that's the is that the task.

C

B

Can't hit the task: if we can you throw up for me, please jj yep. I just wanted that deleted task itself.

B

Yeah that'll be picked on tasks investigated. Fine. Do I say the opposite of the debate. Run august complete the one.

A

No, I don't run.

B

Yeah we'll just delete the.

B

So we should now be kind of fresh okay, cool yeah. Now why don't we give that a try, we'll apply, docs getting started and then ingress run.yaml and that creates a new tester uh task from resolution? Failed? Oh, no! What's this opening listing task? Oh yeah, because we deleted the task accident. So so we do need.

A

Create ingress.

B

Yeah yeah, so if I do docs getting started, creating this should have our lovely tasks back and.

A

You need to delete the run again.

B

Yeah, I'm going to.

A

Reach the reel to rerun that.

B

Yeah, okay, all right, let's keep it queen and one at a time. So it was.

A

I just I just rms slash rf the whole thing anyway, so yeah screw it try.

B

Again so kick off the run, hopefully it doesn't error, get.

A

Oh because we haven't done it, we've created it. That makes sense. Oh yeah.

B

So, do you want to.

B

How did we create it last week? Maybe it's now death. I guess. Do I get different over here I'll get status, maybe.

A

We're perks, tr secret.

B

Hey these three, these two are promising yeah. So beyond, don't look at me the real secret all to you last.

A

All right, let's go with the real secret um and just kept that one quick, okay.

D

A

All right, oh did I delete it. I think I deleted the thing. So if you cat it's not going to be valid, go ahead and yeah, oh there we go and it's on base 64.. Oh no! That's.

B

The bad one or the good one uh what's in the others, can I show people don't look at me? Yeah! That's fine! Oh! What's this! Oh! This is the other secret. This looks like a now exported yaml off of your thing. There was.

A

B

A

B

So doc's getting started, see you last secret. Who are you same thing right so? Do we think the first one was maybe the right one.

A

The correct one: yes.

B

Okay, why don't we apply that? Then it's a bit of fun.

A

I don't think it's valid anymore, but okay.

B

um Okay, did you what how do we create the new one, then.

A

um So let me pull this over here.

C

A

A

First create new token, and this is we need that this is a.

A

So we need to actually put this in the docs here right, so we need to say inside well. This would be you probably want to do this when you change all those.

A

Set up event listener to kickstart, push all of events.

A

And where is it? Do you change all that stuff? Here we go web hook task.

A

So would we want to, we would actually want it up here and like configure, wouldn't we to create create this cluster. I think so. Okay, so um configure the.

A

um Cluster, a web hook c crit.

A

That would be this guy.

D

C

um You mentioned oops.

B

It's basically boring coded token, and the the secret is just basically for encoding anything. I think.

A

I think so I think that's right mention it's a.

C

B

Yeah I mean, if you basically decode that secret not the token the secret. What if it's just like fear or something.

A

A

Go so it's? What is it damn? It where's the decode.

B

Echo the value pipe base64 dash dash decode.

B

Yep, but with our real secret, obviously uh no we're talking, okay, so the b w niner that thingy.

C

B

You go it's my random word excellent, so that is that's basically food. So let's go and pop foo in um into our to do's, because we don't tell people to encode it. I'm not sure we tell people that the secret is just food, think we do at least.

A

Yep copy this for later there we go all right and then I also agree. I also believe we should co totally put this little secret yammel in the dock, so people see exactly what they need to add to do. The web hook secret.

B

What's in there already, I'm sure, there's something called dash secret.

A

I don't think there is.

B

It's just not encoded.

B

Does that say a g.

A

Yeah, it's a silver server. It's supposed to like go through code really quickly, for you.

B

Looks like food.

A

Web hook run just referenced, webhook secret doesn't actually it's.

B

Sure I'm going to triggers getting started, I'm thinking we got this getting started secret from somewhere.

A

I have a feeling it was dewan. He had it like in his back pocket yeah, no.

C

A

Do I really think so I don't think we actually ever yeah it.

B

Is what's that go up right? Oh there, you go oh, but it doesn't tell us that it's encoded, true, so music, just update that it's not the new yeah.

D

B

uh Updates encode, your new personal access token. I think.

A

Yep now this is under change till that run.

B

B

Of your new token, don't you jj.

A

All right, good car.

B

The old one so.

A

B

Go ahead and do that.

A

All right put up the secret bars, so nobody can see it.

B

Yep so jacob just create a new person access token using the github ui and the developer settings then he's going to basically four encode that and put it in his string data and then token that's going to go in there.

A

And we need to give it public, repo and admin repo hook.

B

It so yeah yeah public, repo and reaper hook as per the dock yep. Okay,.

B

All right and then, when you've done, that jj we're going to talk about the ingress secret that was missing last week two weeks ago, that made things look difficult.

B

As you said, that's kind of the the pinnacle of you know what the problem.

B

Was yep so jj's just an echo of the actual token pipe base64 and that's then covered it, for him he's just put that in so bad put the dash secret under the token field and again by the time you watch this, hopefully open up, yeah and it'll all be the documentation.

B

He's also encoding the random string data secret, so it used to be like you know, model now, it's that but encoded as well.

A

And we should be good there. We go okay.

B

Well done jj! I think we do we're good. So what was the ingress secret? Can you remember two weeks ago.

A

That was yeah, that was the um uh cluster.

A

C

A

That guy, which is the secret that we exported, which was one of the first things we said right.

B

Do you think just needs to be in the same name space? Oh, do you have to configure something to point to that secret.

A

uh No, we do if we do the export of the, um as we say at the very beginning, what we're going to talk about as the like expert, oh yaml, and then change the namespace and then re-import it. That should be that should get you the ingress secret. So we can talk to it. So everything kind of lines up for the ingress, subdomain.

B

We don't have to reference it in any of the task rules. That's a good question.

A

You should be regret if.

B

You do a clap on that invest, secret value, jj.

A

Good call qs secret.

B

What's that, what what's dealing with reminders.

A

That is the secret again.

A

So yeah this is this: is the exported tos secret that we did? Okay, so we didn't, we didn't actually have to reference it anymore, but does anthony.

B

A

No, it looks like it doesn't. We just have to put it in the correct. We just have to take the secret and put it in there and it looks like because we have the ingress run in the web hook run um that looks like it works. How we expect it to if we'll.

B

Be ready to do k apply minus that getting started. We're pokefun.yaml.

A

B

Believe so, and hopefully it goes green first time and then we can do a little bit of fiddling with the trigger setup and uh probably off stream or maybe on stream, do a nice little pr.

B

Yes, you know for slow changes, but you can show people you know going through prowl and building and doing little validations and uh hopefully making its way into the main branch.

A

So here we go putting the webhooks secret. In so now the webhook secret has been created, okay, that secret just to verify five seconds: perfect yep. So now we should be able to do k, apply, dash, f, docs, getting started web hook. Web hook run.

D

A

B

The one do that and then let's watch that task run again: oh going straight to get up brave.

B

Okay, it's just running if you want to watch pods, maybe okay, yeah.

C

B

Yeah you can't use the alias in the substrate. I guess.

D

B

I like how your fedora ones have never gone away by the way. Oh yeah, it's near 4, 000, 4 000, restarts.

A

Yeah, I don't know for some reason: it hasn't gone. Yeah.

C

A

We haven't no, it's not showing up.

B

It's still going up.

B

ah Remember if you get that as the logs, I bet you one cent, uh not encouraging gambling, it says ever. No, it says success, 401., that's not not successor. Is it it's going to say 401, but it won't tell you like the real error. That's my prediction.

B

Remember it's! Never, okay, get it! It's always just k logs. Oh.

A

Thank you, yeah. Thank you.

B

But yeah clear logs on is there a web pod up there somewhere? Maybe it's called get create, create yep, that's the one.

A

B

Come on definitely using generate names to.

B

Bad credentials, okay, I'm mistaken. It did tell us.

B

Now remember last time andrew said he's being coded, but we didn't call it didn't. We.

A

You didn't code, it yeah.

A

So this was that repository.

B

If you go up a little bit jj because he tried to see the post for jay jay oscar, not to like you know, eating coffee.

A

Yeah, we lost you by the way, you're really soft. Now.

B

Yes, there's the four one on them authorized there. I guess you sponsor the right place, go to your repo cool um yeah. I guess we done goofed on the secret.

A

Okay, so great.

C

A

Okay, where does it apply? Actually, so we tried to do this.

B

D

A

Yeah yeah, by the way your sounds like you move the mic or something you're really soft. Now.

B

I'm really soft.

A

Yeah we're book secret.

B

A

No actually you're still really you're a lot a lot less than you were.

D

A

Hey there, we go it's a little bit better as.

B

If I leave it like really close, you should hold it.

A

Yeah, if you want to see this is how close my mic is like it's like right. It's just a just a handful away from my mind, yeah.

B

On the other side, yeah.

D

B

We're showing folks uh secret um is that a space after the word tolkien jj, is that two.

A

B

A

B

A

There wasn't extra space at the end. No, what's that.

A

This one, so we want to.

B

B

And folks could use tk at this point to create that and you get a nice little follow logs option. Instead of doing this, okay get pods.

D

Wait: okay, jj.

B

Do k get tr, okay couldn't get tasks. Oh that's the old one. Let's see hold on last year. uh Okay, it's using the same name test run. Isn't it I think it's a name so yeah it tried to configure it and that doesn't actually re-run the task. As far as I know, so that's a bit of a pain. So if you do delete and then do a game plan, you could probably um do a pull request to make it use generate name, not name.

B

So, instead of create report, call it be created, block one one, two three and then next time right before five, six, oh.

A

Yeah, well I mean at the same time, if you got everything set up properly, you only have to run this once.

B

Yeah but let's be honest, who's gonna start properly. The first time me, I don't.

B

Said nobody ever okay.

D

B

See what's in there five seconds, wow.

A

B

You go, did it work?

B

No now. Is this a mirror above.

B

Who's giving it garbage, are you sure about token? That's the right token. I mean.

A

Yeah all right so echo that oh no is it because.

A

B

I don't put quotes around it. No, I don't need quotes. No yep go is that the secret in your.

C

C

A

It the real secret.

B

The real secret, oh no, it matches or nightmare.

C

How did we get this wrong so.

B

We're pointing to the right place: we've encoded the secret.

C

B

Is it not encoded? No, it is encoded, it's definitely encoded. That's the.

C

B

Skills encoded.

A

Yeah, if we do this and then base.

C

B

Code yeah does.

C

B

B

B

By the way, folks, please don't go onto jj's github. Oh.

A

I I have it literally the delete button as soon as something weird happens.

B

Please be gentle to us. Please don't.

C

B

All right, so I'm I'm stumped man is that definitely your token yeah. I can make this a magic trick. Is this your token.

B

Maybe you start recording it correctly. Maybe the command base pipe. Basically, four doesn't encode it. I think it does that's good. Why are you going to start website? Basically defaulting code? Google, google, that there's a really nice I used to use it years ago and I didn't know the command we'll paste in your token and we'll see if it gets the right value.

B

That's the one, the classic pieces of time right, yep, you encoding, yep click on that.

D

A

And it's a completely different, it's also different. It's completely.

B

Different okay bit weird, but this starts the same interesting. So let's modify our secret.

A

Yeah, so obviously we got the wrong commit. Well, there's, maybe that's the reason why the command isn't on the thing is because it's wrong.

B

Yeah, maybe we'll tell people go onto that website and go to seeker?

B

Okay, that's better!.

C

B

C

C

A

That could this one failed out almost instantly.

B

B

Do you mind what you just did there? Did you create the secret again and do the task run again.

A

So I deleted the the run I applied the.

B

Where did you apply the secret, though you just modified the secret on disk? You didn't apply that file.

A

Dope, um my bad my bad.

B

I was daydreaming a little bit. Thinking is my date going to just turn up without telling me and I'd have to stream it early.

D

I wasn't paying.

B

Attention, and now I'm back just I thought yeah should be this.

C

A

B

It have to just remember it's not a resource uh bad could. Is this the right one by credentials.

C

B

No say it ain't so.

D

A

Oh, my goodness, all right! Well, yeah! Well, okay! So you know what's gonna, what's gonna happen here um all right uh here, let me let me send you this and I.

D

A

You I'm going to send it through slack, and I want you to um try this yourself once just humor me and go through the steps and then um how are you so there we go. You try it yourself on this machine and then being that we have less than 10 minutes left where you got to go.

A

What I will do is um prep the path start working on the pr and I'll keep the stream going or not I'll stop the stream, but um after 10 minutes, uh but then I will get the pr going and I will publish- and I will send out a tweet um with the uh replay link of this with with the pr when it gets pushed up. How about that yep?

A

Is it a reasonable thing? Yeah.

C

A

Know in the world we live in right now. um I I cannot keep you from from the opportunity to spend time with other humans based in real life, that that would be just wrong. It'd.

B

Be really nice if we could just encode this secret jj.

A

Well, you know that might be asking a little too much right now. I'm.

B

Doing the same thing as you.

B

So I'm literally oh look at that right token. Is that secret? Is that do that great and then configure you again start right, then delete test runs and then apply. The web hook run.

B

There we go and then okay get pods we're up here somewhere. Do the grip we create completed, get blogs bad credentials jj if you're talking being made no longer valid by a chance.

A

I mean I can give you another one. Yep.

B

A

Hang on delete, yes, create and again just to verify. It is public repo and admin. Repo yep, okay, create token yep copy.

C

A

B

You go yep and I'm encoding that as we speak, okay, I've just done that. I'm now updating the secret. So I'm going to here and I'm going to I'm going to do that, I'm going to do dd and I'm going to go back right there. You go cool, I'm going to apply you the real secret right done that and I'm gonna delete and into some test runs.

B

I'm gonna kick off the web hook run again. Here we go then we're gonna do k, get pods again pipe, create.

A

Here we are oh, that one's taking that one, that one didn't stop instantly.

B

Did it work my credentials? What I just doesn't work anymore? Are we in the right name, space.

B

B

Probably k get secrets.

A

Yeah wait 15 minutes ago.

B

B

My secret just yeah it's now: it's working.

B

uh We'll pipe more.

B

I think I went past it at the top secret and then the token does that match what I copied. uh No, it doesn't nope the t, the actually encoded token it's out to the y ends in two equal signs that.

A

B

Wrong we had to get that secret.

B

And where am I am, I definitely in the right name, space yeah, but keeper nest comes up with. That is that the site yeah.

A

It's just a um selector there. It is.

B

Okay, because it's green okay, fine, fine.

B

B

There you go worked. What can't you read books.

B

Please apparently, it.

B

Worked nope. Well I say it worked. I didn't see that error, so let me just have a check. So we connected to github.com.

B

We always seem to end up with like weird issues: the golden.

A

Truth were not a.

B

A

It's really not bad.

B

Credentials, oh no, but it wasn't at the end. Oh my gosh blind. I didn't see it down here. It looks like it tried again. I forget the secret again.

B

That's the wrong value token.

A

Is it based on coding it again 65.

B

A

B

That's a good point if I, if I put that through the decoder.

B

uh I'm just putting it through the website again: yep yep. It is so maybe it's not basically encoded.

A

Maybe because we saw it, we thought we did it that way: okay, so bring it up, yeah bring it bring it up and put it put the webhook secret in there again. With the actual token.

A

Okay, what the hell man.

B

So this time we offer a non-encoded token yeah, yes, yeah. This means the doctor writing two weeks ago. Didn't really happen, but two weeks ago did happen.

A

Maybe it was the secret we needed to base encode it.

B

Oh yeah, actually maybe but.

A

We wouldn't know because it's.

B

This this could be the one jj.

A

Like am I going crazy.

B

Are we all going crazy? I think we.

A

Are wait? This doesn't.

D

A

Sense man, it doesn't.

B

So, where poker on oh the other career, it's your fedora pod, it's bringing down there, but the resting car, okay, logs, hey! This looks different.

A

What's the hell man.

B

A

B

A

B

You in code, one not the other.

A

Well, I mean it's just arbitrary string right. The the secret.

B

Oh yeah, why don't we even encourage that.

A

Yeah, we don't even need to do that.

B

Yeah, that means the docs are good for secret creation. Is this.

A

Yeah there you go yeah, look, the secret is just it's just arbitrary, so so yeah we don't we don't. It turns out yeah. We don't have to encode it at all. We should probably make a note saying: don't encode this, because.

B

The thing does, two weeks ago we went down this route, but it's your website now green jj.

A

um No because we don't have the ingress right.

B

ah We deal with the ingredients, I created the ingress for an earlier remember. Why did k get ingress at the top window.

A

I'm sorry here I'll get you there. Yeah.

B

Yeah you're right, I've got no english.

B

So now, if I do ingress run.yaml yeah, okay and then can you read over that web book? Do a push to the repository.

B

Yeah you still push because there's nothing to redeliver. I guess so. Just change the readme.

B

And then we have all the steps finally figured out.

A

I don't feel like, I know what we did, though,.

B

uh I got a good idea, basically copy the ingress c cup after getting the c cup incident. Oh.

A

It's a push we gotta do an actual push to. It. Hang on.

C

Not just admit to read me.

B

uh Well, I'd like you to commit on the readme and get up yeah.

A

But it's not a push, though we gotta push to.

B

A

B

There it is, it is a push that should work.

D

C

B

Yeah but it should definitely work. Oh no.

A

B

A

D

B

Yeah yeah, so you did commit.

A

Commit direct mastery.

B

Yeah, so I'm wondering if um oh much computer man if.

C

B

There you go back on me: cool do um yell.

B

Do we have any pods to like handle the actual event itself.

B

That's always that's just me ignore that and walking level set.

B

Do we have any trigger bindings?

B

Do you have any pipeline runs.

B

Test runs but we made the web hook. Oh, is the ingress changed? You see.

A

Yes, yes, yes, this! This one is um oh, no, no, it said event listener. This is.

B

Demo, ah so for you to change that to event dash listener, just for now yeah for change on your github for now cool and then update and I'm just doing a little posture again. Hopefully that then goes.

B

B

If you can hear those birds, oh.

C

B

There's a feast in the field wow so did that actually trigger it at the bottom.

A

B

So event dash listener is the rest of it correct jj. It ends in four zeroes dot. U s! South! We just compare the url.

B

Yeah, okay and if I just get the logs again for the listener over on my little teamwork session, there's nothing new popping up. Can we curl yeah? I can kill that yeah go ahead.

A

Things something happened, oh.

D

A

No, no, this is the. This is the uh the four. Oh, it's not listening. Yeah.

B

That's when you've, not if that's when you're not done the secret.

B

Okay displays the little default four four page, because it's not rooting to the el and then to the underlying service. So it's not hitting the ingress. Is it.

A

So that's the ingress seeker right there. So if we do.

B

Yeah, it's like it's not rooting to get through the steer with that listener.

C

B

Rafter head off from one minute jj so hopefully we'll give it one more try and then wrap things.

B

A

B

So we do have a tls secret. You think the secret might have changed since two.

A

A

Please apply your changes to the latest version and try again so hold on. So if we do um okay get secret web book.

C

C

A

Come down here.

C

And as default.

C

A

um Okay, that's fine I'll, keep hacking on this. Maybe I can come back to it later.

C

B

A

Fine, it's fine, also working on pr um and I'll. Stop the stream. uh Do you wanna? Do you wanna, wrap up by saying anything yeah? I can do.

B

I think you know we're trying to put down the golden path again, but something's bitters, I'm not sure what at this point as you can see it happens, you know we go through again started page and we thought we had it all figured out, but our assumptions were wrong and as if double checking it's.

A

Also, it's also possible. We had because the cluster isn't a dirty state right, because we had something there. Maybe there's something sticking around that we didn't know about or something like that. So.

B

Okay, I think either way it's probably going to be- maybe the conclusion protect on weighted streams directly using text anyway, I'm thinking next time we might try jenkins x, so maybe we'll try. You know using it from scratch and writing a pipeline or learn some examples. I think it uses text from of the covers for its pipelines. I'm not sure that'll be very cool to do actually um we'll figure out the bottom of this issue, the piano I guess and then yeah, hopefully, look at jenkins x, see some cool things sounds.

A

Wonderful all right! Well, uh thanks adam and uh we're if you are watching this live uh we target uh every other week, so not this week, um which is the first we are targeting. The my calendar would move the eighth uh to do this again. um So hopefully you can join us again and tell your friends um because we'll we'll just we always like to have a conversation while we're doing this.

B

Yeah, hopefully things just work out the box, but, let's be honest, I probably won't so.

A

Thanks for jinx jinxing, us thanks, but thanks for taking time I've.

B

Got a back question so I'll say it won't work. Maybe it will there you go all right, then you have a good day. Sir. Thanks folks see you later.

B