Continuous Delivery Foundation CDF Twitch Channel, 27 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Twitch Stream number 8 2020-10-27

Description

Adam and JJ continue to try to get Jenkins-X working on IBM Kubernetes Service, and succeed, up to a point :)!

If you've ever wanted to see jx3 running on a production Kubernetes Cluster this is a great walk through.

A

Now that should be live here. Let's see yes, there we go wonderful, hey adam, hey jj, um so time zones.

B

A

B

And I had to find a suitable t-shirt to wear, and hopefully uh you have fun out of this. T-Shirt has arrived that was sent as part of being a speaker cd card. So I'm very.

C

B

I'm proud to walk the tech ton t-shirt, which you can buy from our cdf store. But that's an aside.

A

Oh, it's good stuff, man, that's good stuff, um so yeah! uh This is uh officially the eighth, so it's safe to say that this is truly a habit. Now um the cd uh foundation, twitch stream, uh I'm jj. I work at ibm as a developer advocate and you are.

B

I'm adam I work at ibm as a product developer.

A

B

Special things.

A

B

Sometimes you didn't take it on and jk um you've got some news. Haven't you.

A

B

A

Was made something weren't you? Oh that's right. Yes, um the the the blog post fisherman out. um I am officially a cd foundation ambassador and uh thank you adam for pushing for that to happen. Excellent.

B

A

Yes, that it means a lot. It's a nice little feather in my cap, granted I'm not wearing a hat. um I have a red hat behind me, though.

A

Hey there we go um and uh that's that's a it's a good honor, uh and it's it's one of those things that you kind of, if you've, never known of what an ambassadorship is it's one of those things, um the uh it's a good way to kind of, say that you're doing good work for for foundation or whatever, um if you've ever thought about if you've been part of the foundation or like you, help out with projects around um continuous delivery um like tecton and and and jenkins x, which we're going to play with today um uh getting go going through the process of becoming an ambassador is always a good thing.

A

um They acknowledge you do the work and then also you get resources from them to do. Cool stuff um stickers are gore right. Is that right.

B

Yeah not just stickers, but you should be getting uh a nice big welcome pack as well. I think.

C

B

Be a t-shirt in there, so there.

A

You go awesome, um so we uh last last time we streamed. um We, um we finally got jacob's x, actually playing with uh mini q, which was pretty damn cool as soon as we got our head wrapped around it, and um we actually got everything. Kind of pulled together uh turns out jenkins x is actually pretty solid.

C

A

Is there is a happy path to it, um which is uh obvious, because I mean it's, it's it's a constantly moving moving project uh but, um as I started uh continuing playing with it, um I did a follow-up video on the typical um workflow that a developer would go through instead of setting everything up like actually interacting with it um that if you're interested you can reach out or just find it on youtube youtube channels, uh but it turns out it was. It was pretty solid.

A

um The next challenge we're gonna have is that was on mini cube and um a lot of the issues uh adam. I don't know if you've seen him or not, because this is actually the first time adam and I have talked about this- um uh I really I put pretty much issues in about the the just the sharp edges. I guess is a good way to describe it um that we had and it turns out a lot of the sharp edges was due to mini cube, um the actual mini cube instance.

A

That runs is very, very underpowered, because it's a development environment. It doesn't need to be production quality by any standard. um So I thought it would be a fun challenge today um to just spend an hour or so um trying to get jenkins x with the mini cube instructions working on an actual kubernetes cluster.

A

um We tried this already once it was a disaster, um but now that we're seasoned veterans, if you will adam yeah, come on come on, give me a smile there you go.

A

um I think I think we both can kind of just just run with it and and kind of walk through the process seem reasonable.

A

He's speechless he's speechless.

B

Well, richard, I think what was problem that we had last time with iks: do you remember what it was.

A

I really don't I really, I really don't and being that there's so many iterations on jenkins x, like we can't say that we're going to be running the same code like it changes so rapidly and they add things to it so rapidly. Is it I, I don't think it's safe to say.

B

It was definitely a disaster, but it's so basically you need to be able to start thinking as hell.

B

A

Go for it, I think.

B

I think I don't mean to remember, but I remember it was a disaster but yeah now we know what we're doing, and hopefully you can get a nice english template because we basically learned that web hooks are really really really crucial for jenkins to work. That's what we learned. We went down to know web hooks when it was a nightmare, so we can get that end point. Maybe with matthews n clock, I'm not sure. Maybe we can admit ain't glock and just use the ingress at some point.

B

Yeah, let's give it a shot. Okay,.

A

B

Nice big custom as well jj like really big.

A

It's a it's a relatively big one. I mean I, I know some companies run production environments on this cluster or not this specific cluster, because.

B

Oh, this customer, okay, all right.

A

um If you wouldn't mind us snitching into the box, while I share the screen, so we both can type because god knows we get frustrated when one of us can't type properly. uh Okay.

A

So let's me share my screen zoom. Why are you being mean.

A

There we go, there's your screen.

C

A

Take that off and then desktop there we go so that should be.

A

Everyone should be able to see the screen. Now, um okay get ns there we go so we have uh there's a handful of things on it: nothing's actually running, which is fine. Okay, um create an s jenkins x, so n s jenkins,.

A

X, so now we're actually in the name space, so we don't worry about stepping on each other, which is good.

A

um So, as you see here, the the just just uh if you haven't seen this yet um I just kind of want to make sure that this is the step we're going to go through, uh which is which is the ginkindex instructions for minicube. There's, no reason why this shouldn't work on um iks, uh ibm, kubernetes service, uh ibm, qna surfaces, very, very vanilla, uh which is actually one of our our pluses.

A

um So um we try not to make too many things different, so you should be able to take something from minicube and put it in iks, and it should just work um as you see here is four cpus uh with eight gigs of ram is what you're supposed to both mini cube with this is like us, I think four by 16 worker notes and three of them. So it's a relatively bigger instance and being the mini cube, is only one instance of um kubernetes.

