Welcome. This is Pipeline Hill, the Sheikot Africa Contributon Project. It is May the 16th, 2022. Thanks very much for joining. Topics on the agenda today, questions and answers. Seems like the most important topic and Sophia and Afi, let's put your questions and try to find answers on that. And then if there's time within the hour, we can do other topics as well. What other topics would you like besides question and answers? There'll be a lot of questions. Okay, good. Then, then let's get started. Go ahead, please. So, Afi and I worked over the weekend together and we were able to highlight contribution we will be making for this project for all the plugins that we listed. We started with some of them, and we actually like some of your assistance. So, what would you, how can we help? Okay, so if we should start with the build plugin, we went to the plugin page and discovered that there were no, there's no enough information about the plugin just an introduction, which you can also see in the Git repo here. Oh, hang on just a minute. I'll get there. Sorry. It's build pipeline, isn't it? Yes. Okay, and that, no, so that's not it. So I must have the wrong one. Build step. Build step. Thank you. Build step. So pipeline build step this one. And now if we open that in GitHub. This is the one you were working on. Is that correct? Yeah, this is one of the ones, yes, this is one of the ones we're working on. And we discovered there is no information about the plugin and just the introductory part and would actually want to have more information there, but would want to have more experience on exactly what to do because for now we just probably have some examples probably would like to include some examples. Unlike the Git plugin, it's having a lot of information and I think if you can maybe guide us on what exactly to focus on, we can make useful contribution. Very good. So, so would it help if we look together at the kinds of places where people would use this plugin and how they might use it to do to do interesting things for them. Would that help you? Yes, please.  Oh, whoops, I'm going to bring up my Jenkins instance and we're going to look briefly at and what we're going to do is we're going to create a build job. So let's, let's give ourselves a new folder just to put things in. And inside this folder, I'm going to create a new and I want to create a new freestyle a new pipeline job first. So, let's call it call or use build, build step to call other to to launch other builds. So here I'm going to create a pipeline step that's going to use the build step and I, whenever I create a pipeline I like to first be sure that hello world works. So I'm doing the hello world I'm building it now and there it is it worked and it said hello world. There's the hello world okay so the, the, this is a fake for now but we're going to use the build step to launch other builds. Now the idea then let's make this text more readable there. So then, then now I need something that can be launched. So I think I need a new, a new, a new item here which is. Let's call it a pipeline that will be launched. So this is the thing that's downstream. And again, I'm going to just create a hello world entry here. And then I'm going to run it once just, just to see that it works the way I expect and there it is and it says hello world. Okay, so now I've got two jobs here one is use a build step to launch other builds and the pipeline that will be launched. And now what what a user would do is they would configure this pipeline, the, the one that's going to do this launching the top level thing. And in pipeline syntax. They click build. And the job to configure, they want to use that other job that they're going to build so they want pipeline that will be launched and I need to get the text of that that way. So pipeline that will be launched and now it hints to me, hey, this is a job that it recognizes so it knows about that job and I could have made this much less text. And if I just said pipeline, it will suggest that and I could click it. Okay, so now, should we wait for the job to finish for this time. Yeah, let's say yes, do we need a quiet period, I'm going to say just for fun. So three seconds, and now I'll generate the pipeline script, and that's what I want to do. So what I just did is I've generated a script that says the upstream will ask to launch the job named pipeline that will be launched, wait three seconds before doing it. And it will wait for it to finish before the job will continue. So, so here we go. So this is use build step. I'm going to put that in and then I'm going to say echo goodbye world. Any questions so far Sophia. Or is this, or is this not helping and did you have a different question that I should be should be doing something else instead. Okay, all right, good. So, so here what we're going to do is we're going to, we're going to watch. So remembering that the pipeline that will be launched. It's only been run once we see down here that there's it's only been executed once. And the use build step to launch it's been launched once. So now I'm going to build now. And when we look at what it says, it says scheduling project, something and starting building something and then it says goodbye world. So here's the hello that I started with the goodbye that I put in and here is a separate project that got run. Now when I look at this page and refresh it you'll see job to ran, even though I never clicked build now on this page so. So what the build step did is launched another job. And, and now if we if we do things like, for instance, let's configure this one, make it a little more dramatic we're going to instead of just echoing hello world. We're going to sleep for 15 seconds. We're going to wait inside this job so I'm going to save that. So when I click use build step to launch other builds. I'm going to build now. And watch what happens here notice that it started one second ago, and six seconds in it hasn't finished yet. Now if we look at the trend initially it only took three seconds the first time I ran it. This time it's over 11 seconds and still hasn't finished. And that's because that 15 second delay that I put into this job sleeping for 15 seconds. That 15 second delay was waited for by this upper level job. So, so one of the use cases that's good to describe is in this pipeline syntax generator, wait for completion, what does it mean, and how do we explain to people why it means that. And so what wait to come for completion means it's got. You may ask that this pipeline wait for completion on the downstream build. And here's what. That says, okay, now what is all of this other help and this kind of thing gives us lots of insights on. Oh wow, there is a return value that that I could use that can give me other examples so not just not just that hey let's look at what wait for completion means, but now this is giving me a hint, and I could remember other things about this. So question so far. Yes, so I was going to ask about those parameters. What happens with that wait for completion. I don't like. That's really advanced, or I don't, I don't know. Are they supposed to be in the pipeline step and it wasn't needed. Because I can really tell the usefulness of it. Okay, could you could you ask your question again so your question was, is this. Oh, go ahead. Yeah, this other parameters down here after may experiment. Yeah, yes, those ones. Like what, what am I supposed to am I supposed like, what are we going to use them for as a user. Oh, good, good. So, how would, how would these things, how would these things help a real user. Good question exactly very good okay and and what what I think you just asked is, why would a real user care about build number return from a from a wait and what's the what's the case what's the use case the story that someone would care about that one. I think is what you're asking right so so let's let's talk about that because I think that's a good, that's a good place to look at these kind of things so, so what I'm going to do is I'm going to try to take what the snippet, the syntax generator suggests here, and it says hey, the return value of the step can be used to get information so let's let's do let's get the return value. Now, now you're going to get the process of switching from declarative descriptive pipeline. And so build. So, and I apologize that this is for me a rather more advanced topic than just, but I think it's a way to answer your question. So what this is going to do is this is going to say, and then we're going to say echo. So build result is is. So what we're doing now is we are remember remember the return value from the build step, and then display the result of that to the user. So let's let's try running it now. And just to make things go a little faster we're going to change this sleep. We wait 15 seconds maybe we wait three, because three I can wait patiently for. Okay, so now remembering how I'm configured I'm going to call that builds that that build step and remember its return value in the build result variable, and then I'm going to display it to the user let's see if this gives us what we hope. So here it is it schedules the downstream job started building it now we enter the three second wait period. And here it says, Oh, this is what we got back. Now that for me is not terribly helpful. What is that well what this help says is it includes, let's see where is it inspect its dot result and so on so what this thing has is a bunch of fields.  So, so let's look at that one now by saying configure it. And now instead of build result we're going to say build result dot number. Okay, so it's now referencing that build result thing that was returned from build and looking at the number field. And so now I need to make this. Oh, no, no, I should do it this way. It's much easier, we can all see it better if I do a second echo statement build number is build result dot number. And while we're here, let's see if we can get one more which is the, let's see a good one is the result. It can be can be interesting so build result is this. Here we go save it build now three seconds wait. build number is five build result is success. So now if we look here, the last build number here was five. Now I'm going to change this. And I'm going to say let's fail. Let's make this one instead of success let's make it fail. And intentional failure. I think that's the syntax we may have to look it up. Build now, waiting the three seconds starting it. And it says. Oh, look at this it says. It failed and stopped the execution of the upstream project. So the downstream failure that we'll see here, cause the upstream to fail again a use case that we'd like to describe what if I want to ignore the downstream failure. It says propagate errors thing. So, again now when I generate this it says propagate colon faults if I wanted to ignore the downstream failure and just report it. So I've got to configure this job. And say, I'm going to add a new parameter here propagate faults. I'm going to start building it again. And this time what it should do is this job will schedule the downstream. Start building it. Wait the three seconds, see that it failed and still report. It says build result is failure build numbers seven. Now that's my downstream here so let's, I'm going to build this one now just to give us a new number. Let's build several copies of this just to be sure that it's distinct. So ready here we go again build one more time. And what we want to explain to the user is, Oh, this is what propagate faults means and this is what, what the, let's see the other the wait for completion means. Did that help a little bit Sophia or do you ask more questions help me understand what, what else we should, we should highlight. Yeah, yeah actually things that else on meaning that with the results we get from the downstream pipeline build don't we could actually like me can make it conditional statements that if this build fails. We could run an alternative or backup view of something. Yes, exactly. Very good yeah you understood it precisely it's if because of because of what I've done in this example here where I said, remember, remember the result of the build that I just called. And then I could do a conditional based on build result dot, dot number or build result dot result. And now if I, if I, if I don't want to worry about that and I say, if I call a downstream job and I just want it to fail everything, then I would remove this propagate faults or set it to propagate true. Now let's take out this quiet period, because again that that's something that can be explained but in this our particular example. I don't need it now when I build. It's going to immediately start it and it won't wait for three seconds, looking for other changes, it just starts immediately. So, so does, does that address your question with regard to to what might we say in this help about wait for completion and what might we say in the help for propagate errors. This is an example in propagate errors and, and here's a, I think they're both valid, valid places propagate errors for me is a little easier to see how we might add an example here to this text, where what we would say is the pipeline is a real tax generator generates the following when we, when we disable propagate errors, and then you might say and we would do this because we want the return value. We want to use the build result, but we don't want to block or disrupt execution of the current job we just want to get the return value, and the job value is the job result. So, use that for further logic. Does, does, does that sound okay Sophia or have I have I have I missed something. Okay, so are there, are there other questions that you'd like to ask. Should we hear from our first person. I, I fear that off he seems to have dropped off from the call I don't. I, she may have had internet issues or some other surprise. So, absolutely, we can certainly check with her as well if she if she rejoins us. Okay. So, sorry, why actually like license some examples for the agency here. Um, I really couldn't generate a stay the syntax with credentials issued to request with credentials. I was able to do for the custom errors, the motor part fire and the others, but I couldn't do for the credentials I don't know if you could then wait. So, was that was that the credentials you were using with the gets get with the checkout step, or was it with something else. It's HTTP request plugin. Oh with HTTP request okay so let's, let's do that one very good let's let's try that I've, I've not used that plugin before so if you don't mind me doing experiments here live. Let's let's do that experiment live so let's create ourselves a new job that is and make an HTTP request. Okay, so again the usual thing I need a hello world I want to be sure that it builds. Hello world looks good. Okay, there it is so now we want to generate an HTTP request that we're somehow going to use. And so that HTTP request. We still need the pipeline snippet generator to help us generate the HTTP request. Right. Oh dear do I not even have it installed on my on my. I must not have it installed just a minute let's get that plug in installed. Okay, install. HTTP. I do not shame on me. Okay, so we've got a first install the plugin. HTTP request, and here it is. Okay, so download now and install after restart. Okay so in about 30 seconds we'll have a, a running Jenkins with because of how busy this particular one that I'm running is it would take a while so will. So what we want to do though is we need to, we need to create an HTTP request that is a good example using a credential ID, right. So just a minute let's see what I can do with that as a as a possible target for an HTTP request maybe what we ought to do is try. What's a place where we would go with an authenticated HTTP request maybe to CI Jenkins.io. What if we tried there to launch a build of because I happen to have permission to do this you you may not but I have permission to launch a build so maybe what we do is we find a plug in that it's okay for us to launch a build on it and that will do that with an HTTP request oops wrong one this one CI elastic access. Okay, so we look at the rest API here and we're going to use HTTP to make a rest API. And we get a call to schedule this build so here's what it says it says to perform a build post to this URL and you could do this with your own server I just happened to be using CI Jenkins.io. So, this is the URL that I need to open with a post request. I don't need to use credentials, because if I don't use credentials CI Jenkins.io will will just discard my request. So did we ever come back here, come on, come on, it takes a long time to restart my big Jenkins instance just moments. So, while that's restarting I'm going to bring up a text editor and make use it as a place to put some notes. So what I want to open is that, and that will ask to schedule a build now what what I think we should do to experiment with this is we should first try to open it without credentials and confirm that it fails. So if you get that in the Jenkins job, then use a credential to open that URL and confirm that it works. Does that work okay for you Sophia if we take that approach. Come on Jenkins get back. Okay we're getting better. Sorry for the slowness let me go look at it and see what's keep making it slow. Interesting. It's just starting. Oh, here we go it's back. Very good. Okay so into our folder. And make an HTTP request. So here I'm going to do the configure and for the moment. I'm going to close the tabs on my right hand side and I want to use the pipeline syntax to find out how to make this HTTP request so I click the pipeline syntax generator. So the request, the URL that I need is this one, and it said that I need to use post. So I changed the HTTP mode to be post. And now if, and I will I definitely do not want to ignore SSL errors so I'm going to generate the pipeline script so here it is. Let's see what their suggestion is for my my command that I should run. So let's try that here. And with my apologies, I have to have shorter lines. So this says it's going to say hello world. It's going to submit a post request to see I dot Jenkins that I owe asking to build the elastic access plugin. Let's go check to see what things are looking like right now before we start it. So the elastic access plugin right now is its most recent build is number 170. So remember that number 170. We're going to save this now and build it. So it will say hello world, it will make the HTTP request, and then it should tell us something about it so it's opening it's doing a post to that location, sending the request. And it says forbidden. Good. Okay, so that's the failure we hope to see. Right it says, I tried to access this URL, and wasn't allowed to do so. Now to your question how do we add a credential to this. And I think we do that by clicking advanced. And now, where is a credential choice. I don't see. Oh, here we go authenticate. There we go. So let's try this one. So how do I have a credential that I can, there's the Jenkins API token which I may not already have a credential here that I can use. So I may need to actually add a credential for right now let's, let's just borrow one of these and try it so that we have the syntax but I expect it will fail because none of these are for CI dot Jenkins.io. So, I'm going to generate the pipeline script to use a credential. I'm using this credential but I think this API token is actually for my own Jenkins controller, not for CI dot Jenkins.io. So let's try it just to see. And here if I grab that I only actually need this additional parameter authentication everything else is the same. So now when I build it remembering that last time when I built it the output said sending the request and it got a response code forbidden. So now let's build it again I expect the same thing but I think this time it will mention that it's trying to use a credential. So here it says using authentication, I still expect it to fail because I don't think that's a valid token for CI dot Jenkins.io. It's opening up the request, and it says, oh, notice this is different instead of forbidden, it says unauthorized. So it got the request, it saw that I was trying to offer a username or a credential and it says that credential is not authorized to do this. So the next step I'd need to do is I need to create a credential on CI dot Jenkins.io that is valid that I can use. And for this, I'll probably have to turn off my screen sharing because I don't want to record permanently this new credential I'm going to start the process and then we will get to a point where I'll stop the screen sharing so that you can't see the token.  No, no, no, I'm wrong. I'm my mistake. Kevin, you may have to help me here. I think I need to do configure. Yes. This is what I want to do. I want to create a new API token on CI dot Jenkins.io that I can use to do this work. So what I'm going to do is I'm going to click the add new token button. And it will then generate a token for me show it to me on screen and then I can paste it into a new credential over here on on this dashboard. So here I'm going to create a credential, let's see where credentials here, and I'm going to get ready to create that credential then there will come a time when I just have to have to put the folder. I want to add a credential here so here the username will be mark you wait. The password is something that I will enter in when I've stopped sharing the screen. I'm going to assign the ID which is CI Jenkins dot IO credential or mark you wait API token. So API token for CI Jenkins dot IO as mark you wait. Okay, so I will put the password here but I'll do it after I've stopped sharing my screen. Any questions so far. Okay, so we're just go ahead. Yes, Sophia. Okay, because I know I tried creating a credential in my local app but I couldn't. I went through the money is drinking money is plugging then global configuration configuration, but I couldn't create a credential. So if you did, you did actually remember. I think it's for the example. Yeah, that's a useful example. But it wasn't to this was right at them and manage plugins down was on the left side menu. Then you added it. But I don't know how Mark did this. Yes, it's different. So let's, let's go through the likely path you took to create the credential because I could do it the same way that you did I think. So I think what you probably did is you went to manage Jenkins. And then you went to credit manage credentials. Yeah. So here, unfortunately the user interface is confusing and I apologize for how confusing it is it is just confusing. What I have to do is find a place where I can click a down arrow that lets me add credentials. Yes. And so for instance, I like to do it from this store scope to Jenkins pick and I say, I want to do here. No, not add domain. I want to do on global add credentials. And I could do the same thing up here. Global click the down arrow add credentials. I find that as a really strange place to have to go to, because my mental model says oh am I adding a credential to the invalid user and password. But the answer is no what what I'm doing by clicking this domain drop down arrow is I'm adding a credential to that domain. So I think what you probably did was, and I sincerely apologize the UI for this particular page is really weak. I click add credentials and it says, I'm adding a credential at the system level, and it's a global credential. And here it here is where I'm adding it so this is I suspect probably where you were adding it. And we could add ours here as well. Let's just do it this way so that it's, it's recorded there so this one. I'm going to make make some additional comments here folder scope. This one I did in a folder, but we're going to take that. And we're going to do it the way you, you did it, but we're going to put it all the way up at the top level. Okay, so, so what we have now is, we're going to get a new credential, it's token will be this CI dot Jenkins that I would dash mark II weight dash API dash token, its description will be API token. And let's let's make it even more clear top level API token for CI dot Jenkins.io. So, comfortable so far Sophia, Afi. Yeah, so far so good. Okay, now we're at the point where user mark weight was about to click this add new token button. And this is where I apologize I have to stop screen sharing because otherwise I will show everyone and record for everyone exactly the value of the token and that that would not be good. So I'm going to stop screen sharing I'm going to press the add new token button. I'm going to take the text from that add new token button, and I'm going to paste it in here. As as this global credential let's put these two tabs right next to each other so it's clear to me where I paste it. So, I'm going to paste it here's the password I'm going to press okay. Once I've pressed okay I can start sharing screen again because I can open it and show it to you and it will keep the password hidden. So, add new token is what I'm going to do next after I stop screen sharing paste it here and then press okay. Okay. So sharing is going to stop. And now I do the add new token and it shows, I need to give it a name like she code Africa token demo. I'm going to press the generate button. Now it gave me the text. And it says on the screen it says copy this token now because it cannot be recovered in the future. I'm going to paste that text into the password field, and already I can start sharing again. Because even before I press okay, you'll see what this how the screen looks and it's already not showing the password. So what you see now is, here's this, here's this password that I pasted already hidden. I'm going to say okay. I'm going to drag this screen off. And press the save button there. Okay. Now back to my configure bringing this back on screen. There is that she code Africa token demo. And now what we really want to see is where did it go and here it is CI Jenkins dot API top level global API token. And there it is and the password is concealed. So now what I want to do is any questions so far on the steps that we've taken generating the token on CI Jenkins that I went and using it in my Jenkins controller. Okay, so now let's try using the snippet generator to reference that. Okay, so we want to do this again with HTTP request. And I need to remember the URL again so the URL was this. And we need to make it post not get we want to heed SSL errors and continuing downwards authenticate and here. I'm so glad look at that marquee weights top level global API token for case so now let's generate this pipeline script. And what we see here I can copy that thing.  Where was my make an HTTP request configure this. And here it is. And if I put in that again. Okay, so this is saying it's going to authenticate with that API token I just created. And it's going to use the elastic access you access URL through check where we are on CI Jenkins that I'll hear it still build number 170 so we haven't built and run a new build yet. I'm going to save this. Build it. And now this time if we're lucky it will tell us, hey, I used. There's the URL here it's using my new credential. Good. It's sending the request. And it says. Oh, 201 is in the accepted range so now if we go look on CI Jenkins.io. We can see that job number 171 has started. So, so does that give you a sense of how we could do a credential based. Now, now, writing that in an example is is probably easier than actually getting it to work the way we just did because the example you just give some arbitrary text for the credential ID, and assume the user will replace it with their own. Sophia and Afi. Okay, so far, or is there more that we should discuss about how the authentication, how to how to get to this point, because it may be that what we would want to do in a long term thing not for this project but someday in the future we might want to video of this kind of thing where we say look, here's how this is done, because there are a lot of steps to get a credential out of some other system and into your Jenkins controller. Yeah, it's okay actually things so. Thank you, Mark. Thank you. And my apologies for showing you some of the uglier parts of Jenkins in your exploration you're very patient with us. Thank you thank you for being so so considerate and open to try these things. Thank you. So, so far, we've actually got clarity on two major plug in that we had issues with. And I don't know if there is time for us to actually explore the imputes, no game, the input step plugins. Let's do that we've got we've got about 12 minutes left. So if you'd like to try the input step let's let's definitely do that so. Let's first find it on the plug in site. It was input step is that right. Yeah. Sophie I go and according to the list that we came up with. Yeah, okay. If you have any other questions. Yeah, it was just and also we wanted to notify him that and the changes that he tried to make the last time that was not reflecting. It was because it was because he was not referencing it's in that other file to remember. Yeah, I miss those things. Okay. Okay, great. I'm actually referring to the last meeting we had here you're trying to help to capture, capture should be in the input string plugin. And it wasn't showing so we're able to figure it out that first. Yes. Okay, so, so you were able to figure out that that's great. So you were able to decode how to where to put things tell me more about which we're able to where you were able to figure out. Okay, let me get the name of the plugin. Okay, so the name of the program is the input step. Okay, I will have to show that. Okay, I think we're going to go ahead. Okay, so would you like me to, would you like me to, to, to start a new job that uses the input step and maybe we can use that for some experiments. Yeah, we'll take an example. Okay, so let's create a pipeline that uses the input step. So hello world. Build it, confirm that it works, but you did configure. Okay, now we want to use pipeline syntax to do something with input. Wait for interactive input. Please provide your input. So here's the simple one right so please provide your input and we're going to do this. Save it and run it. So it started. And now it went red. And now we have to look to see what's going on why did it go red. And if we look at the console output we'll see it says please provide your input proceed or abort. Now if we want a prettier view of that we go to Blue Ocean, where it says, please provide your input and proceed or abort and there are other ways to look at this but this is, this is one alternative so when I press, press proceed. The job will run to completion. I did the same thing so pressing the, the run it again this rerun loop. What if I press abort. Now it said, Oh, I stopped the job, it did not complete. So now when we go back to Jenkins what we'll see is notice this icon says oh the job was aborted, whereas the first job was success or the job number two was successful. So the major purpose for this audience to get input from users. Correct. The input is, is a simple yes or no, shall I go forward or not. But but the goal of this thing really is to ask them for for things now. Now this allows us to do parameters. And then the parameters, the values are returned so we could in fact, ask for more things so let's let's try that. And again we're going to use the syntax editor to the syntax generator to help us. So input. And now we go to advanced. And just for okay, let's see, waiting for. Let's how about we ask a different what do you want. And we're going to give it a custom ID my custom ID. Okay button caption. Yes, I mean it will be the okay button. And now we're going to do add a parameter, we're going to add a Boolean parameter which is, we're going to make it very obviously named Boolean param. It will be true by default Boolean parameter true by default. So my defining I'm defining an input step with a different message what do you want using a custom ID, and the okay button will have a different text on it. Yes, I mean it will be on the button, and it should ask me for a value of Boolean param. So let's take that step and put it back into our sample job. And we can actually do multiple inputs so let's let's do this. Okay so this says I'm going to take it, maybe we'll comment out the first. So I'm going to take input from the user that asks them a question. Let's them to okay so input requested. There we go. So now it's put me into a screen asking me for for my input. I could do it here, or if I want I could look in let's see what blue ocean does with this. What blue ocean says is what do you want. And there's a Boolean parameter and if I uncheck it or check it and then yes I mean it is the button to say yes. Now if I run it again. I could, and I could leave the Boolean parameter check but if I click abort it will cancel the job. Okay. And the, the gap there I think is that, hey users may not understand the first pointer is, we always want to point them to pipeline syntax generator right it really is the best way to do this without without guessing what the syntax is just let the generator help you. But still it would be good if we had some words on the, on this on the pipeline documentation page that said something more than the very simple thing that you see here. Yes, that's actually what we intend to do. Great. Okay, so that means that we could give more information about the pipeline syntax generator and certain options that it could go with when they are. Okay. And Sophie, the next one, we have a few minutes. We can actually go through the list. Sorry. Yeah, I don't think so. Yeah. I'm going to share it today. So my, regarding what I was going to show you is actually the HTTP request plugin and the custom edge. We are trying to have help to it. And when we tried to the last time it wasn't showing so like, we were able to be going during the weekend awesome so I'd like to share that with you. Yes, please share. Are you willing to share your screen or, or do you want to just describe it that would be great. I would love to know how you how you discovered it. Okay, thank you. Well, remember we just actually added, we just only had an HTML page here, the custom editor, but we did not actually, we did not refer it in the Jellify. So we're supposed to come here and then add the the URL to the help. Oh, you're brilliant. Oh, thank you very much. Okay, so, so the thing was, this jelly file needed a change to refer to where the help, where the help is. Yes. But it's not so for all. There's some guidance as well to fair it, but for this particular case you have to. Thank you, that Sophia thank you very much I appreciate. I love it when I learned something new. Thank you, thank you. That's, that's a group. Truly, thank you very very much that's wonderful that you discovered that. And certainly, it's in the, it's in the documentation did you find it in the documentation for that or did you just you just looked at the source code and made a good guess and said oh this is obviously missing Mark didn't realize it. I went through documentation but I couldn't find it in, but I had to go through the source code. Yeah. Excellent. Sophia, thank you very very much. I have learned something. Thank you, thank you. Any other topics we should discuss today. Yes, so we actually like trying to work together. And for our lease we're able to discuss three plugins. And now the other one was supposed to be the load processor where it's supposed to have more documentation to the plugin page. And also the clean workspace plugin and basic step plugin and some other plugins but I don't know if we will discuss this today. I would, I would leave those I think you've already got more more in the input step than we have time to do so I think just input and HTTP requests those two if you make progress on those or, or the the one let's see the which one was an HTTP request that you just showed us how to do. Yes, it's a very quick. Yeah, so if, if you were to do those two that already is for me quite an accomplishment. Thank you. Thank you very much to both of you. I believe we are scheduled for another session later this week with our usual time are the two of you okay with that as an next session. Yes, won't care with that. And now I need to look to see when okay so we're scheduled for Thursday is Thursday okay. Yes. Great. All right. Thank you to both of you. Thanks very much. I'll get the recording posted of this. And if, if I've missed past ones hopefully within the next 24 hours. Okay, thank you very much. Okay, thanks to both of you talk to you Thursday. Yeah, thank you for nobody.


