Hello and welcome you ever Enter a shell and then go a shell deeper and shell deeper and you have these children's shells and these parent shells and you have completely Lost track of how many shells deep you have gone Well, there's a variable fault for that a system variable I should be able to say echo dollar sign sh for shell LVL again all capital And that will tell me how many shells deep I am so I'm 18 shells deep I can run that again, and now I'm 19 shells deep I can run it again, and now I am 20 shells deep and if I exit out of one I can run it again, and you can see I'm 19 if I exit exit exit I can run it. I can see how many levels deep I'm in which could be helpful and It also works with their shell so I can go into my z shell here and I can run that same echo dollar sign shell level Variable, and you can see I'm this may shells deep and I can go again and again and again Again, and I can run that same variable Echoing it out, and you can see it on 21 levels deep This could be useful again if you don't know how many deep you are and you're just curious You could do that, but I could also see this being useful if you were to Put something in a script or your shell settings that because sometimes you're a few shells deep and you start exiting out and You don't want to exit all the way out in some cases And you don't know what level you're at and you might exit too far and completely close your terminal You could theoretically I haven't tried this But you should be able to alias your exit command to check that variable and give you a warning if you are at the Top-level shell. Anyway, that's just thought I found this interesting I'm just looking through system variables here, and that was what I found interesting. So again I'll sign shell level And I can see that I am 11 deep now. Whoops. I did not mean to go into it Okay, for most of you it's probably useless, but it's just interesting information It could be helpful and again I could theoretically see somebody putting an alias in there for their exit command that checks that variable And if it's at the one the you know the top-level Shell it will give you a warning so you don't accidentally close your terminal if you don't want it to anyway Thank you for watching. I hope that you have a great day