A

This is spread out over three different worker nodes, so the scheduler will be able to give out um the different pods because there's like a trillion pods inside of jenkins x's, we discovered that was a joke. um So hopefully the schedule will be able to level set it across the whole cluster, so we should actually see better performance, which is the ultimate goal sitting there. If you watch the video, it took a good 20 minutes for everything to churn through, as it was walking through the process. um So that's that's a disadvantage anyway.

A

Let's continue on um so I'm going to go ahead and just start from the very beginning. Unless you have a objection- adam nope, okay, so um we'll do this as uh aspire labs um jenkins.

A

X, tobacco and then cd, okay,.

A

X, click clone.

A

A

Copy there we go.

A

My insulin pump is telling me I'm having problems, which is always fun all right. So um now we need to configure our ingress domain to point to this, the equivalent of that. So, if we do, if we look at our ingress domain here, js cluster get, uh we have this one already, which is nice right like this is actual ingress subdomain. So I should be able to come in here and do jx rjx installed. I do there jx update command. Do we know?

A

Okay, um you want to pull this. The newest down anyway, just be on safe side.

A

I feel like I'm talking a lot and you're, not talking at all adam.

B

Well, I'm walking around and I can see those commands jake's upgrade, but I really can't believe it's not on an update command. Why are you doing it? I was searching because it was on, like I think there were like 20 or 50 version changes like in the past few weeks. So how can I figure that out? But I can't really see anything good.

B

I just literally don't want to buy them. um What's your session name as well, jj for team looks please.

A

uh Jake jenkins x, all one word. Thank you.

A

A

A

Give me two seconds: I'm sorry.

C

A

User, local bin, yes good and I'm not watching the chat. Actually I have that up. Okay, uh jx all right. So of course we don't actually see the release version. We just see cl3x, but that's that's here, nor there all right so back to what we were grabbing. Yep.

B

So you've got the ingress domain. Did you set the requirements file to use that domain yet.

A

I was just about to do jx get ups requirement edit. ah I do like splitting my windows. Life is better when you split one windows hit ops requirements.

A

Edit don't mean that.

B

Okay, so we're emitting the weight nipped il thing. Oh, is that an error.

A

Yes, because I'm just in the correct directory, okay.

B

Right so you've got to be the director of the githubs repo. I guess.

A

And if we're here get this there.

C

A

A

There it is there's our domain as we're.

C

A

um And yeah- I just completely walked past past that instruction um all right. So we need to set up ngrok for this, but we shouldn't need to because we actually have.

A

We have an actual endpoint.

B

Is that reachable by anybody, though, so, could you or I curl the endpoint? You should be able to yeah, um okay, I'm going to copy that and just do a little ping uh on the sides. If I were to do, is it okay, getting us all named spaces maps? What was the plan that you just did jj that got you that nice, english.

A

It's a cluster, yes,.

B

That's the one: okay, I'm gonna copy that to my clipboard. While you do the rest of the things, so it's the sub domain. Now, why isn't it? Okay? I've just got that. Okay, okay,.

A

Go ahead yep, so I'm going to go ahead and put this in the ingress cuz the hook for this, which should be reasonable, yep, so copy the charts copy.

A

If I can only copy and paste and that- and this is the hook.

A

There's a uh hip-hop joke about that in there. Oh.

A

Oh, I'm an old man, um all right, so get ad period, get commit, dash m fix, configs.

A

Get push origin master, origin, master.

B

So I've just verified that I can get to your endpoint, but there's nothing there. Obviously, and I do believe we might have to use that ingress secret somewhere later on.

A

Okay, it should be pretty standard which is fine, yep, all right fixing it we're pushed up into the repo okay. So now we're doing the install the get operator.

B

Now do we have one already installed from our miniature.

A

Debacle, pretty sure we don't okay, I'm gonna pull this one over here, because I'm into deleting that uh as I've as we've learned many a time adam um save those tokens, but on.

B

Another window.

A

So you delete immediately after streaming.

B

Yep definitely.

A

And that's new that wasn't there originally.

A

Yeah, it actually filled everything out directly for me, which is pretty damn cool nice um all right. So then, jx admin operator, user, name, jj, asgar.

B

You know what page talking than that. Do you.

A

I'm going to say I have it right, open right now, I'll just delete it anyway,.

B

Okay, I just wanted to did it without the token, would it be interactive and give you a prompt that was.

A

Oh um well, yeah you'll be prompted for them. Yeah.

C

B

Okay, adding missing home repo and this bit, I think it did a heck of a lot of things. Remember one thing that we learned in the last lesson that last lesson last session was wait. I remember you had a full request and we suggested making some coffee in the meantime. Just.

A

B

This did a lot of things like 10 minutes worth of things and the quick start as well required. I think 10 minutes more of waiting. So hopefully it's a bit more powerful cluster and I have to wait so long, but you'll feel patient and I do hate being patient. But I think.

A

B

Does anybody really like being patient about? Why wouldn't.

A

B

C

B

If you're a professional procrastinator, I'm not sure that pays well, though,.

A

No, it's true, but there's.

B

A

The drinking space right now.

B

Well, that's a bit weird.

A

B

ah Oh, the namespace jx gift operator- oh, is it wait? That's interesting. Has it moved? Is that.

A

Yeah it made its own.

B

Okay, so let's watch that namespace, I don't remember jake's kit operator, maybe that's a new feature. Oh.

A

Yeah, that's uh so they they got smart.

B

Change it every day, yep, maybe now it won't even take so long or there'll, be a nice little coffee cup ascii, as it says, yeah.

C

B

Things please wait there, you go okay, okay, so I've got a new namespace and it can say init one. Okay,.

A

Things are happening. Okay, so that's all looks like it's coming up. Yep, that's good!.

A

Now we're doing our home.