This is Think Tech Hawaii, Community Matters here, 12 o'clock on a given Friday, you know, I am not Stan Osserman, I'm Jay Fidel, I'm standing in for him, I'm standing in for him. Nicely done. Thank you. And that's John Nauchi, he's the Deputy Director of the Department of Transportation Services here in the City and County of Honolulu and we're together on Stan's show, the Hydrogen Man, I'm not the Hydrogen Man, but we can talk about that kind of thing. So Stan, welcome to the show, thanks for being, I'm sorry, John, welcome to the show, thanks for being here. Glad to be here. Yeah, yeah.  Without being too wordy, my long pathway probably started with where I grew up in Kahalu'u. Okay. So I was reading Kahalu'u, the bus came by, made a left turn in front of my house, every day, every hour, for as long as I could remember growing up. And you know, once in a while, my mom or my dad or my popo or goong-goong would shuttle me onto this bus and I think that's where I learned about reliable transit. So fast forward through my high school and I'll shout out to Yolani because they're my favorite and that's where I went. I did go to college in Los Angeles at University of Southern California, USC, and I studied urban planning and I had a chance to experience LA immediately post Rodney King at a time when, you know, a lot of their infrastructure was just devastated. I mean, I arrived on the USC campus and things in the neighborhood were still literally smoking around the neighborhood, but the campus was relatively pristine. So I got to experience LA with bad transit and bad mobility and car-based mobility. And I developed, further developed my, I call it my transit geekiness for studying transit systems and how they work. It's actually a thing by kind of experiencing LA. And when I came home, I wanted to apply the knowledge I learned in urban planning. I studied urban planning with an emphasis in transportation. I wanted to kind of bring that home and figure out a better way, a better path to mobility for Honolulu's residents. So upon returning home, I took up work at Oahu Transit Services, OTS. They're the contracted management and operations for the city's, the bus system. Worked for them for 16 years, left there as a director of planning and service development. Moved over to heart for a little bit, did deputy director of planning, environment and culture, and was appointed last, well, in 2016 by Maricaldbo to be in his cabinet as deputy director of DTS. So I'm, I like to actually kind of proudly say, if I'm going to took my own horn a little bit, I may be the only person on this island who's worked in bus and rail and paratransit, which is our handy van, to, you know, be able to kind of be in the really uniquely situated position to kind of bring it all together now. Yeah. I agree with that. You're perfect. I used to say sometimes like I got to quarterback the thing, throw it down the field and then do the Marcus Mariota and then catch it again. So no, it's, it's, I'm not that, I'm not that good. So deputy in DTS, what does he do? The deputy in DTS oversees a number of divisions, which include our traffic signals and technology, our traffic engineering, transportation planning, and our public transit division. Within those falls the responsibility of what's called complete streets and the city adopted an ordinance to implement complete streets, which equalizes no preference over mode or balances out preference for bikes, peds, transportation, cars and buses. Complete streets is yours. Complete streets. Oh, that's really interesting. I hope we have time to talk about that a little bit. But let's talk about the news first, always the news first, top down, yeah? So the news is the electric bus. Yes. This is really interesting. Somebody told me they saw one. They really looked beautiful and it was, you know, it harkens a new time. Can you talk about it? Yeah. That's actually been one of my passion projects under Mayor Caldwell's leadership. And councilmember Joey Monahan has been, they've been very front facing in terms of pushing us to get electrification of transportation and have that incorporated more into our DTS's immediate and future goals. So the city basically began what we had hoped to be a year long demonstration program in which we opened our doors to bus manufacturers who have electric vehicles to come and demonstrate their buses in Honolulu's transit environment. And when I say that, it is really an environment. It's different than other environments, yeah? Yeah. Everybody likes to think they're different. But I would point out that in Honolulu we have the fifth highest per capita transit ridership. And that says a lot because in that top five, top six, top seven, we're the only ones without an active rail component. So just with our bus system, we have maybe one of the most heavily utilized bus systems in the nation. And that's something that most people don't realize. I think if you think Honolulu, you think I have to have a car. But it's changing. It's changing. And I would actually put it out there that everybody is talking now about TOD, TOD, transit oriented development. And I like that it's in everybody's mindset and everybody's considering it as, oh, this is something we're going to do now. And I'll nod and I'll agree. But I'll contend that we've always had TOD here. The Honolulu that we know, the old urban city, is based on the streetcar system that was developed. The 12 miles of streetcar that we used to have is basically TOD, run up and down King and Barrett Tanya streets in downtown. Tell the people what it is and how it works and how it benefits us. It's this idea that the city should have a more compact footprint. You should be able to get around. You should be able to do everything you need to do without requiring a car. Now I'm not going to malign anyone who, like my former predecessor planners, who thought that we should sprawl to the suburbs. We should have neighborhoods with nice looping streets and cul-de-sacs, because that's what the rest of the nation was doing. And we went along with that as almost an American ideal. Was that the yard, the American family? A cul-de-sac in everybody's pot. A cul-de-sac in everyone's neighborhood, yeah. But when you look at it, we had TOD in the 1900s. And those neighborhoods that were established by that are still thriving and are still vibrant. And if you look at even YLI and Kaimuki, Kaimuki was the answer to probably Honolulu's first affordable housing crisis. So we had a sustainable transit system that was electric powered. And like the rest of America, a lot of us gave it over to diesel. And so that was a big evolution, probably in the 40s and 50s. And we're seeing that evolution where I don't want to sound too hipster about it, because I'm probably officially a generation X or Y-er. But we're coming back to this ideal of putting electrification of transportation back in. And I find that we're on the cusp of it, and I'm kind of happy that we get to see this ushered back in. I'm not going to go back and start using manual typewriter. I like to see the quiet vehicles coming back in. So TOD means you develop at various intervals. And those intervals are mercantile. They're shopping. They're commercial. And so you can always get somebody to fix your shoes, to sell you some groceries, whatnot, within a fairly short distance. And you don't have to have a car to do that. Sure. It's this idea that you can live, work, and play. I mean, I think that's the simplest way to put it. Live, work, and play in a very compact area. That's not to say that everyone should be based out of their own small little village. We want to give people mobility within the region also, because we still cannot turn our back on the sprawl, the fact that affordable housing exists farther away from the city center. But we want to make sure that people have more of an opportunity to enjoy their own neighborhoods. And neighborhood is community. Neighborhood, it all begins in the neighborhood. That's right. And I think, I agree with you, we kind of lost touch with the notion of neighborhood where you say hello to people on the street.  And the problem I see, just to compress this part of our discussion, is that we spent a lot of time sprawling. That was the big plan, second city, all that. Sprawl, sprawl, sprawl, sprawl, for how many 50 years anyway. And now the better judgment is not to sprawl. And here we are trying to reverse an initiative that we spent 50 years building. This is hard. And it's hard to get people to change, turn around too. It's hard to get them on board for this sort of thing. It really is. And we're coming into an era where we want to transition people away from fossil fuels. And I think the mindset is in place. Now, how do we translate that mindset into actual forward action is the rub here. And I'll share something that Mayor Caldwell always tells me personally. And I think he means it maybe as a little joke, as a little knock to me as someone who hasn't ever been planning background. But he'll always say, you planners, you always plan. You guys have a hard time implementing. You guys can plan, but to implement is divine. Is that true? Well, planners like to think about things. Is it true that planners have trouble implementing? You don't strike me, actually, John, as someone who has trouble implementing. Well, I will say a planner's job is to plan. And then we hand off to engineers and other more able-bodied members to implement. So our role is to plan.  And maybe nothing will get put in the ground because of that. But we have to make sure that we can articulate our ideas that make sense and hand them off to a more technical set to actually put them in. It's the same time, though.   To me, that's unacceptable. So they're all self-defeating. You've got to, if you want to realize your plan, your destiny, your work, have it come alive, have it flower, you have got to follow up and say, wait a minute. We've got to implement this. And I'll go to great lengths. I'll even push people in order to implement it. So I'm not just handing it off. I'm saying, here, now, let's do it. And I'll help you do it. And that's what I usually tell people who are contemplating a career in planning or contemplating going into the field, even for education. I said, you have to be OK that for every 100 ideas you have, maybe five of them will get done. And if you're not OK with that, don't enter this field. And I was liken it to the real erase. We package the idea. And we have the baton. We hand it off. But at the same time, I can't just hand it off, let the person take it and stop running. You've kind of got to run with them for a little bit. Just to make sure that what you had articulated, the vision you had, makes it all the way to the finish line. Yeah, you should have some authority actually to do that. Maybe it's just cheering for them as they finish the work that you started. Well, as DTS deputy, you do have some authority, don't you, to cheer them on, to ask them to be accountable, not to let it die. After all, we went to the trouble of planning it. Then it should happen. My feeling is there's too much planning that never goes anywhere. So if you're going to go to the trouble, you might as well force the issue. Anyway, but going on to the news, what is the electric bus like? Is it the same inside, outside? How does it work? So this is interesting. So let me back up a little bit. Mayor and council member Manahan told me that they wanted to do an electric bus demonstration. And I said, OK, that's a great idea. And I got the speech about implement. So we set up a program for the demonstrations to start. Same discussion every time, every time. And I say jokingly, but there's an answer to every true statement. But so we had some people answer to our call for demonstrations. The first happened to be a company called Protera. Now what's interesting about Protera is they're a technology company that is building a bus. Everyone else, I believe, is a vehicle manufacturer who is applying high technology to an existing platform. So it begs the question for us, as someone that operates transit, is it easier to teach somebody how to build a bus, or is it easier to teach somebody how to add technology to an existing platform? So with Protera, it's the only electric vehicle that's designed from the ground up to be an electric bus. And I found that very interesting. They're based out of San Francisco. And what is another interesting feature that they have is it doesn't have a stainless steel frame like most buses do. It's made out of composites. So it's manufactured in very much of the same materials that a boat would be manufactured. Lighter, more efficient. Lighter and more efficient. And the battery storage actually happens under the floor. So in every other electric bus, they stack the batteries on the roof because that's where space is available. And they don't have to re-engineer that platform. More stable under the floor, no? Having driven it before, and having heard comments from our bus operators who do drive it, they say it turns and it is nailed to the ground. Yeah. This makes for a better ride. It sure does. It really does. And I think one of the moments of realization I had that this was completely different, I was standing on the intersection of Baratanya and Punchbowl, which is right next to one of our most busiest stops in our system. You have all the lanes of traffic coming up in Punchbowl and Baratanya. And all you could hear was the noise from the cars passing by. You couldn't hear anything from the bus. The bus passed by, you know, it was just like, well, this bus is here, you know? That's like Stan's hydrogen bus. I was telling you, it doesn't make any sound at all. And we had a lot of discussion about whether we need to add a friendly little noise that the driver can actuate. So don't need to tap the horn to make people aware that I call it the silent green ghost is behind them. But, you know, when you look at that, that was a moment of realization I had was that this bus was not polluting the noise environment any more than, you know, all the other cars were already doing it. And when we had the press conference, we had a press conference to introduce it on Tuesday. It's the first time, and I noted this, the first time we've done many of these bus presentations and bus demonstrations before with diesel buses. First time we've ever actually had the press conference with the bus fully on and the AC running and everything like that, because we could. Good sound. Yeah, I mean, it didn't make any sound. So we could respond to it. We could put it right here in the studio, eh? Yeah, you know. You'd hear a little whooshing because of the AC and all that kind of stuff, but it's not significantly a noise polluter, no environmental effect in that sense. So one more question before we go to the break, John. What does it cost? I always say right now, an electric bus will cost about one and a half times our standard diesel bus. So we're talking about more than half a million? Yeah, a standard diesel bus costs a little bit north of half a million dollars. We're talking about 750 or so. Yeah, so even numbers, nice, easy math because I'm a planner, I'm not a mathematician. I always like to think of 500,000 and 750,000. So in that case, you know, you got issues about raising and you have to buy it cash, no? We can buy it federal funding. Federal funding. Ah, okay. So the feds have a lion's share of our vehicle purchases and we provide a local match to start it and the feds buy the rest of it. Okay, when we come back from this break, we're going to find out how many of these buses John wants to put down in the streets of Honolulu and over what period of time? That's John Nauchi, he's the deputy at DTS, the Department of Transportation Services in the city and county of Honolulu. We'll be right back. Good afternoon, my name is Howard Wigg. I am the proud host of Code Green, a program on Think Tech Hawaii. We show at three o'clock in the afternoon every other Monday. My guests are specialists, both from here and the mainland on energy efficiency, which means you do more for less electricity and you're generally safer and more comfortable while you're keeping dollars in your pocket. Aloha, my name is Mark Shklav. I am the host of Think Tech Hawaii's Law Across the Sea. Law Across the Sea comes on every other Monday at 11 a.m. Please join us. I like to bring in guests that talk about all types of things that come across the sea to Hawaii, not just law, love, people, ideas, history. Please join us for Law Across the Sea, Aloha. I'm Jay Fidel, not Stan Osserman. I like him very much though. And this is Stan the Energy Man on a given Friday at noon. And we have John Noucci. He is the deputy of the Department of Transportation Services here in the city and county of Honolulu. We're talking about the new electric bus, among other things. So before we left it, there was a cliffhanger there. How many are you gonna get? Over what period of time are you gonna take to deploy them? So I am working under the mayor's guidance that in December, all four county mayors gathered on board the Hokulea or Empokai Bay or the YNI coast. And that was more than symbolic. The Hokulea had just done the Malama Honua voyage and learned how climate change is really affecting the rest of the world. And upon the deck of the Hokulea, all the mayors committed to powering their public and private vehicle fleets in each of their counties with renewable energy by 2045. And Mayor Caldwell gave city and county of Honolulu an advanced finish line 2035 for our public vehicles. So it sounds like a lot of time, but really we have 15 years to execute. It's not that much when you start looking carefully. It's not a lot. And I think what we need to do is take stock of the resources that we have. And it's more than just us appropriating money to buy these vehicles. We have to look at the infrastructure and electric infrastructure and see what's available to us right now and how we might grow that and introduce more of the renewables into that electric infrastructure. So we're not just burning fossil fuels to power electric vehicles. And I think I like to use that adage. It is good times in the kingdom right now. We have been collaborating very, very, very well and with Hawaiian Electric. They have put a pretty serious commitment to electrify transportation. It's called EOT. And hopefully as we go on EOT, I won't have to say it means electrification or transportation. People will know what EOT means. They don't know it yet, John. They don't know it yet, so we'll start here. And part of that issue is integrating our charging needs with what the grid can hold and what the grid can provide. And the city recently applied for what's called a LONO grant. That means low or no emission vehicles. And we're poised to bring in our first purchased electric bus, hopefully by the beginning of next year. And there is a certain story that goes along with that bus that I find very exciting. We've partnered with our long-term bus manufacturer Gillig Corporation out of Northern California. They're an all-American bus maker. They've been in business probably since the early 1900s. Are they healthy? They're healthy, very healthy. They've survived the San Francisco fire in the early 1900s. And they've recently just moved. They moved to Hayward after that. And then they're now in Livermore, California. But we've had their buses since 1983. So we've been a long-time partner with them. They've partnered with the Cummins Corporation. Now Cummins is one of those products. Diesel, diesel. Yeah, when you think diesel, you think Cummins. Most people have an experience with Cummins and maybe don't even know it. They're that ubiquitous. They're a $17.2 billion a year Fortune 500 company that they're bread and butter in almost 100 years has been diesel engines. Now they've chosen to turn the corner and- Go electric. Go electric. And their first electric- He works for them. Yeah, and so their mindset is there that go along or be left behind. So I'm glad that Gillig and Cummins, our long-time partners, have chosen to be leaders and that we're moving forward with them to bring a bus to market as part of that federal grant. Okay, so federal grant, 750 apiece, at least for now. Deadline 2035, a city deadline to change out, among other things. I mean, I'm sure there are other changes too, but on this one item, change out all the diesel buses in the city for electric buses, presumably the Gillig- Gillig? Just for this purchase. Oh, just okay, but whatever manufacturer it is. Between now, 2018, you said the first one comes a year from now? Yeah, we'd like to have the first one in probably at the start of 2019. On the road, operating within the schedule, within the fleet, so to speak. Yeah, normalization, just a regular bus, just one of the fleet. Okay, and then gradually introducing more of these, maybe the same brand, maybe different, who knows, over time to achieve 100% by 2035, which is 17 years, 16 years from next year. So question, how fast can you go on this? Because ultimately, it's a matter of the federal funding and the money and taxes and politics and changes of mayor and administration and city council. I mean, there's a minefield out there, really, to get where you have to go. How fast can you go? I mean, so one in the beginning of 2019, how fast do you see it? Because ultimately, you have a fleet of how many? 500? Over 500, about 540 right now. Yeah. And so what we have to do is it's so much of us just pivoting. You can't turn a ship real hard into this direction. And the mix of renewables that we've committed to use before 2035, that could be anything. And I don't wanna, I think now that the city has a chief resilience officer appointed, Josh Stanbrough, we've had a lot of discussions about what is a resilient source of energy. So for me, I think about it, I don't necessarily want 100% electric fleet because if something happens that impacts our electric production, we have a transit system that can't run and we have no mobility. So diversity is always good. You're gonna get hydrogen? We would all consider hydrogen. Hydrogen, I think, is still in the test phases in terms of transit. And electric vehicles were probably there 20 years ago. But now electric vehicles are a reality. They're in place, they're operating. Better and better all the time. Better and better all the time. And the price in terms of battery capacity, storage and range will go up as prices come down. So electric is one prong. We'll be looking at other alternatives, including hydrogen. And there's a significant, one of the unique things about our bus system is we do some really long routes. I mean, our route 55 goes from Alamoana over the Pully into Kaneohe, runs along the whole windward coast crest to the top of Kohoku, ends in Halibu. So long way for a battery. It's tortuous grades going up the Pully. Perhaps those get swapped out last with diesel electric hybrids. The diesel can be sourced from biofuels. And I think our biofuel production is ramping up. And while earlier on we, the engines were not made to tolerate a little bit of how the mix of biofuel existed. Nowadays, the engines are more manufactured to accept biofuels. Okay, so we have electric, pure electric. Just like cars, we have hybrid electric with using a certain amount of diesel, less, but still diesel. And then we have, that I mentioned, hydrogen. And then biofuel. That's another one you've introduced. Any other possibilities for the fleet as it will exist in 2035? Well, we're open to looking at anything. We really wanna look at how we can accept and implement. We don't want something where the initial cost of entry is infrastructure wise. I don't wanna spend 10 buses worth on just a fueling station. There's those kinds of balancing of budget that we need to do. But isn't it, don't you get a better economies of scale if you say, I want all one kind because I only wanna have one kind of fueling station and I don't wanna have different, I don't wanna have five different fueling stations for five different types of buses. Exactly. And I think our maintenance guys would definitely hop on board. They're probably, if I were to say, we're gonna do one kind of everything and we're gonna have one method, I'm sure they would cheer that on. But resilience again, if that one source happens to get quashed, we don't have an alternative. So we do have different bus divisions or maintenance homes for the different vehicles. So we could diversify our fueling based on where the bus is housed out of. In terms of green, what do you agree with me that pure electric, which is fueled by electric generated from pure green sources, purely renewables, is the most pure in terms of climate change carbon emissions into the air. So that it all depends, and I'm glad you mentioned, what did you call it with the utility? They had an acronym that you were rolling out. EOT, electrification of transportation. Yeah, EOT, remember that, EOT. So you need to have EOT coming from the utility. Because if the utility is using diesel, they're not really getting it benefits. Quiet, I give you that, but you're not, you're still using diesel fossil fuel to run the buses. So you have got to be working in parallel with them the whole way through this period. Yeah, and it's not just about government shifting their role. All the partners that come along have to shift their role. And I like to say that this was the first time we recently went to a transportation convention, a huge convention in Atlanta, Georgia. And we partnered, we went along with the different county providers, we went along with some of the private transportation providers, Juan Electric was there. It's the first time we all kind of linked arms and we showed up in a big mob to every single bus manufacturer. And the bus manufacturers were kind of floored, they're like, how did you get all these people in the same room to talk about this? I think individually in other municipalities, the government can't do it alone. They've other places where they tried to deploy a good amount of, or even one electric vehicle, they've run into problems with the utility, municipalities and even other departments. So our talks with Juan Electric have been productive to the point where we realized if we were to charge an electric bus during the peak demand time, it does not pencil out to be cheaper than diesel. So we have been working with HECO to devise a charging strategy where they have something called the duck curve where when the sun's productivity is high in the sky and all that solar energy is being fed into the grid from photovoltaic systems, say between just 9 a.m. or 3 p.m., let's say, all that energy is getting fed into the grid, nobody's home spending down that energy. So we'd like to actually charge our buses and we hope to get a very good tariff to help spend down that excess energy and thereby allowing HECO at some point to maybe allow more solar on the grid. So it's a real partnership there, but you can imagine all that coordination that has to go on with that and even for us, we have to upend for the longest time, probably for 100 years in transit, we fill a bus up with diesel, it goes out on the road all night, comes back at the end of night and that's what it does. Fill it up again the next day, yeah. Yeah, but now we have to bring the bus back, charge it because that's when it's cheap and then we see the huge savings in energy costs. Yeah, and we don't have time for that conversation now, but similar issues exist with rail. Yeah. Do you ever see a time when we'll be putting panels on the top of the bus to sort of trickle charge it as it depletes? The amount of power that actually is required by that, probably you wouldn't be able to see the ratio of energy production that you need. But we have looked at putting charging solar on top of the stations to just power lighting and on those bases. Yeah, yeah, yeah. Well, finally our last discussion, so to speak, John, is how do you get this done, given all the changes in a free society? You know, with all the tumult of government and all that and the change administrations, how do you get that done? I know you had one thing I think is clear, you've got to have people trained in planning. Correct. Like you. You're a breath of fresh air to have you there. You're not political, you're a professional and you're trained in something the community needs. But you also have to get the community up on this. And I suspect that was so when you went to that conference was in Atlanta, when you went to that conference to see all these people from all over the country. Things are changing. People are coming together on municipal transportation and you're part of a movement. But how do we ensure that these plans will be realized? How do we ensure the city government remains responsible and responsive, responsive to the public need, the public wish for complete streets, the public wish for clean transport, what do we do? And if you wish, you can tell them on camera one, you can turn your chair, you can look right there and tell them what they want to be doing and thinking in the years going forward. I don't know that I want to actually address the public right on as a hypnotic thing, but I will address you. While I think you've upsold my role in this, I do think the strength and how we do this, it has to, exactly as you said, it has to be people-based. And in Hawaii we have a strong base of continuous labor. I might go out with the mayoral administration, but I have to impart upon the people that I work with that these relationships, you build them. So no matter who's in charge, the mindset carries through. And I think that's the seeds of what is being built right now. And with strong partners in the community and the environment, I think there's enough upswell that we can carry these motions forward. And we can just have a better livable community, at least in terms of transportation. Yeah. Thank you, John. John Nauchi. Thank you. Deputy Director of DTS Department of Transportation Services here in Honolulu. We wish you a long life and long participation in all of these issues. Thank you. Aloha.