Recording is on. Thanks everybody for joining Jenkins Docs Office Hours. See, I need to find our notes. I've assembled them. And here they are. Okay. So Jonathan, since you're here, any questions that you have that you'd like to start us with? I didn't see our agent until today. Today was just Q&A. Just question and answer. No, I have just a... I need some clarification for you. I would like to have your opinion about the PR that I created some days ago. And if possible, I would like to have more information about the Community Bridge too. I read all those links that you provide to us, but there is no valuable information to members to send their proposal. Maybe I didn't find it. No, you are correct. We are not ready yet. I don't think we're ready yet anyway with a process that proposes how people would send a proposal for a Community Bridge project. Yeah, I don't understand the workflow process to work on. Right. Well, so let's put that as a topic and we can discuss it. And so Community Bridge proposals and topics, right? And workflow. Okay, good. So I'm actually going to go ahead and share my screen and we'll just look at my screen as a... as our source for the notes and we can talk to it there. That's... it's certainly no worse looking than I am and is a lot more organized looking than I am. So there we go. We can argue that, but... Yes, yes. That'll be enough. That's great. So Community Bridge is... we don't have a project proposal workflow defined yet. In the past, in the past Community Bridge project, we reused the Google season of code proposal workflow. Now it was a code project and therefore it fit to use Google season of code. I would assume we'll reuse the Google season of docs process for Community Bridge. So right now that would mean we would draft proposals. They would go to probably the Jenkins governing board for review or to the mentor team for Google season of docs. And then a project would be selected, that person would be funded and off we would go. Now is that what you were asking, Jonathan, or is there some other question? Yeah, yeah. Just for clarification I asked for, because I have some doubts about it. But what do you need to... we need to prepare something. There is some timestamp to work on, like a stone mark, like a timeline or nothing. Not yet. Not yet. So just let's wait for it. Correct. Right. The first, the most crucial thing here is funding and approval to do a Community Bridge project. We'll have to come from the, comes from the governing board from the Jenkins board. And that hasn't been granted yet. And so that's the most crucial thing before that until that happens. Right now, our total dollars sitting in Community Bridge to use for this is not enough to fund it. And so, so we would, we may have to request more funds, or we may have to request donations, or etc, etc. Okay, so we can wait for a signal from Jenkins organization. Right. Right. So wait, wait for an announcement and it will be, it will be made very publicly, right? So, of a Community Bridge project. So the last one we did, we did with a blog post. We did with a mailing list announcement. I don't, I don't think that we would do a webinar for this one, but we might even do a webinar that's, that's a possible for sure. In the past we've used blog posts and mailing list announcements. Okay. I would expect we would in the given that now we're using the Gitter channel we would likely also announce in the Gitter channel. I wanted to, to comment on this in case if participants of this special interest group, or like any Jenkins project participant participants can facilitate funding, please let us know how can we help. Oh, great. Okay. That's a, that's a very good question. Let me show one example. This is when you might mention to, to others with whom you work or to employers. So if we look at the Jenkins Community Bridge page. We're accepting donations. And let's see where is it. So you could pass for instance to an employer. Then you say hey we would like you to contribute to Jenkins Community Bridge and now I may have to go find the correct location just a minute while I go looking. It is not there, but there. Okay, so there is a donate button somewhere in these things. Donate, where is donate. Maybe I should just do it like this. I know there is on GitHub on different. Oh, yes, yes, that's a very good suggestion I should just go there because of course it also exists there. I think I can find it here. I'm contributing down. Okay, so because I know that the donate page has been added. No, that's not it. Okay. So it may be that it's still in progress. So let's use Vlad suggestion and go to GitHub. And get up. And I think if we look at core, I believe it's been enabled on core hasn't it. No, I don't see sponsor sponsor sponsor. Oh, that one. Yeah, there we go. Thank you. Excellent. Okay, so this page shows us that we could. And so individuals and organizations can contribute. Yeah, I believe this $3,000 expense that you see here was what we use last year to fund the Jenkins Community bridge project that we ran last year. So we would be delighted to have more contributions and big green donate button. Thank you. Thanks for guiding me through that. Sorry for my lack of skill, but yes, that's that's that's the way to get there. Any other questions on community bridge. Hey, we had another topic here which was Google season of doc proposal details doctor solutions and tutorials. Vlad was this one you had asked or is there somebody else who'd asked that one. I actually added this. And this is a follow up to our submission of proposals which I guess happened last week. And I would like to address my, well, my proposals, I just wanted to keep them somewhere. I posted today a question on Docker discussion group and got response from Alex that nothing is developed regarding to my proposal. And it was basic proposal was about creating something very simple, which will allow to generate set of Docker images with Jenkins inside. Something similar to Marvin archetype, for instance, archetype generate you can create different archetypes up to 15 different solutions predefined. And we can, well, just an idea do something very similar to this. The main goal from my point of view is simplicity of this kind of tool or plugin I have no experience developing Jenkins plugins. So users can very easily build and instantiate run Docker image which will do something very specific. And the specifics will be defined by Jenkins project or by by Jenkins basically community bridge, and the user and user will need to choose between solutions which are more appropriate to his goals goals. And again, there is like wide range of different possible solutions. And I would start in case if I will be allowed to implement this from simple one and go up like increment complex complexity, not vice versa. So kind of bottom to up approach versus top down. So, yeah, I will start with Kubernetes but go eventually to Kubernetes. And I think the idea is interesting. The, the we have tutorials currently that for instance run run an agent so run a Jenkins plus an agent to build a Maven project. And we have a Jenkins plus an agent build a node node JS project and Jenkins plus agent to build. Let's see what's the other Python project. And so, so you've got some good working base to think about it. How to go. Were you considering. I'm assuming you were not considering other components in in this Docker image. So, for example, not considering placing a source control system inside this image. Probably not. Well, it depends how we run this. I guess. So if there is like volume will be mapped to the source then during this situation place. It will be this image will have access to the sources. Yeah, you are just my main goal is to attract new users so they will become adopters or Jenkins so we can increase their user base I know it is like already significant enough but still like. And the reason for this is for the simplicity. I believe this is how main technologies got very popular like how Internet appeared basically HTTP HTML is very simple kind of approach solution versus previous attempts. Or like rest restful approach is better than simpler than so that is why it was adopted by industry. This kind of idea so simplicity is the key for adoption. Because like Jenkins is already complex enough. So, we already have good base of professionals, like programmers, computer scientists and so on working on this, but something like to popularize it and make sure that like, My, let's say, virtual grandmother or virtual granddaughter will be able to succeed all virtually. There is no such person, but they will be able to run it by simple command and create Jenkins apps. Now, regarding this tutorials that you mentioned in the previous paragraph, I guess they exist but they're using how to phrase, not official Jenkins image they're using blue ocean. Jenkins evolution, which is my understanding is deprecated kind of not supported any longer. It's, it's not only it has very specific problems that we would like to get away from it. Absolutely. Yes. So those tutorials are are flawed in the sense that they're using an image that then if users if users say, Oh, I'll base my work on that tutorial. We think they've made a mistake, right, rather than basing themselves on the blue ocean image they should base themselves on the production Jenkins image. But that's that's disconcerting for them but I just did the tutorial on blue ocean on the blue ocean image and the answer is yes that's true you have to make that disconcerting transition. So if those tutorials could be switched to to not use blue ocean, that would be a win for the users for the students for those who are studying. I may mark a comment also, instead of saying not using blue ocean. I think blue ocean is very interesting attractive plugin, not using the ocean image, not but blue ocean plugin maybe still included through plugins, text or whatever inside plugins. You make an excellent clarification, absolutely wholehearted agreement that we don't want to. We want to in fact encourage them to use the blue ocean plugin to visualize pipelines. It's an elegant way to do it to do pipeline editing and visualization it's very very powerful. Using the blue ocean docker image is an anti pattern. It's a negative because of the problems that are in there built into the blue ocean docker image. Yeah, good, good clarification. Thank you. Now Vlad, I think you saw my note on the custom war packager. As a, that one is a relatively exotic thing I hesitate to, I would not envision us being able to tell a new user of Jenkins. Oh just use custom war packager to define your own completely custom Jenkins instance. That's, that's to me just too complicated for them. It is certainly an excellent technique for experts. Oleg makes very good use of it and others make very very good use of it. But the custom build service. Jenkins custom Jenkins distribution build service is working towards what could be an end user acceptable and end user usable. Ready to go you define the configuration you want or pick from a menu and conceivably we could have have something that says oh you want to run this tutorial. Fine go to the custom build this Jenkins distribution build service and choose this distribution. And then they would get the this custom probably docker image that's built for them or custom something built for them. That would meet their need. I know that this this project is part of Google season of code, I guess season or some of code. Properly. Although my understanding was that this specific project was targeting UI so users through UI will select what they want to build by clicking proper plugins or whatever. I was thinking about doing something from CLI kind of tool which you can just like put some option. For instance, whatever name of this tool or whatever, generate or create or run and option like number for instance, and this number will be mapped to one of our solutions which we predefined based on something to decide based on statistics, the most popular solutions the most widely used less issues well whatever would be the most appropriate rule to define this kind of solution. But, but you're right, I need to like look more closely into this project. Definitely there is some kind of overlap in the section. And again, I'm putting this for discussion suggestions and so kind of follow up and providing more details to ideas which I submitted. Any other questions or topics you'd like to we'd like to bring to the discussion. Wow, can we speak about the DPR that I said at the beginning. Absolutely. Let's do that. So that's, and which were the PRs Jonathan. Yeah, I sent it through the chef the chef. Perfect. Let me grab it there and let's take a look at it so 3481. Yeah. Okay. Okay. So, some days ago, Oleg recommended not to use raw HTML HTML and the right documentations. But that's the P this PR and the that one other. I, I use the already imported bootstrap to create this effect of to go visualization. Are you seeing on the gift. Hit the button that show you the help or not and you choose see or not in the image. So as the back does not offer to us a feature to do this. So you will, you will prefer to keep this button with raw HTML or you recommend to remove it too. So I would tend to advise removing it, but let's let me look at something different. Let me show you a different one because there is a thing that does we've got something already that does a hide and unhide in a different context that we might be able to use or might be able to use to justify the technique you're showing us. Let me see if I can find it here it is in the plug in the pipeline documentation. If we look at pipeline syntax, I believe it is. There is a section which will show us this is purely declarative. I may need. Okay, pipeline syntax reference. Okay, there's declarative Meg, maybe you know where it is I. There is definitely a segment where I can see. See using doctor maybe this is okay let's see. Yes, there it is good. Okay. So, let's see first question can everyone see my screen okay. All right, so here is here is a segment of the document that describes using Docker with pipeline. And we give the preferred solution first in declarative pipeline declarative has the benefit that it, it is immediately parsed in its entirety. So if there's a syntax error late in the in the pipeline it's detected immediately scripted doesn't do that. But some people have found that hey they have to have scripted and so we have this here which says toggle scripted pipeline, and it presents this other thing. Now, I, I haven't looked in detail Jonathan to see how it does this, but I'm pretty sure it does it without without doing too much JavaScript without doing I suspect any JavaScript magic because the people who worked on this particular thing I don't think we're JavaScript programmers. Yeah. Yeah, it's quite complicated, sorry. That solution but I will replace it. I wish that there's the one and replace it. Well, at least compare it I'm not sure I'm not I'm not confident yet to say who you should replace it. But if you compare what this technique is. This technique is helpful because it in this case does I think what you were trying to do which is initially the user benefits more by seeing the list of steps without seeing details for each step right there's, I need to know that there are five things to do. And if I put the pictures in there all the time. I don't use track of the fact that there are five things to do because the pictures obscure that, whereas if I could toggle to see the picture expand. Yeah, it's much more understandable. It's the same idea that Vlad tells us it's to keep simple. So, no, no is visualization with you in the first contact you have a lot of information you get lost. Why will you read my study. So I will study this link that you show to us and if you work well I will replace it. Well, and I'm going to put that into the notes just in case so that is a place to alright so. So let's take a look at that. Let me make it so. Pull requests. Discussion. So it was PR 3481 which had the expand and contract. Unhide and unhide images. Sitter this. Yeah, and I wrote to the PR and I opened the issue to to create a plugin to ask doc. So if you come back to get visualization there, there is the link to create a new plugin. So that was the description at the description. Yeah, the first. Oh, yeah, yeah, second bullet. Okay. So, in fact, I, I wrote the code, but I'm not I'm not a rugby expert. Do you know something in our group that have have the expertise to write plugin to to help me in some question. Well, I know that Daniel Beck has done it. I know that I will be using some Ruby code to do a thing that I need to do for the Jenkins infrastructure page. So I'm going to be getting into it. But if you're asking somebody who has Ruby skills that is definitely not me. I am willing to experiment and learn. But I certainly know people who have written code in the in the Ruby here like Daniel back. I think he has as well as your clinic connection he has based in I believe he's in. Okay, I send a message to all again. So maybe he's answering the next two days. And I come back to next help to YouTube. So, if I can't resolve alone. Great. All right, so that was the first is the is the second to the same. It's the same as just for over samples. It shows our two different phase one about the parameters building. And the second one is about the agents. Excellent. Now, would you be willing to share a tutorial with us I am truly impressed by the scrolling image that is here. How did you create that. You're able to do that same technique. Yeah, it's a help to the review review to see review the change. I can make a tutorial and I think to you. That would be great. If you want to just record something. That's great if you want to just tell me that's fine I I've just I've seen people use this kind of technique where they'd use what I thought where it must have been animated gifts. And it's marvelous. Okay. You just need a program to recorder your screen. So you export the key part in the website that support this. And so you can put a hdm tag image tag. It's on this. Okay, great. I will send you which page. Oh, that would be wonderful. Thanks very much. Jonathan, I had done this sometime in the past by already forgot, if it is possible, I would like also to get your. Yeah, okay. I use it. Okay. I'm sure I misspelling your name Jonathan. It's correct. Oh, very good. Yeah, I've, I've fallen in love with my full page screens capture plugin that I use with. Google Chrome, but it's a different thing than, than scrolling gifts it just gives me a static image whereas you've got a way to show images that look like a movie. Yeah. Some documentation website to use a lot of gifts to show complex steps for the users. Nice. I use gifts to my PowerPoint presentations too. So while I'm talking with the people that gives is running and background. It's easier to show samples while presentation. Nice. Thank you. Any other questions. I received a mail from Google season of dogs, just asking for to confirm with the hours organization. If they receive our proposals correctly. It's so you receive the everything it's okay. As far as as far as I can tell from old age reports. That's a good question has the organization receive the proposals. Yeah, they just asked for confirmation. And the answers as I can tell is Oleg reported to the mentors that we have received it received them. Okay. Now, we did have a he's he is Oleg is currently assembling the links to all the mail messages. He did have a surprise. I was surprised when Google season of docs sent the proposals to the Jenkins docs mailing list. That was not where we expected them to be sent we expect expected them to be sent to the organization administrators. We saw them like detected them and has has been able to get what he needed out of them. So we think we have all the right information. So and the reason that was a surprise is the the list did not accept those postings. And that was really a good thing. Oleg was really worried because we didn't really want everybody's proposals sent by email that was we assumed we would review through the website and be able to give feedback and ranking there. Was that clear enough. Yeah, yeah. Any other questions. Not for me. Go ahead. Just general question. I wanted to ask, somehow related to what we discussed today about using, for instance, plug in plugins.txt file in configuration as code while we're building, for instance, our own configuration of Jenkins. I mean, what if somebody knows what would be the best approach or best practice for configuring this set of plugins. I mean, the name of plugins and versions. Is there kind of standard approach for doing this, or maybe there is some tool to generate this plugins.txt file. We need to base from the previous configuration of running Jenkins application, export this file, something like this. What is the best approach for doing this. Because general idea is very attractive, very interesting to include this and this docker image will be configured with all these plugins, but how we generate, how we create this this text file, which is very simple kind of in format. But about the contents, how, what is the best way of doing this. Right, right, very good. So, so there is a, there are several ways to generate that so several different ways, right to generate it to assemble plugins from a list. There's plugins.txt. But that requires that you must must enumerate and this is in the docker image right in docker for image definition. You must list every plugin. So it does no dependency analysis. You just must list every plugin. Mark, are you sharing correct screen. Oh, I don't know. Let's see what do you, am I sharing a screen, I think so do you see my typing. Good question. Yeah, I'm here. Oh, dear. Okay. So let me stop the share and I'll restart it just to be sure. Okay, so you should see a Jenkins Docs office hours screen. Yes. Okay, and ultimately so ultimately this one. You must list every plugin, including all dependencies. And there is another way to generate that same file using the plugin installation manager, manager tool. The same tool that was created as part of last year's Google summer of code. And what it does is you give it a list of relatively few plugins. And it will grab that those plugins and all of their dependencies. But this one is not yet integrated into the Jenkins Docker image. Certainly on the list, we want it done there but it just hasn't been done yet. It is integrated right now inside all eggs demo configuration as code. Correct. Yeah, so, so one of the, the install dash plugins.sh is reads plugins dot text and downloads files. And it is integrated through the Docker image. So now how to generate that list. I think was your original question Vlad, how to create a plugins dot txt file. And the technique I've used. This is a terrible thing to admit that the technique I've used is I go to my Jenkins installation. Let's go there. And in my Jenkins installation, I go to the system info page. So that's manage Jenkins system information. And then if we scroll down after environment variables there's this big table of plugins. I copy and paste from this thing. There's a little bit of editing magic to turn it into exactly the things that plugins dot txt needs. So this system info page is all that I used. Now that is that is a flawed and terribly imperfect way to do things but it worked for it met the need that I had at the time. So basically you derive from running image something that you know it's good enough. Correct to copy and paste. Right and that that has the benefit that I absolutely know I've satisfied all dependencies because Jenkins did the dependency resolution itself. Now I've used another technique. But this one is not not viewed highly favorably by others so I wouldn't claim that anyone else should do it. I have a get repository that has large file support enabled. And I just check the plugins into that get large that get LFS repository. But that requires that you pay GitHub extra money each month in order to be allowed to use LFS. It's just so so convenient for me that it was it was easily worth the few dollars a month that get help charges to use large files. I'm not going to put that in the notes because it's one that I don't think anybody else should it should emulate it just happens to work well for me. So glad did that address your your question there. Yes. Now I, there are there are probably better ways to do it than either of those. It seems likely. I just don't know what they are and so then it'd be best to ask him to get her channels. Any other questions. I just want to ask one more question and this is related to the issues are general approach are in Jenkins project is my this is my understanding that some of the issues are tracked by GitHub. We have GitHub issues for some components. And some components. are tracked by Jira. And I was trying to find out if you have specific component how to determine the application which tracks these issues. I visited GitHub or Jira, and I found solution like if you go to GitHub, the project name and component, let's say Jenkins CI Jenkins slash issues. It will redirect to pools. So there will be no issues on GitHub only pull requests. It means all issues are tracked by Jira. Or maybe there is some other solution so or approach. I just was wondering. No that you described it well. So you're the heuristic is assumed Jira is the place where the issues are tracked as your first choice. If there's a question is Jira actually being used check the source code repository. And if the issues issues tab is enabled, then it's tracking issues in in GitHub. So the example, let's see let's let's take two different examples there's the first which is the Jenkins get plugin. So plugin I maintain. You'll look here and it does. Oops, it does not have getting used to my new mouse. So, across the top here code pull requests actions projects, but no issues tab. If we take a different different repository let's take the Jenkins.io repository for instance instead. This is for the website. This one notice that it has an issues tab and has good content in the issues tab so it is in fact using GitHub to track its issues. This is one where the Jenkins.io site comfortably can use GitHub to track issues, whereas the Jenkins get plugin intentionally does not use GitHub issues, because GitHub issues do not have a simple direct way for us to manage security issues inside GitHub issues. So we've we've had to be more sensitive there. Now back to your question, Vlad. How can I tell, and the answer is, check the GitHub source code repository. If it doesn't have an issues tab they are certainly not using GitHub issues to track. If it does have an issues tab. It's still safe to check, is there a Jira project where they are tracking those issues. I'm not sure I'll bother opening Jira for you but it's the Jira issues are definitely there. So we have components which are which issues are split between two applications. Well, we have we have, I would say we have components which are in transition. And components in transition typically are going from Jira towards GitHub issues. One of those components in transitions is the Jenkins.io site. We initially tracked its issues in Jira. And we found it was much easier for users and much easier for contributors if we switched that site to use GitHub issues but that means there are still some some old issues in Jira that we are slowly closing Thank you, Mark. All right. Any presentation at Hackfest. You and Oleg and speaking about some plugins that are ready for adoption. What that means? What is adoption to are depreciate plugins or underdeveloped ones? What is what means adoption? Good question. Very good question. So what does it mean to adopt a plugin or for a plugin to be up for adoption? That's an excellent question. So on the plugin site, if we look there, what we'll see is there are labels that are associated with plugins. I have to think of one that might be up for adoption. I think the subversion plugin is up for adoption. Yeah. Sorry, Meg. What was that backup? There's a bunch of backup ones. Okay. So here is there's a if we look at the here's my example. This is the subversion plugin. So if you were a subversion user, you might see that you would see this, this indicator which says hey this plugin is up for adoption. And on the adopt a plugin site, it tells us what that means to adopt a plugin. And plugin maintainers can say hey I'm not planning to maintain this plugin therefore they market for adoption. And other plugin maintainers may say hey, I would like to adopt that plugin. So you follow this set of steps right here. You can email to the Jenkins developers mailing this saying I would like to be made a maintainer. And in that email you tell them which plugin you want to adopt. Pull requests that show that you're credible. Your GitHub user ID and your Jenkins user ID. And, and then you go to work on it. And how does the expectation about just approval some PRs or keep maintaining and in the future, offer them to adoption again. How does the logic behind. So the assumption is that you will, you will make some positive impact. Usually the reason someone adopts a plugin is they would like to release a new version of it. In order and in releasing the new version of it they want to make some changes either. They want to update it to use the latest Jenkins versions or they have some feature they want or some pull request they want there's usually some motivation that says I would like this. And therefore they adopt the plugin so they can do it. We hope that they would then continue maintaining the plugin. But that's, that's up to them, they will be listed as the maintainer, and then they get to choose do I want to continue releasing new versions or not. Okay, and there is another tag that said abandoned. What is the logic for transition from adoption to abandon it. It's just. So abandoned, I think is not actually tagged. I don't believe. Let's see if we've got it. I don't get the subversion plugins that it's set to with abandon it. Oh, did it. Okay, let's look. Okay, so let's see. So when you you click on adoption plugin, click on the link. Oh, I see what you're saying right so there is a plugin. Right. The second paragraph. Got it. It's this right here. But the concept of an abandoned plugin is not labeled on the plugin is not not a label you will see. It is merely an observation made by looking at the commit maintenance history of the plugin. So for example, actually, let's let's take a very specific example. We can find one that Oleg originally wrote, but he no longer maintains called the remote loader plugin. Let's go look at it. And it was released there are plugins that were released last for instance last release nine years ago. And, and a plugin that was released that long ago is probably abandoned. See if workflow remote loader is that way. Here we go. So, oh no, this was last released only a year ago, so it's relatively recent. But there are other plugins that I've looked at very recently where the plugin was last released a very long time ago. And that's, that's where we would apply the rules and say, Oh, this is probably an abandoned plugin. And so we need to follow the abandoned plugin adoption rules. Okay, it's just far for us to thank you for information. Great. Any other questions. All right, then I'm going to propose that we end our session for day today. Thank you. Next milestone on Google season of docs is July 30th, I believe, when the organization proposals will be submitted to Google, and then I believe it's two weeks after that but Google will announce who's been accepted. Thanks very much everybody. Okay, thank you. I'll save a copy of it, and it'll be posted to the list. Thanks. Thanks. Bye.