B

B

I wonder how long it's going to take so are these images cached already no.

A

No we're going to work with them.

C

No yeah they're directly down from there yeah, but don't forget we're this is in the.

A

This isn't a dc with like super fast internet access, yeah.

B

Certainly right, I'm just wondering, because you know we're starting this at let's say 11 20 for your time, let's say: 11 23. If now I should know the time from you know: zero.

C

B

Is there something cool or they can say, hey it's working so so far it's been two minutes yep. Obviously you don't want to do this all the time. It's almost a one-time thing, but I'm just curious from a test perspective.

A

Yeah, this is very much a one time, but I I'd be really curious to see if this actually finishes, because this will be a really good video just to share around showing people how to get this working on an actual kubernetes cluster yep.

A

B

Are you seeing when the cube's not an actual configuration.

A

Shots fired over here.

B

C

B

If this look at those really big images, though, because remember I think the jxcli was like three gig and there was like a node start, one that was like two in a bit. So it's.

C

B

Be quite beefy and quite chunky, but again maybe that means it's quite powerful. So we've just got a lot of cool features, so this is all helm stuff, more more more helmy stuff.

A

Yeah still just chugging along, let me make this a little bit bigger. So it's easier to read.

B

So you've only got two pods in that name: space on the bottom.

C

A

C

B

Stuff going on, uh I guess anywhere.

A

Secret infra just got created, it looks like wow um same as with production and staging oh. We made those environments already yeah, which one, which is that's, no, that's yeah they originally. When we did this a couple weeks ago, those did not exist. They.

C

A

When you push something from staging into production or something into staging so they're they're pre-populating this stuff now.

B

Because probably know that you already had a quick start because who doesn't want to do a quick start yeah here we go now remember those are benign errors after a while they're resolved. I think it's because some y and others uh and eventually they'll all pop up.

A

Yeah, it's like it's like a race condition that they're all people.

B

Yeah yeah, maybe yeah, maybe maybe it should be a stateful set but x, then y or z. I've never used them, but I heard they're pretty cool, but I guess it's just weight and eventually all will become healthy, and this is in the exchange place. Is this thing jj this.

A

Is jx I moved into the jx namesakes because it looked like it works what's happening there.

B

So you have pipelines visualizer now, hello, I've never heard of this before in my life. Oh, have you heard of this before.

A

B

I think we're getting some new stuff here.

A

B

So I'm going to go on searching github, it's playing visualizer. While you do that, because.

A

That's something.

B

A

Our secret infra is not happy right now, but that's fine, that's fine. It looks up there. It goes.

B

Okay, so I'm working on jx cli because remember jxcli is the gx3 stuff which we're playing with okay, see it just jx is version two. I think.

A

So I'm gonna search.

B

For pipeline visualizer mean that's in a separate place, I'll report back with anything that would be fine. Hopefully our customer installed still going well.

A

A

A

It's amazing how easy it is for zoom just to get in the way a little drop down thing.

B

Yeah so so jj I've I've found jake's pipelines, visualizer right.

C

B

Yep, it's a web ui for jenkins x, the clear goal virtualize the pipeline and mail logs. If they start in september 2020, which had a couple hours work, is deployed and used at daily motion. There is an announcement blog post from the 23rd of september boy did we. We must have just missed this when we streamed, um I don't know why we missed it. uh It says why are you a new ui he's already announced someone's already protect on dashboard as well, so this will be fun to play with. Hopefully, we can see that.

A

And it looks like our git operator has been pushed up. Our friend, pow devops 2020, is is back in the repo.

B

A

Thought that was worth it. Oh.

B

um It was started daily motion, so it says that daily motion started this ui to visualize things. You showed objects community, so I think it'd be really nice when if we can get it working drink his ex and visualize a pipeline, if we.

C

B

Great victory, I.

A

Agree, I agree and I have a feeling- it's probably not in this quick start and or the doc so we'll end up. Writing it ourselves.

C

A

That was me being a little bit facetious um okay, so we actually didn't actually get to the point where we had to write the log, because it was actually telling us what was going on pretty pretty um exquisite, which was nice.

B

It's better, it's good! Yes,.

A

B

A

ah Yes, okay, so now that we've done the once it's following command: that's fine! Okay! Let's, let's create our our quick start project again. Do we not enter that port forward? I don't think so, because this is all.

B

The proper end point yeah. It's actually.

A

Okay, get in grass there we go. We got real ingresses here. There's our whole.

B

Jake's pipelines visualize, it's got an end point. Can you go there? Please I'm excited already.

B

There's a takedown dashboard maintainer. Oh.

A

Crap, um oh it's port 80! So it's probably not going to https.

A

Oh things are happening: hey hey! I'm going to hit the button you're not going to hear it excellent! I'm going to figure out how to pipe it back into our audio. Wait.

B

So did you just.

A

Say it instead.

B

A

Nice, okay, so.

B

That's interesting. Yes, let's, let's do some stuff, maybe make some make you do a quick start. I don't know how do you know if red pox are working? I guess we need to make a quick start project and see if we get agreed.

A

Yeah but check this out, you have it built its own docker registry, too, classing yeah. So so by installing jenkins x, you get your own docker registry. I.

B

Bet, that's a secure one as well that only you can play with.

A

B

If you go to that url it says login. So why don't you.

A

That would be amazing. Like that's a total, I mean. Obviously you need to be http, but that is a okay. That's a really nice hat nice! Oh wait! No nothing's happening.

B

Is the pot healthy are we? Are we being celebrities?

B

Maybe you've been selling, there's no ui food.

A

Yeah yeah it's running so.

B

There is a little guess right, there's no ui! It's just like a thing. You can push key map. Maybe oh, but that's that's! Probably you when you hit it you're using firefox. I guess yeah.

A

That's that's the health.

B

And readiness probe, so there is a website all right. Let's keep going then this.

A

B