tretotela lesa pakutupela uksena minu kwa tupela, kwa kutila tuapitava UPND mu 2021. tretotela lesa pakalambasana, but we should not take our victory, we should not take it lightly. No kumuna bantuaba yafile UPND uku bama power, kwa mbo kwa muna kwa tifipua. Abantuuga waikala zi, tekoiba tini shifipua. Sometimes Abantuuga waikala zi, it is out of respect. Nipamulandu fewamuchi inshi, wakua tilen tungulushi, you will hear that you will see that some people will be quiet. Even if they are troubled, even if they are victimized, they will remain quiet not because they are not seeing anything wrong, but it is out of respect. But now we know chinshu yo na uku labensh temu ya kuibati, you can't take it anymore because efomusangila tabantuwa hii paya, bada basha kosa, efomusangila tabantuwa hii kurika, bada basha kosa. Because bada filu uku landa limbi aletino kuibati ngana landa intungulushi shisha lakalipa. Uyumunandu yu mueluwa, mweluwa inshi mwishwenu kumishwa, mueluwa perthiasu wa kukopa beot. Nachi lila no ku lila ilio achistashia ama griverses ya kwe. I don't know if he stood on UPND as a council, I don't know whether it's Chingola or Kitwe. But iishu ya kwe iri na yadimu dairy nation tabroid. Where the dairy nation tabroid actually stated that UPND leaders as neglected its people. And some people took it lightly. Some people took it lightly but that is the truth. That is the truth we've been neglected. We've been forgotten, completely forgotten, completely leten off. Ukufuma po tuwa pone na, fwewa pona.  Takuatala aba po nangu ko, nangu imo. Takuatala kfuma po ko nangu imo. Ukufuma kumu ulukuwa karamba. Uku tuwe wokutila chawi papakupona kuntumu apona. There has never been a ko. Aba ne soba shakwete shukoya kuchita petition ama cases. Tabastre petition. Some of us didn't want to petition the cases. We were told to petition the cases. And we petitioned the cases because our leaders said so. They said petition. I am very observant. Daba observant sana na lemona ilu ama cases. Aba kansela aba pf, ama kansela zwa pf, wonsobo bashtre petition kuriwa UPND losing candidates. Wonsama kansela zwa pf, bariba pila ma loyas. Ukufuma pate abo. Kumi esku pate, takuatila kansela nangu imo, uashtre petition, uo itilonga ni nocesu cha UPND, cha afire kona loya. Aba we ni na ma cases aba ku UPND, ama kansela zna ma kanso chi amen, aba we ni na fioruse loa ku alesa. No one was helped with a loya. Except members of parliament. Ama members of parliament, baritu afuako na ma loyas. Teteinpon teteinbe pobofi. But again you will find that ama loyas obo wa tu afire na bena, I don't know how much was given to them. Aba bena ma loyas ua tu afire na bo. If we were losing candidates, nifoto wa mbiroku basunga, nifoto wa mbiroku barisha, nifoto wa mbiroku beinisha, uku fuma kwa lefuma. It is costly, mwakot, uku puisha mula nandu for 3-4 months. Kwa aba ma pepala ya ku, tka shani, ifi ya ku, tta fingi, we spent even the little, which we had, and a lot of us, to isa ngiloku ingila na mwukongole. Pa kutila tu titefie, ifi otoa ngiloku titefie, pa kutila temilandu yesu, nilandu ya kubambi, shamwene po provinsho ofisha nangumo uku tita attend ama sessions ya mula nandu andi. Shamwene po provinsho ofisha nangumo uku muna atita attend umula nandu andi. Shamwene po wakunashonu managementi nangumo, ofisha uku tita attend umula nandu andi. Aba lechitagofi attendu umula nandu andi. Ma district ofisha wakutefie ulu se. Now you look at feeding, feeding the witnesses, transporting the witnesses across the district. Aba mo bale kuka 3-5 days bale kuka. Pa kutila vese bale titefie api amkot, kuma kese ziyesu asite testify, bale puisha 1 week, tu leba liisha, tu leba suonga, tu lebe insha, batwe muntunishinoku pona wa lipona, nokuluso umula nandu nishu wa lilu sa.  Leilo, taku nandu umulandu wikonstitushonu kot, nandu umo uwakubuteko, uingakutumi na kufonu kutila chachabipa, mebantu wakua lesa uktila tibachita api umulandu wa konstitushonu kot, nalaisaku koti, jisengunfekufi umulandu owe, taku ali umuntu nangumu na kariayo, panjtari onseo na sangiroku konstitushonu kot, ilona bale pela judgment mu konstitushonu kot, ayu was the only UPND member, at the same time the person who was actually facing that case in the courts, nalefua yoku fein tamkoti, when they were reading the judgment, nalefua yoku farm kot, because there was no one, there was no one, there was no one to say top son, shipa uri muaume, taku ali umuntu nangumu wa kumkoseleisha, taku ali umuntu nangumu umo uwakubutu we muaume, talala atiri fei wino, the only people who were in that court, ma koto official sewe kaveka, avantu fewa limu pii mu kot imu liya, kukonstitushonu kot, ma supporta zewakua kandide tichibu e, uwa kupifu, eva limu fei fulu kupela support, kumuntu wabo, inena limu fei nneka, I wanted to die that money, I wanted to die that money, because it was so painful, no one from the party, no one from UPND, no one from the branch, no one from the constituency, no one from the province, no one from the national management, no one from the government to say top son, nichabi ipa, pakanaru sumula andu wa shita pronounced judgment mkoti, nanguna ndilok fuma kuru sa koku, it was by the grace of God, it was by the grace of God, nomba, up to today, no one has called me to say top son nichabi ipa, pafio wa pitamu, top son wali womba, people wanted to kill us, people wanted to kill me, we have spent the little which we had for our children, no one can even visit you, no one can even call you, because everyone is busy, because we should wait, we should be patient, and we have been patient, and next year it will be one year, one year into government, no phone call, no nothing. If you are going to listen to this video, suspend this man Mr. Chifida, initially he didn't want to suspend Mr. Chifida, I don't need, I mean, suspend this man Mr. Chifida, he didn't want to suspend Mr. Chifida, he didn't want to suspend Mr. Chifida, I have served UPND, I have served UPND from 2006 to 2011, he didn't want to suspend Mr. Chifida, he didn't want to suspend Mr. Chifida, 5 years I served UPND, I came back to UPND in 2016, this year I am croking another 7 years in UPND, I don't have a position in UPND, not even at blanch level, not even at blanch level, shakwata position me UPND, umuntu kandide, uach treko fea aspaia, alusa na muli naine, ninewa na imakene pa UPND, kaso nteka.  If you know you have an office, I am coming to Lusaka next week. I am coming to Lusaka next week.       Be tactical. Tactical is the way you think. I must actually lay because the ground where I stood was a fertile. You have neglected people who suffered for the party, who truly suffered for the party. I must actually lay because the ground where I stood was a fertile. You have neglected people who truly suffered for the party. I must actually lay because the ground where I stood was a fertile. You have neglected people who truly suffered for the party.  We must actually lay because the ground where I stood was a fertile. You have neglected people who truly suffered for the party. If you want to chase me Will I die? No Tete mere chula vantuba mi chudidi Not even a core Not even a core Umuntubamu lasabamu kontolu kulu Bamu tuwaraku kut, constitutionu kut Ni ita mu kut But pf ufulu Been one official from the party Ha ha ha ha Yay Yay Yay Yay Yay Of the one of court sessions No Provisional official Two cases in a winner Ushemu, mulandu leinda shani No one could to call Ushen indana ma shakufi yusilefwe No one could to call Two ingenamu kongo li Umulandua ku This is a diploma. This is a diploma in teaching. I'm a teacher by profession. This is a diploma. This is a degree. This is a degree. This is a degree. So 10 stone. 10 stone. 10 stone. 10 stone. So if you want a job, we all land there, we'll refer to 10 stone. Not topstone kunda. Uredi apanshile bombandechu la panondechu la, but in the panga 20 pini in a month. I'm able to make a 20,000 kwacha in a month. But that 20,000 kwacha can't take me anywhere. Because it's special, in enda kudi labantua maanda. And the fukumbo kudi labantua maanda. Nadi temuku pera kumunimo akwalesanspera maddu wa wanpini. And the pelo muli mwa kuaalesan da la meishingi. And the pelo abantu avalanda. Not 200 kwacha. I give money. Niti ma ashani yo mwa kuaata mune pepekaba kote. Nende keba sekriza hijainilo. Tata mwa luba buhe lenimu uchila. Tata pa deba kamiyeba. Jenny Jenny Jenny Jenny kusenda nabu eno kusenda nabu eno tuwadi pusanazana techin senden senden mo and senden senden you just not treat me eno you treating somebody you don't treat me like that I will roar like a lion I will roar it's only God who knows let me say this I made more votes for the president across the country because of my talking I know it I made more votes for president in other districts than I made for president so ma tu senda kofi eno ma tu senda kofi eno I think Nalanda sir