Ready for unboxing? Today we have a release that just arrived today. This is the PinLux Masterpiece Grande Golden Crystal Fountain Pin. You've got your PinLux packaging here. The outside of the box has a sleeve over the top that we already removed and then the PinLux logo on the black lid. That was a really tight fit but you just remove that and the bottom of the box is blue and you have all your PinLux information about your pin works and the brand information and any warranty information on the insert. Your pin is in a plastic bag and there's another, there's a false bottom on this one but there wasn't anything under it in the one we received. Inside your plastic bag there is more information though about your PinLux piston filler. So you just slide that out and make sure to give it a glance just because this talks about one of the main problems that causes damage to PinLux piston fillers. Here's a good look at this golden crystal. The PinLux is on the center ring there and the trim is in gold. Your Masterpiece Grande is in a high grade PMMA resin material and it has an extra large barrel and this is a good look at the nib and it is branded with the PinLux logo and it's a Jovo nib. This particular pin is the stainless steel nib that's plated to match the trim. The pin is postable and it has a spring metal clip and a threaded cap. The piston is activated by the piston knob at the back end of the barrel and if you're not familiar with piston fillers you just use your piston filler fountain pins with any fountain pin safe bottled ink. Alright so that was a first look at the golden crystal. The new addition to the PinLux Masterpiece Grande collection. Find more information at pincellay.com.