It's very new, very, very different from our last experiment.

A

I'm like I'm actually getting like a little giddy here over over over here.

B

Just those of me free things, it's just free stuff below exactly yeah quick. Is it christmas.

A

Time already, this.

C

Is just good yeah right, it's just lots of free stuff.

A

Project hey here we go.

B

All right we're.

A

Ready uh we're gonna go.

B

With jj asgard- oh remember, you don't want to use 2fa.

A

B

A

Git token, this guy, which I'll put over here again.

B

Yeah because remember we had an issue last time.

A

Yep, it got real angry yeah. We.

B

Tried to use justice keys and it was like nope, the url contains a call. One can't do that and I think we have to use https uh of our tokens instead.

A

All right, hopefully, this will work.

A

B

Hey! What's in blind cart with hulk.

B

A

Let's do let's stick with going again, yep put it in my name space. um I think asgard was jenkins.

A

A

Well, yes, I would thank you.

B

A

A

B

I mean the catalog folder, that's interesting. What.

C

B

Folder, what's the catalogue, I guess you should have clicked on the question mark.

A

Well, I was worried, it was going to break it.

B

But so there's that token being printed again, so there's two little exposes there, but you can use an issue for that one. So that's saying in value is my password.

A

Oh, it's because the little percent.

B

Oh, you, you put a white space at the start and it said, what's your token, so there's three things there one should do the trim two. It should not tell you what it is when you put it in three and the other, so you shouldn't display it. Okay, there's three.

A

Issues, do you want to take some write down that notes real, quick, just.

B

I'm raising an issue instead, I don't. I don't use writing down implements I'm going to make.

A

An issue right now, while you put.

B

The right token well.

A

No I'm going to just tell me when and then I'm going to delete it and I'm going to start over and use and try to make sure I get that. No, I have that. Don't have that white space, okay,.

B

A

Wait what so, but surely adam roberts and jj asgard became the qa for for jenkins.

B

Yeah, I'm gonna.

A

They better pay us some time. No, I'm kidding I'm kidding stickers. That's all we need.

B

I'm just gonna make an issue now uh gonna say doing a live stream with jj um watch your version by the way please jj.

A

That is a great question.

A

A

uh 30659 all right thanks, alright, so rmrf.

A

Jenkins looks going.

A

Copy all right.

A

A

A

Oh so it had the right steel to create it, but it didn't actually what that's so dumb. um Let me delete it. Real quick, hang on.

A

Come on computers, do your job!

A

Oh! It's! A price initially starts as a private repo.

A

A

All right, that's gone, no questions in the chat in case you're, wondering.

A

A

A

C

A

A

um So we need to change this.

A

There we go and if I.

A

A

That's the problem, oh so they're looking for the actual like get credentials file and because it was already there, it didn't ask me for the key again. You see that right.

B

A

So if I go ahead and cd rmr asgar lab string context going and rmrf tilde gets credentials now, if I go back to quickstart yeah see now it's all like. I can't do anything. Oh please, copy paste.

A

That should be a.

B

White space of the stock jj- I don't that it is the control a, but it is.

A

uh Controller didn't work surprisingly,.

C

A

B

That's weird: well I mean it's the enviro.

B

A

Go to the previous.

B

A

Nope can't get.

B

Up there, I think that's there's too much space there for my liking.

A

Yeah yeah see you're right there. It is you're right there.

B

Yeah, so we're scared of that. That's just garbage in garbage. That's you're not copying it, but I've raised an issue because that should be trimmed froze.

A

Yeah there we go so then we can come back here, quick start because we have our credentials. There everything's happier now yep put this there and then that one scar labs I already recreated.

A

I hope I didn't.

A

Profile, where are your profile?

A

I've been trying to audit my github repos, because I have like 420 now: oh yeah 411 about 20. yeah. It's a it's a lot, yeah! No! It's just because I keep forking things and I just don't. You know.

B

Yeah, it's a good practice, get hygiene and also dr registry hygiene. I know I've got a heck of a lot of image and docker hub that I don't really need to have up there if it was a nice book delete friday. I'd be a happy man.

A

Or for that matter, just like bulk archive everything right and then, if you actually have to come back to it, you come back to another time.

B

Yeah I mean you could just compress it somewhere on some little file server, yeah, that's.

C

B

Might be handy just so it's not always there and visible in the way.

A

A

This is looking.

B

Better yeah, I think, last time when it said catalog ford, I think it said build pack, but now it says from impact detection, so maybe catalog something else and it's techno catalog integration for the pipeline. I don't know, but maybe now should go to our pull request.

A

Yes, so if you check out this, it actually did the correct pull request. Sorry.

B

Well, that's f is done, do you get excited and lock us out.

A

So um if you see here, we have waiting 20 minutes, that's fine, but it actually went to the correct repo this time from to import it from the repo that we're not doing, which is that remember we had that weirdness originally, which were like. Why is it doing it this way? Well, it's because get ops. All the configuration for jenkins is in this getups directory and we're now importing another project into it, and now we're running our pipeline for this thing to do that. Work.

A

um Okay and that's fine dco is just me being bald yeah, um but this is really cool um hold on. Does that mean we can actually see the logs yeah? We see the dashboard here we go there, it is there, it is hey adam. Are you happy now.

B

A

C

B

Think so um is this: ah this is the pipeline visualizer. Is it.

A

Yeah is it well by clicking on the uh the uh by clicking on this details sends me directly to the output good.

B

Good good good good, what are the other options that were top right of that there's photo logs and yeah? What are these little things? Hey that was like protect on dashboard, okay, let's see dark component, uh what starts up left bone.

A

Top left, this is the the status I'm assuming like, where it.

A

Is pr one and that's it really there's a nice search bar.

B

Yeah, I'm oh well, I'm gonna go and find the code. I like the look. I don't.

A

B

Takedown dashboard things, because we did a lot of work to get those vlogs and do all the things that's good, I'm glad they've got it in there. It's all linked up nicely as well.

A

There we go, things are happening.

A

Not seeing done yet.

A

Verify successful.

B

I've just seen some changes back james, going in fix at a tech time, dashboard style path for pipeline runs and there's another commit which is support, tecton dashboard style, urls, so good. I think they've worked our code for the text and dashboard and made it awesome and then scratch.

A

B

A

Now, let's I do want to just throw this data point out there. When we ran this on mini cube on our box, it took a good 10 12 minutes right yeah. This is only three minutes on an actual production environment. That's the.

B

Best logo point and the web hook stuff just worked, didn't it.

A

It really did it just worked with with um with our iks ingress subdomain.

B

uh Hold on, I think so, wait wait. Has this one a callback yet to the server, because you can go from you to the server without web hooks. Remember so under settings hooks, let's see if it's a nice green tick there.

A

B

There is this a new web hook there. It is fantastic good, so it's been, I think the timing was uh 24 past. It's been 22 minutes from hello to hero well from from uh inception to hero, so.

A

I wouldn't say fully hero, yet we've now created our jenkins instance. We have our giveaway.

B

Yeah we've imported a project.

A

Into it, we haven't actually done a pr against the project, which is that's the real real end. End story.

B

But we kicked a protect on pipeline that we could visualize and get the logs for yup and we get everything installed on a real product cluster in less than 20 minutes, and now our developers could go and make their apps and do their thing with pro and web web hooks and get ups and good practices.

B

And uh you know happy days, yeah.

A

B

A

Neat like it, I do find that weird, oh wait, no hold on this is for this. Is this? Is a nice? Oh? Actually, that's really cool if you think about it. um After committing everything it outputted the law, the the commands, you would need to actually see what was going on, get big enough.

B

To go and find it and giggle it and look at the questions.

A

Yeah so let's copy this and then put this over in a note over here just so, we have that for a little in a little bit.

B

Yeah I've always said ideally, approach should have no documentation. It should be so good. The african docs, but if you did have to go with docs, tell them to me when I need them. So that's handy good. All right.

A

So here's our going it really is. It really is uh okay. So if I come back over here back to my profile.

A

Back to my repository, we should see oh interesting. It starts as a private repo.

B

Yeah, maybe you don't want to share it yeah, maybe it's secret.

A

um So, let's see where this guy this so this is the actual first master release.

B

When you say release, is this a build and then a push and then uh publish to the helm chart? What does the release mean.

A

Is I believe it's it's it's! The initial like this is version 1 of 001 of everything. So if you look here back to that, being that it's a private repo, no releases kicked off the build pack to make sure everything actually builds, how we want it to so now it's waiting on git clone. So if I come back over here and then look at the pipeline activity.

A

There we go so this is. Oh, oh, remember, hey hey already. This is better remember. This was all like broken and you couldn't really. You could really tell what was going on.

B

A

Is an odd one, yeah yeah, it actually walks through the whole thing. That's cool this.

B

Is going to all okay? So when I said what does the release mean? It's going to be this stuff here, it's going to be a clone setup on name, two merge next up: okay,.

A

So then we should be over here here we go, that's it all doing that that work over there. So when this is finishing building the actual container, we should see.

A

I'm assuming 001 released.

B

I think you're going to get a github release and maybe a helm release an actual pods, and then you can promote it by objects, promote at the bottom yeah. It says that home release you can promote it, then from staging to production or from from yourself wherever you are to staging and then give it to your friends tests and then production when you're happy.

A

Yeah wow: this is really so much better than we did last time.

B

A

Now granted granted um because we have the scars from the first time of doing it and not understanding what was going on. This is to us eons, better right yeah, but I could only imagine like I'm still curious. We need to find someone who's never done this before and go through it themselves to see if they have the same reaction that we do trying to with you. The excitement around this does that make sense.

B

May I can be our homework, we need to either find some guinea pigs or, if you're, in the chat or watching it on youtube or anywhere reach out to us. There's a sectional for the continuous delby you can find it through the website. I believe, um if not maybe you find jj's repo. You can make it public or jxcli or jenkins x, slack yeah, more guinea pigs get in touch yeah.

A

You see that the the chart repository is actually a local chart. Publisher too,.

B

So it's going to be a local home release and then we're going to add sub charts, I believe for each subsequent version, so they're all belonging to the same one big thing. So I think we do just get applications that will be a mapping to one giant home release with various sub charts. Because remember last time we had like a staging and a production view on the applications of dawn, unique urls.

B

So that's how we're doing the grouping it made it quite easy to developers to uh try things out in different environments. It's a good feature. So what's next jj.

A

B

There's nothing there yet so you probably got helm somewhere. If you do a homeless stash to.

A

One second, I'm trying the other commands real, quick.

A

A

Let's try these build logs.

B

Remember but it was always like jx get act, act command as well.

A

I think this might be the same stuff from outside. Oh no! This is a little bit more verbose. Oh no! It's not so. This is.

B

Doing that is it my goal, build on the docker, build I'm going to do a google outside then put it in the container.

A

Yeah, that's what it's smelling like that's what it smells like: taking: a snapshot of the files. Okay,.

B

If they're doing that for the gold, but it's kind of weird, though, because then you're gonna have to make sure your os is on the same ones, your locker image. What is the cross compilation but sure.

A

By the way that get act- as you were saying, uh this brings this out where we are- we still see the status here, um ah but the second pr has been created. Oh no, that was pr build two nevermind, um so we're still waiting on the build to complete, um which is our initial build, which is fine because it started going faster. We were bringing we got overly excited thinking.

B

A

To go faster, but we've hit. We've hit some some cycles here and uh to your point that looks like the go: build command right there for the main.go to build it and then yep doing the push into.

B

uh What's the dockerfile look like for this, what's the from with a dockerfile, that's.