Hey everyone, I hope you're all well having a great day. Thank you so much for tuning in to another episode of our Pokemon VGC 2019 battle series it is Wednesday, so we're in the middle of the week We played a couple of games already this week with this team that you're seeing on your screen right in front of you now If you missed any of the games up to you this episode so far this week And you'd like to check those out go back up here I'll link a card for you can check those out before coming into today's episode We've had some really good games actually with this team We made a few changes from the squad that we were playing with started with last week with the reindeer court And we're gonna have a little bit of fun going into the the rest of this week So today tomorrow will play this variant and then on Friday will introduce some of those Really fun suggestions that you guys have suggested so far this week and thank you so much teaching every one of you That have suggested things and there have been some really crazy comments And I've tried to squeeze as many of them in for Friday's episode as possible because the team on Friday is gonna be a Lot of fun. It's actually in the battle box now So I'm gonna play through today and tomorrow's episode and then hopefully do Friday's and then it'll be a lot of fun Hopefully but I'm looking forward to hearing your thoughts on the squad and what your thoughts are in general on the reindeer court I do like it I can see that it's probably not as viable as it once was in the Sun or the moon series When we first played it, but I still think it's got a place in the format for sure for definite But as always the team is down in the description below as well as a raw poker paste and just the raw paste as well If you can get my words out, it's been a busy day bear with me and without further ado I guess we'll just jump straight into it guys. So let's pop some music on will not forget today and As always if you if you enjoy this sort of content, please make sure to leave a like Do subscribe to the channel so you don't miss any more Pokemon content Do leave your comments because I love hearing from you. This is it's been a bit of a crazy day today But we've got a first opponent. So let's jump straight into team preview Okay, our first opponent today is running a team of kai ogre evil to tapu lele a stack of tucker in Ciderot and a Gengar So this is a really kind of popular call that we're seeing at the minute the the evil ogre team or Vettel however we're pronouncing it and but the premise of the team is to trap your opponent in with the mega Gengar Utilized tapu lele because it's normally scarfed on this sort of build and then you've got a trick room switch with the stack attacker Which is really really very versatile within this team, especially with the trapping from the mega Gengar One of the things that we do have going for us here is that we ha, you know, we're not combating the rain We want the rain to be up. So we've got that on our side and swamper actually does super well in this match we've got to watch out for obviously the intimidate support from the Incineroar, but swamper generally does pretty well here I mean, I'm kind of tempted to lead off with tornadoes Just to get some speed control going but also we could bring Kaioga, Kaioga We probably want Incineroar here. I mean ferrathorn could be also very good in this match like ferrathorn is actually really good in this match If we can keep the rain up Kind of tempted to go ferrathorn Do we want tornadoes? Tornadoes, tornadoes, do we want it or do we want Incineroar for a bit of intimidating support? Let's go. Yeah, let's go there. Let's go there. I'm just thinking maybe Tornadoes would have been better for the speed control for sure, but The same time Incineroar gave us a nice switching to stuff like Gengar stuff like tapilele They're gonna be threatening big damage on our Pokemon like Kaioga and Swampert, you know So we are gonna see Kaioga and Gengar come out to my opponent Like one thing that pops into my mind straight away here is do we play in future thunder on our Kaioga? It gives us a bit of a better option outside of ferrathorn to hit opposing Kaiogas Which we haven't got so many options with right now and But one of the things we do do put a lot pressure on to the Gengar for sure with our mega Swampert and Like to me would protect you definitely protect I mean we probably get a free water spout off for sure without without Kaioga Depends what kind of build the opposing Kaioga is we could just go for an origin pulse I do want a mega evolve, but I probably feel like I should protect here rather than do anything else and Like do a fear getting trapped in that's the big thing I'm not really too worried about anything coming in on Kaioga and an origin pulse to do Like ridiculous amount of damage. So the only thing we're not doing the big damage to is the opposing Kaioga It's just whether or not I click what's about origin pulse I'm probably better off clicking How confident am I that we're out speeding the opposing Kaioga? Hmm. Let's go what's about we'll soon find out But I think the Gengar protects here I think you want to utilize your Kaioga to either knock out or weaken the Swampert and not lose your Gengar So that would be my my best bet I don't see the Gengar like the Gengar could not protect could go for a substitute, but I think We're gonna get punished if they don't and do do something like that for sure No, there's the protect from the Gengar now you've got to imagine the Gengar probably switches out this next turn. Oh This is why this is why we want thunder And this is why I want a what's about is doing nothing nada nada Okay, and now we're in a real Nasty place because we can go for the Gengar, but like I say the Gengar probably switches out I don't think the Gengar staging We've kind of baited that so I think like our best bet is to go stomping into The Kyle I mean we could go for waterfall and try and flinch bird and origin pulse is the Because I think the Kyle that actually goes for a water type attack here to try and get the Swampert rather than the thunder. Okay, so Veltal will hit the field. We could ice punch that slot as well for sure Hmm If someone put can get through this turn, that's that's great for us. I mean that damage isn't too bad It's actually going to the thunder. It's gonna talk it into our Kyle guy. So you don't mind too much Yeah, that's not too bad to be honest as long as the rain is up We are the thing is we haven't brought zonius here, which is like mad zonius right now would be amazing We could bring in fair though Though the incineroar is probably better to bring in to be honest and we can fake a kyoga Put it in range for a stomping tantrum ice punch the valto It's probably got the z move, but I don't think the z move picks up How does it well it definitely doesn't a minus one for sure so Let's go ice punch into evel tail and go for that fake out into kyogra Because as long as you get the fake out onto the kyoga now It would be in stomping tantrum range Maybe should have z moved it Okay, we're gonna see the evel tail do I mean freeze here would be perfect, wouldn't it?  Wow Pretty bad pretty bad Should we flare blitz it should we flare blitz it? I don't feel like I don't feel like we should really and let's stomping it into the kyoga um And yeah, will you turn out onto the evel tail will get ferrathorn in I don't suppose this will kill the kyoga, but you never know I feel really bad for my opponent right now The rain has lifted which is not great for swamp it because we need the rain We need the rain, although it doesn't really need it so much Because the gengor is still threatened by anyone not it's not going to be able to damage I'll damage us one on one anyway Okay, taking the evel tail out the game though like that. I mean We called it and it happened.  I do feel I do feel bad for them Um, we could do the gracious thing and forfeit. I I guess we could let's just gyro ball into the Gengor and we'll get rid of it before it does thaw out I'm gonna see substitute from the gengor It's still frozen solid, which is a shame because it's probably gone for the z move like it is gone for the z move And I don't suspect it picks up the knockout into swamper, but that's not the point It's putting it in range for a shadow ball for the gengor to pick up the knockout now the rain's gone Which it would be able to do so you've got to think like without that freeze I don't think we we really come back into this match Um, so that it's it's pretty big And it's one of those really really like not ideal Mechanics, isn't it? It's it is really really bad really bad really bad. Um, okay. Let's I mean Leet seed the stacker and we'll go stomping but there's the forfeit So I do apologize to my opponent. I would say a good game, but I'm sure they're not feeling like a good game right now Hopefully we can go on to our next one I think one of the things like I say like not bringing zernius there was a bad call, but I think more of the problem with the team is not having something to actually hit opposing kayogas when we do bring that combination Especially when we don't have pherothon out in the field like if we've got pherothon out in the field It's not so bad, but when we're getting trapped in and maybe that was something we should have probably considered maybe switching pherothon in for Kayoga Um on the turn that we're pressuring the gango It makes a lot more sense to do that rather than leave our kayoga and and just hope I will hopefully we get some like big damage off with with waterspout origin pulse and then banking on You know outspeeding your poison kayoga. It's not the most reliable way to to kind of look at that situation Like looking back at it it would have been a lot better We're like pherothons are not in the worst situation there if it does switch in on what would probably likely be a sludge bomb into that slot And maybe a waterspout at worst, but we're protecting swampert We switch the pherothon in it's going to be able to take that combination of attacks all day long And then we pressure Really heavily the kayoga and then you know the gango is pressured as well So we can react from there and go from there and make sure that we're keeping up that pressure The gango switches out it leaves room for us to switch out our pherothon We know my opponent didn't have there incinero either so it makes life easier for pherothon to kind of operate so There's that angle to look at it from we got particularly lucky there And I will just hop over to a screen so you can see our rating as well She has taken a bit of a tanking, but I've been doing testing I'm gonna say I've been testing stuff so outside of outside outside, which hasn't been gone. Well, it's been gone. All right. It's been fine, hasn't it? But We'll creep back up. No problem. It's taking a little bit longer to find opponent than usual If it does take a little bit longer and we have to search again I will just cut this right now and we'll come right back when we've got an ex-opponent And we've got an ex-opponent of the epithode so asada and we'll hop straight into team preview my friends They are playing a team of requiser incinero, kayoga, pherothon, tapakoko and stack attacker. So we've got the the requiser kayoga combination They're really powerful combination between the two you got the airlock that allows the kayoga a lot of room The airlock is going to be a little bit awkward for us to To get things like swamp earth going because we rely on the rain as long as the airlock is active Then we've not got that rain In the swings of things Obviously the the pherothon as well does give us a lot of issues So we need to be while we're relying heavily on tornados and incinero here to deal with that pherothon So I think both of them are required here Bringing the tornados does obviously cause a few issues Especially with the tapakoko that could come out and that's why swamp earth's like a really nice lead here I think i'm kind of leaning towards swamp earth pherothon as a lead Do we want our own pherothon? It doesn't do too bad, you know, it really doesn't do we want Tornados, I think we need our own kayoga for sure Um, it's whether or not we want zonius and then kind of with the two steels. It's really putting me off a little bit. So Hmm Tornados could be what we need Uh, especially tailwind Put kayoga in a nice position Yeah, we'll go with that. Am I regretting already not bringing pherothon? I feel like probably am but I mean, I said it on monday I feel like the team like one of the issues with the team is it's got like that why I don't know how to explain this well enough because I feel like with four pokemon I'm not quite covering everything So it's the build isn't quite right because I'm always wanting that fifth pokemon to be squeezed in just to get the extra cover there Um, whereas with it like a really cohesive build you can pick your form you think right I'm fine. I can kind of cover everything all angles here or for the best part really good teams That's what they generally do and I don't feel like I've kind of clicked it yet with this team Um, it doesn't quite feel like it's kind of that got that glue to it That you normally have with a kind of polish team, but that's the that's the thing That's what you test, isn't it? Um, we are going to see the kayoga and incinero come out for my opponent um I mean one thing we could potentially do is just mega valve Mega evolve. I mean It could bring in ferrithon here But I don't have it do I I don't have ferrithon. Um, it could bring in kayoga My own kayoga sip swamper for later. I guess it's not a bad idea. Um It's just then we don't have a really decent switch the next turn. Um I'll mega evolve. I'll go for waterfall into the incinero and I'm going to just fake out the opposing kayoga I guess the scary thing here would be a faster incinero Okay Ferro coming in my opponent's book ferra Now a big mission here is to get rid of the um Get rid of the kayoga so we can actually get rid of the ferrithon because without it and without super power We can't really do too much to the ferrithon And we do take a little bit of iron ball damage in the process It does reveal leftovers Um, I don't really want it. I can't lose ferrithon. That's like the one thing I can't I can't afford to lose his ferrithon Um, I'm going to protect swamp hurt And I'm going to bring in tornadoes Hmm This is again like the problem like we've got not really having enough to deal with opposing kyle As we're finding this more and more And it's because we haven't brought our ferrithon We need to bring our ferrithon to these sort of matches because it's really kind of highlighting In these games where the issue is lying that we've not really got the offense Especially with like no thunder on kayoga. I think if we had thunder on kayoga It kind of opens the door a little bit for us to cover that A bit better, but we're going to see just a leech seed from the ferrithon and Now we can get a tail wind up, but I mean We're going to see a power whip into You're like we can get a tail wind up, but I mean I we have to sack incinero to be honest if we're doing this I think And then get swamp hurt kayoga onto the field and then hope that we've got enough of water spout Stomping tantrum to get the ferrithon It's a bit like how we've been dealing with the amoungus, but by doing that It's detracting all of our attention away from the other side of the field or concentrating just down to the ferrithon but I mean We get away with it here with the kayoga protecting. That's pretty huge for us That is massive for us um And a leech seed as well. Okay. That's like Couldn't have asked for anything better Because now we've got the fake out and the hurricane into that kayoga I don't really care about the ferrithon. It can take down our tornadoes now if it wants to Um, I'd suspect it'll probably protect I mean one of the things we could potentially do is go Uh fake out and then hurricane into the ferrithon. I just do think the ferrithon probably does protect here It's just the kayoga is not it has protected the last turn It's just whether or not the extra damage onto the ferrithon is worth it. Um Whereas I think getting the kayoga in in range of like a stomping tantrum and okay, we're gonna see the ferrithon withdrawal. That's fine Like we're getting let off the hook here a lot like over and over and over again We do get the hurricane into the the kayoga. My opponent's doing a nice job of kind of not allowing us to make the most of our Tailwind turns here. So I think this turn will switch in kayoga And we're probably gonna be better off sacking Yeah sacking our tornadoes I'm gonna taunt the kayoga because if I can get a taunt off onto it It kind of stops it from protecting And that makes things a bit easier when we bring in Kayoga swampert Because a water spout and stomping tantrum will get the kayoga now I'd imagine As long as we can get rid of the kayoga it means you got incinero has an easier job against the ferrithon You still got to consider the ray the ray is definitely still a threat Um and the longer it's taking us to break down these pokemon the more damage we're taking making life a lot Easy for when that ray comes in and this is one of the beauty like the great things about this sort of call You know, um, where's you down and where's you down and where's you down? So we'll get the taunt into the ferrithon, which isn't bad. I mean it stops at protecting it stops it Um, yeah, there's the u-turn Hmm And then we've got a hope You've got to hope that a stomping tantrum And a water spout is enough to get the ferrithon because I'd imagine the kayoga comes back in now Kyoga, there we go It's not I just don't I just don't see stomping tantrum And a water spout being enough to get the ferrithon It's not a calc I've done if I'm like completely honest with you. I mean we've got a full power kayoga here Stomping is going to do more Just with the stab that we've got so I've got to go for that The ferrithon can't protect But it can pick up the knockout here if we don't if we don't kill it Kind of want that double power stomping tantrum now. That's That's kind of like the dream right now because then we guarantee the the water spout and stomping tantrum Kale onto the ferrithon Ferrithon going to retreat though. That's interesting because now we take down the incinero with the water spout And we probably are going to be able to pick up the knockout onto the kayoga if it doesn't protect you Oh, no No, no, no we go first. That's not what we wanted. I mean pick up the knockout there. That's a crit So this swamper today, it's like critting freezing it's doing all the rng stuff She'd take this thing to Bristol see an origin pulse It does hit does connect. Okay I think does that tailwind run out? This one put just barely hangs on tailwind pit is out now But the kayoga is at such low health now We can pick up the knockout onto it with an origin pulse or a stomping tantrum But the ray is gonna be lying Waiting to come in And do some mischief. You can tell the ray. Yeah, here he comes Here he comes big bad boy ray And it's whether or not I should have been paying attention. I don't know if we outspeed the opposing kayoga or not Um, but I'm gonna have to try Hmm Just swamper goes down to an extreme speed. That's the only thing I mean one thing we could potentially do here is actually just go for an origin pulse And protect swamper Because I was initially thinking we switch in incinero there, but that gets punished if their kayoga's faster than ours Which it likely is um, and the origin pulse take us down and then we lose a way to at least nerve the requiser And then deal with the ferret on so seeing the requiser it is gonna mega evolve Hopefully it goes for the extreme speed into the swamp. Come on. Please do that. Please do it Leave our kayoga alone Leave the whale Go for the swamp. Come on The toad's more attractive to go for dragon ascent. Yeah, you're going for the right target So nicely play by my opponent picking the right slot identifying the threat Knowing that the swamp puts in um That extreme speed range as well makes it a bit easier for my opponent I mean kayoga takes it. We're not in a best position at all Um, but the door is open now for our incinero to come in And I think what we have to do is protect the old guy. It's really really obvious Why do we switch in do we switch into incinero here? And lose I don't want to lose one but if I'm like completely honest with you Rather make this play and go into to incinero here Let me kind of force the opposing kayoga to come back on the field to protect that ferret on that's the thing And that's where we have to watch out for because then we can maybe attack it into that requiser slot Because it won't reset its intimidate drop for sure Okay, right That's actually big for us. Please we can fake that slot out the next turn if it does decide to turn the field We protect kayoga and leech seed Yeah, go on for the incinero Now we've got a decision to make Do they switch out the requiser into the kayoga? Which I imagine they probably do Do do And if they do that we can't touch the ferrethorn. We just can't We can ice beam it Um Will the u-turn be enough to get the requiser? I heard the kayoga on the switching. That's the big thing She don't think it will be It's just you kind of want the intimidate back onto the field for the requiser. That's it I'm gonna u-turn out onto the requiser slot. I'm gonna expect it to switch out now to kayoga It would make sense that my opponent would do that That means we do lose kayoga but We get the intimidate back on to the field and that's It's kind of important for us against this requiser. Yeah, I'm okay Just about whether or not the u-turn picks up the kayoga. It's such low health as well I can imagine we do we're not intimidated so My best guess would be and I mean the thing is like we could ice beam freeze the ferrethorn ferrethorn protects You're a madman. I don't agree with that at all. I think you've got I think you've got to attack here I think there's no reason not to attack because you've got the rain up You're not worried about the potential um Flair blitz coming in there And we could potentially maneuver our field around so we could It's it's hard though, isn't it because We need swampy in the rain The requiser unless the requiser now the requiser is not banded because it's protected, right? There's a strong winds coming back Okay, kayoga we can protect. Do we want to protect? I mean to be honest we could ice punch an ice beam the requiser They can only attack one target, but they can clear the field, but it's whether or not An ice beam will be enough to take it down and I really don't think it will be um Yeah, I'm gonna I'm just gonna double into it if I can never got time Let's double into it. Sorry cogs are going and I'm just like let's just do it Let's try extreme speed into swamper. Okay Kind of nice beam take it down. I don't know if it will be enough It will be very close It will be very close if we can take it down though That's huge for us because then in scenario can win this game come on Yes, come on. Oh come on critical hit I get excited. I can't get excited about that. I cannot get excited about that Ferrethorn has the hardest time in the world and I can't believe this and yeah, there's the There's the disconnect right there and I mean Can't really blame my opponent for that one. I mean you can I mean no situation should you really ever do that But you can kind of understand why that's them probably picking their DS up and throwing at the wall That's what I would have done in that situation. So big apologies to my opponent It's been a bit of a crazy rng episode today. I mean we've had some bad rng on ourselves previously on the channel I never I don't think we've ever had it as favorable for us So I probably wasted it all and I'm gonna have none in Bristol Typical but guys, I hope you've enjoyed today's episode. It has been a lot of fun I'll be back tomorrow with this team and like I said, we're gonna change things up for Friday based on your suggestions Keep your comments coming. I'd love to hear your thoughts on the rng today It would be great to hear from you and just a big shout out to both my opponents Because I know how it feels and being on a receiving end of that. It's it's never fair and definitely game one. We Got very lucky. I'd like to do the calc on the requiser because I know The ice beam would be doing a lot of damage. It would be very close depending on how it was built Whether or not it picks up the kill or not, but Um, the crit kind of spoilt the whole thing there, but I'm gonna say goodbye guys. Thank you so much for tuning in today I hope you've enjoyed today's episode have a great rest of your day whatever time of day it is and back with more Vgc 2019 ultra series tomorrow. So until then take care of yourselves and bye. Bye