A

A great question scratch.

B

Okay, so hopefully scratch is a multi-arch image. She probably is. I don't.

A

Know about the os.

B

A

I'm thinking because there's nothing.

B

Yeah, I was thinking that because you're on linux over there on the left, there's some the gold building there, but has it done they go buildings? How to protect on task using a container or is it using go on the system? It's probably using gorilla, tectum container. So if you do k get task, perhaps you have like a go: build task in there using a jx image for.

C

B

Oh, you can't take tk and get. I thought you could.

B

Where's the build.

A

Happening, that's a great that was worth. That was my next thought.

B

Also watched jenkins x and what's jx jenkins,.

A

X was me: I gotta get in there um staging production kit operator, I'm not seeing it yeah.

B

Maybe it's building inject skill operator did get tasked in that jx get operator.

B

B

All name spaces on the end.

A

A

No, no! No! No. This was me playing with techton.

B

Oh yeah actually look how old they are yeah. So I don't know, I don't think it's using tankton. Yet.

A

No, but you did by the way, did you see the version 001 as we were discussing.

B

So is it what's being visualized if it's not I've typed on pipeline?

B

Is it a regular pipeline? It's not.

A

A groovy pipeline.

B

Is it, why is it I'm confused yeah.

A

I don't know how are.

B

We using tecton.

A

I don't, I don't know.

A

Like, where is our pipeline.

B

Right this way, if you did a vlog command of protect on pipelines controller, does it say: oh I've just reconciled the pipeline. That.

A

Well, you can try that in the background and when we poke.

B

Around I'll do that you play with that and I'll do the.

A

There's a helm file.

A

Make file shouldn't be anything too.

A

A

What is all this new.

B

B

Yep see what we are using, tecton we've got, task runs and rejects namespace and pipeline runs. We've got a jx release pipeline, that's still running as of 10 minutes ago, and there's some verify from build packs going on. So it's season tech time. It must be using tasks from somewhere. They've mentioned the catalogue earlier. I don't know if they've changed it all to somehow use it from the catalog.

B

There's also a pipeline called jx meta pipeline and look at that. Why you.

C

B

A

We're still stuck at taking snapshot of files and I'm still not seeing the pipeline.

B

You don't see in the pipeline still not seeing it no.

A

In the accidents- ah but this is definitely this dot lighthouse jenkins x, pull request ammo. This is definitely the um uh pipeline run. Tecton. Oh.

B

A

This is definitely taken from our catalog this. This smells exactly exactly like yeah. Here we go. Here's the actual pipeline.

B

A

B

A

There's a builder x right there there's a builder and pulls in cli to do stuff there. We go go builder from jenkins, x, right and then it does a bunch of oh. It uses kaneko to do it underneath it that's kind of cool.

B

Yeah, I think the first build pipeline had impact on this kanika, so.

A

If I didn't get.

B

Pipeline yep, I can see that.

A

Wow, the timeout is 240 hours.

B

That's pretty long, do you want to wear that.

A

One that's uh 10 days, no 24 yeah, it's 10 days. Your pipeline could run for 10 days before it actually times out.

C

B

First pipeline is taking a while, uh so we need to check our vlogs again so head to that nice visualizer.

A

You're still still sitting here.

B

What's it doing taking a snapshot file stuff.

A

Now I remember that was one of the things that said, we should go, make some coffee. That was that, wasn't that the joke we like, when we saw snapshot taking snapshot of files, that was when it was going to take forever.

A

B

Like that feels, I think you'd have mentioned.

A

That on your issue,.

B

A

B

Also, it says skipping snapshow and the copy it is taking snapshot. So it's copying what we've just built.

B

Yeah, so you should live in the jx name space and you should have to see.

A

So if we go into okay logs, this guy.

A

Every time, every time.

B

But it's not a part of them so that will have pods glass attachment.

B

Cck get bugs then get the vlogs to the test from pods.

A

You hear you do it.

B

Right so there's going to be some new task ones sitting somewhere we're in the get x name space. If I do okay get that there's this.

A

B

C

One of these two not ready for 14.

A

B

Remember I think I think this might be the one. uh So let's do looking things.

B

Right no apply, no push tag to get server. We're gonna follow those logs as well.

B

A

That's not what we're.

B

Seeing over here, but it got past this part so you're, seeing on the visualizer it's stuck at that.

A

Excuse me: yes, 15 minutes, so that's why we still are here.

B

Okay! Well, where we're up to is cloned by ralph checking out revision, fossil and request.

B

So why is it not ready I'm going to do a stride pod next, this fire pod says pulling image jenkins x. I o slash builder. Go, I think. Oh this happened last time. Remember this is not happening. Last time it successfully pulled image builder go and then it said pulling image again, and I said why is it pulling the image and then I did a docker pull of it manually and then I checked the logs again and it was pulled and it was fine.

C

B

So we'll do the exact same thing.

A

Oh pogba, maybe.

B

Yes, you remember, did this last time, you did it last time.

C

C

A

hmm Hang on hang on here I got it.

A

B

Do have doctor? Oh remember, you don't get to a docker socket though.

C

B

Security, so you can do that paul here. Your docker images pipe grab builder, go see if it's.

B

A

Hang on, we just.

C

B

You have to become the docker user.

B

How do we use docker on ibm card.

A

Bring up character, images!

A

Oh no! This is the t-max box. Just remember what this is.

B

A

Yeah but I do have docker on here, which I should probably turn off now.

B

Okay, so so we need to say, duck images on the real machine, yeah.

A

I have a feeling that might be a little more challenging than it's probably worth. um I think we just need to kind of hang out and wait. I think.

B

Okay, I'll look around the different room.

A

I mean still sitting in 18 minutes. Building this thing go, we have a tag. Oh, we have a tag, something changed.

B

Oh I'm pretty in the dark as well. You can't tell.

B

So you have a tag, so you have a release and that refers to.

A

We released this now 10 seconds ago, so this is there's things happening. Okay,.

B

So we're on the precipice of success off.

A

B

So, do we have a nice.

A

B

A

Creative pull request too.

B

A

That, when they get.

B

A

A

A

There we go: here's our staging environment, it's actually.

B

Yeah, why is it prefix of true? Did you put that in there.

A

B

That's not sure a chore to me is like some meaningless rubbish change. This is actually a big big big impact change.

A

Yeah moving it directly into staging.

B

I'm just a chore, it's so easy in jenkins, x, solid show. So what do you do next? Does it say waiting on merge or what.

A

Yeah no, this is now doing its verify right, which is expected. It needs to do its thing now. Yeah.

B

So what did uh what does our handholder supervisor say? Is that basically, what the docs say so, obviously a quick start command? We've got running in a shelf somewhere. That now says wait until foo. How do we know? What's your next.

A

uh Nothing really like we're still still in part for the quick start project, um we're still waiting for everything to.

B

um But did I command return from jx project, quick start and everything just control cd? I was in a tab somewhere, okay, this is this. Is it this? Is the show yeah? So this is.

C

What we're watching.

B

So you can see running, promote and just to confirm jj if you just scroll up all the way. This is the command of jx project quickstart. Is it.

A

uh Yes, no, no! It's the.

B

Does it get pipeline, maybe yeah.

A

But good activity, okay,.

B

Watching connectivity, okay,.

A

So as soon as this one promote, which is what we were seeing right, yeah as soon as this gets merged,.

B

A

Then we should do jx get um applications and we should.

B

A

Able to go to our staging environment.

B

And then he can promote from staging to production if you wanted to so we think they're waiting on oh.

A

Oh, we need to approve it.

B

Yeah yeah good, that's good, of course. So now we should do. Maybe slash approve seems reasonable. Yeah, hello chat, ups for them.

A

That should do it.

B

Well, I don't know they started in texas, maybe it needs to actual label.

A

Or maybe it's slash approved, I always hate that.

B

Nah, I have the label based, but.

A

Well, it doesn't, then, then it gives it. The label of approve.

B

In tecton, when you use a pro, yes, that's how I've got it set up on git, but I'm not sure if it sets up for you. I thought you'd get chat up, stolen.

B

There's anything in the docs that says to approve it, do approve you voice it, but she could say, add the label or maybe she's for themselves to review and then do a proof of.

C

B

Why don't you add yourself as an approver as a.

B

Reviewer there you go on the little cog up a bit up a bit.

B

Well, so what he could do is either make me a collaborator or you want the label approved. That's.

A

What I thought I.

A

Did it's regenerated.

C

A

So the second one verified and succeeded.

B

A

So if we come back over pipelines, I'm assuming oh that's pretty. You see that.

B

Yeah, so what goes at the top? How are they linked so aren't they.

A

A

Why are you not merged.

B

Because you need to have that approved label.

B

It's also got an x next to it: oh, okay, never nevermind yeah! So add me as a carburetor or at the approved label.

A

All right hang on. Let me do that.

A

B

Range access, yeah there you go yep all right, very good. I'm gonna go to github. Now I should get an email.

B

B

Notification right have you censor.

B

A

hmm It's interesting: they don't have the approved label by default creator, for you.

B

Okay, well, good news. Is I'm going to accept your invite, I'm going to go to pro requests and I'm going to take a good look at it.

B

I saw myself as a reviewer, and now I've got a few things to play with I'm going to just put a few little chat commands in just for a bit of fun, see what happens. Probably nothing.

B

All right so nothing there yet.

A

So it should be.

B

Slashed, I'm sure I saw something just done.

A

Oh here we go added that must have been slash approved according to the docs.

A

B

So you must be.

A

In the repo's file.

B

This piano is not approved, it's been approved by roberts, so your lowly approval did nothing but my powerful approval says it's been approved, um I'm not in the owner's file. Yes,.

B

Can you commit to the owner's file.

A

B

Basically, I wanted to spell.

A

B

Oh, this is come.

A

On drinking zach you're so.

C

B

I'm mildly over man, mildly. So are you making the audience final? Well now.

A

I'll go ahead and you can go and create it well copy to.

B

My tech on dashboard on this file so now for syntax all right: okay,.

B

B

So I've made you and I an approver.

A

So I think it is. I think this lgtm was from disapprove because it's me who added it right, yeah and then because according to these docs approve um because I'm oh, no, we're not part, I'm not. There is no owner's file.

B

Well, I've made it I'm doing. Slash approve.

A

B

Jj out of the approved label, did you so you're acting as pro, I believe uh it started. The approved label.

A

Oh there we go yeah nice, so.

B

That now it's in pipeline from the pack.

A

That was almost, there was only 20 seconds to win.

B

Yeah, so basically they should make the quick stats if the owners file.

A

B

A

Me see if it's an issue.

B

A

Yep so then this should be.

A

There we go now we're doing the release.

A

Okay, so that means we should be able to come over here.

A

A

B

However, there is an owner's file in the github speaker. Oh no, wait! What no there isn't I'm in the wrong place. Okay, enough, mine, there's! No way, I thought. Maybe it's pretty not that place. Maybe that's a better idea.

A

Yeah this one, this template needs an owner's file.

B

Okay, I've made that as well.

B

All right so, what's going on now, then.

A

Okay, so we've merged that's been merged in let's.

B

Get out of the pipeline.

A

Still waiting on our release, though,.

B

Now is that because it's a different name space- maybe it's under jx station or maybe it's a promote command.

A

No, no, we don't need a pro. We just need staging first right now: okay, okay, get an s, so we should see staging yep.

B

I think we've got pods in there.

A

There you go, no, no.

B

So what if you do a helm list all.

A

So maybe if we come back to jenkins x, dash, go away.

A

This has been released, it's tagged, so we are still in.

B

A

B

I'm right so jenkins, x, on its own, didn't, have an onus file, and I made one jenkins x: gohan is where your goal code is that this is weird. Is it I think it's mirroring between repos, I mean I'm going to ping you on slack. What I'm talking about.

B

Yes, yes, that's it.

A

Yes and that's expected right, because we need an owner's file there to be the gatekeepers of the approval and non-approval to get it promoted, to merge to get in something into staging, and this repeat repository right, which is what it's cloned from initially or templatized from initially does not have your owner's file. So what we should do is put a pr in here for the typical owner's file um and just be like put name or something like that there. So you can add yourself as and put that as a step.

B

But I thought I approved the pull request under the goldbang repo. Was it under the operator repo? Sorry.

A

Correctly correct.

B

A

But we're still not quite there.

A

Yet, oh here we go here, we go.

A

So we're I'm assuming we're so! Oh my.

A

Goodness so that's our actual build in staging right there and I think I'm assuming we're waiting for the build to finish.

B

Right yeah, so image pull back off. I don't think it's going to pull from its registry that we found earlier get this video describe pod on that. What's humorous coordinate, maybe it's like my private book of extra jenkins.

A

A

Take and subscribe.

A

Every time jj every.

B

Time yeah the question I pulled from china from your own private docker registry. I think okay yeah, maybe so, if you do get pipeline run or k, get tasked one. If those are all done, then I'll be a little bit concerned.

B

And I wonder where those are getting wrong in the jx namespace. I think.

A

Maybe we should be able to see inside of our main overarching pipeline run something running here.

A

B

So I've uh they've pushed to it and they'll is well what you can't pull from it or they've actually not pushed a form at the end.

B

B

All right, so I'm going to do a k, get that one online spaces, because I can't believe: okay they've all succeeded right now. If I look at the latest one, which is that.

B

C

B

Yeah, I think it yeah gk. Yes, if I did that as young uh minus and x.

B

Right, I want to see what the output is on that. So, if I do that pipe more okay, let's see what's going to push our thing to in the pipeline run, so I see jx asgar at the top. That's fine, a bunch of weird stuff fields.

B

Right id: okay!

B

B

Now, when I start seeing some push.

B

Parameters using my image great- maybe it's a pipeline.

B

B

Well, it's all very exciting. So far, it's a very big pipeline run.

B

All right, I'm not having that unless my grappler.

C

A

According to this, it should be in the staging environment.

B

I don't think it is. We need to fall back off yeah, so the image it's not a pipeline resource either.

A

It's busted huh yeah.

B

I just didn't see it do their push, but.

B

B

And then any of these coordinates, I don't see your bucket register clear grip on push nothing uh mechanical moves in my task, one, but again it's tasks on all.

B

Namespaces, so it's 19 7, I think it's. This is the latest, so this release here hey well, if you got a bit of release on your project and if so, what's in this coordinate.

B

Or maybe it's just go.

A

Code 20 minutes ago, zero, zero one. I think it's in there, no.

B

Yeah, so nothing in the task function with our image, nothing in the pipeline wrong. So I think it's just not push the image and that visualizer does it say that it's uh then a docker.

A

Portion was 10 minutes ago, master on jenkins x and there's a release.

B

A

Let's get the vlogs for that.

B

Yeah, if you search on push, maybe so as a dip bush is with doc or kanika or builder,.

C

A

Yeah, nothing like not exactly seeing any good output right now. If you do get applications again,.

B

Yeah uh uh hold on yeah I'm trying to type into the zoom window, which obviously gonna work. Let me find my shot.

B

A

B

Well, yeah, but it's got enough in that yeah there's nothing now, because there's no image remember.

B

B

Close all right- and you give a healthy back of registry.

B

C

A

C

Yeah so basically.

B

Policy is, if not present, which is correct. It's going to try and pull from here first but yeah. I just don't see any.

A

Questions we're still seeing the image back off, pull back off.

B

Yeah so that ip matches that which is good.

B

Yeah, it just doesn't get pushed.

B

I think we call it a day. If I do maybe it's not a pipeline, maybe it's.

B

Maybe it's just a big task.

B

These are a load, I just don't see a or maybe it's jake's meta pipeline.

B

Maybe it's that so, let's just check that as yaml right and let's just see, if that has got, that's got maven in it, so it won't be that has it got to go in it?

B

uh No, have you got a push.

C

B

Yeah, I just don't see where it left on the push.

A

So close man so close.

A

We just didn't get it to show up in staging.

B

Then it gets built and pushed the image, but it built the image, but I didn't push it anywhere.

A

Well, I guess for our next uh here I'll go ahead and switch this over away from the yep yeah yeah all right. So I guess to wrap up to your point, um the oops um so yeah. uh Well, we almost got it done, which is great. um We got everything installed. How we wanted to, which is fine. We even got the builds and the docker container.

A

We look like we got everything wired properly. We just didn't finish that last mile, um which is unfortunate, but that just means we can try it again in a couple weeks um yeah for how how big of a jump we had from the first time or from the very first time to the success to today.

A

I can only imagine what that next time we do this uh and how far we get we might actually get through the whole, build or setup then build and then maybe even be able to add change the main.go to say hello, jenkins or something like that and actually see that, but get pushed through too seem reasonable.

B

Yeah sounds good and it's just literally imageboard back off, I mean on ibm clouded massive, but the username called registry, but I think let's make it use either public docker hub or that internationally deployed for us. That would be a big win. I think, and.

A

C

B

I see all the improvements going in as well there's a lot of good things happening jenkins x at cms.

A

Okay, all right, sir well um yeah, uh we'll we'll be back in uh probably uh the 9th 10th. Probably the 10th um is the rate we're going about every other week or so and from there we'll see where we get sound.

B

A

Yep all right, buddy say bye.

B

Thanks everyone bye catch, you.

B