Bitcoin dropped 3% in September and 16% in quarter three. This has been an up and down quarter where we reached a high of $25,000 and a low of $18,000. Inflation didn't slow down at the rate anticipated by the Fed, which caused more rate hikes in July and September. Bitcoin down in September was no surprise because if you look over Bitcoin's history, September is its worst performing month ever. However, we are now entering October and November, which historically is the best performing month for Bitcoin. So where does that leave us? Will Bitcoin get a relief rally and history prove itself again? Or will Bitcoin lose its $18,000 support and drop down to new lows? In today's video, we will look at Bitcoin's historical performance throughout October and November, as well as how it typically performs in the fourth quarter of every year. We will also be taking a look at some of my favorite bottom signal indicators for Bitcoin to see where they are currently compared to previous bear markets. Finally, we will take a look at some charts, analyze them and take a swing at one or two end of your predictions. So let's dive right in to today's video. Remember guys that this content is for educational purposes only and is not financial advice. Always DYOR before risking any of your own money. And as a disclaimer, I've been invested in Bitcoin since 2016. So September was pretty much an up and down month. Overall, we ended in the red, but it wasn't as bad as it might have felt. We went up as high as $22,800 and a low of $18,000. But we opened up the month at $20,000 and closed at $19,411. So only a 3% difference, not too bad overall. Currently we're sitting at this same support that we've been sitting at since June. And we're also in what's called the golden pocket. Now, if you take a look at this chart here, you can see in September, it is literally the worst month for Bitcoin. Seven out of nine years that has been tracked in this chart have been red. And if you add 2022, now eight out of 10 years have been red. So it was definitely expected that September was not going to be a very good month for us. Looking at the quarterly results, quarter three is actually overall not a terrible month. We've had five years here where it's been green, four where it's been red. Adding this year, it's also five where it's been red. So it's basically a 50-50 shot in quarter three for Bitcoin's price. However, now we're heading into quarter four. If you notice here on quarter four, we've had one, two, three, four, five, six years where Bitcoin has ended in the green and only three years where it's ended in the red. If you add that up with entering October and November, which historically are the best performing months for Bitcoin, we start to see the possibility here for some sort of maybe a relief rally or some sort of run back to the upside. Since 2013 in October, only two years did it in in the red. And in November, only three years did it end up in the red. And let's not forget that last year in October, we had a 40% run. The year before that, we had a 28% run up and the year before that, a 10% run up. If we take a look here at the average, the last nine years, it's sitting at around 23.6%. So just for fun, let's say that we went up the average that we usually do in October. That would put us around $24,000. Now in November, the average has been way higher, mainly because of 2013 where we had this 454% rise in November. Now, I don't want to say that we're going to go up basically 60% in November, right? That feels a bit unrealistic, even though in Bitcoin and crypto, it is very realistic. As you saw in 2020, we went up 42.9%. But I want to be conservative with my numbers. So what I'm going to do is take this one out that 453.9% and just do the last eight years, which gives us an average of about 10%. So if we were to make the average move up in October and November, that means that we'd be sitting around $26,000 by the end of November going into December. December has pretty much been a 50-50 month working going either direction. You can see that the average here is about 5.7%. If we add that onto the top, that would put us right around $28,000, which is right around exactly where our resistance line is drawn. Now, you guys might be thinking, but how are we going to get there? What will take us here? There's inflation, there's rate hikes, there's still a war going on, and the market overall just looks terrible. Well, what if rate hikes stopped or at least slowed down a bit? That would most definitely help aid not only the overall markets, but Bitcoin and crypto as well. It would most definitely trigger a rally to the upside. Now, of course, the issue with that is the Fed has said over and over again that they're going to continue to raise interest rates until probably 2024. They're expecting to reach their 2% inflation goal by the end of 2023. However, something interesting happened a couple of days ago where the United Nations warned that continued monetary tightening will only hurt developing countries while failing to cool inflation. They basically said that the Fed will trigger a global recession if they continue to raise interest rates. And the solution to this reverse course. So this is definitely something that we will be looking at. We will be watching because if there's any type of decision to kind of back off or slow down these interest rate hikes, that means that the value of the dollar will begin to probably drop again and everything that's traded against the US dollar will go up in prices, including Bitcoin and cryptocurrencies. Now, looking at the chart, I've highlighted a couple areas of interest here. This green box is basically where that support is. So remember that support is never an exact number. It's a zone. It's an area. This is the zone and area for the support right now for Bitcoin. So that area is between 18,000 up to $20,000. That's its support. That is also exactly where this Fibonacci level is sitting here, which is that 78.6 level. And if we go all the way back to the previous bull market, you can see that is the exact same area where we were rejected. That was the previous all-time high back in 2017 and 18. It was again an area of resistance here when we tested it back in 2020 before we finally broke out and went all the way up to set new all-time highs. And here we are again, except this time we're using it as a support level. So that's why I'm very confident in this support level here. It's already shown us that it's holding here. It's a previous all-time high area. So I'm pretty confident, especially after getting through September, I thought if we lost that area, it would probably be in September. And now that we've gotten past September into quarter four, into its most bullish months, I think that we should be able to hold here and possibly retest this 61.8 Fibonacci area. You can see that this here is also another very important area here where Bitcoin's price has held as a support many, many times over. So it is only natural that it will now probably be a resistance here that's right around that $28,000 to $30,000 area. And remember, if we go back to the average prices in the last nine to eight years in October, November, and December, that puts us at $28,000. Whereas $28,000, it's sitting right at this Fibonacci level. So all the pieces of the puzzle are looking like they fit, which brings me to one of the reasons why that's my possible prediction for the end of year price. It's that we hold here at this support and retest that level up here of $28,000. Now, if for any reason we were to lose this support, which of course can always happen, you can see that the next support here would be down here. That's around $13,000 to $10,000. That's the last time that we had a support here at that level before we broke out. And it was also some previous resistance levels here prior to that breakout above that level. So that would be the next level that I would be targeting if we were, for any reason, break this support that we're currently sitting at. Again, I don't think we're going to break below it, but is it possible? Of course, it's always possible. But as I try to piece this puzzle together, put the story together, make the story make sense, it's showing me that it's going to hold here and possibly retest that next Fibonacci level at that $28,000 area. Now, the last thing I want to take a look at here is these bottom signals. If you guys want to know more about these bottom signals, you can check out this video right here, the top five bottom signals that have never been wrong. So let's see where they're currently at right now. Starting with the R-Hodl ratio, you can see that right now we're in this green area. And in the previous bull runs, you can see that that's kind of where the bottom was for Bitcoin once it got into those green areas. So that is a possible bottom signal there. If we look at the MVRVZ score, you can see kind of the same thing here. The price of Bitcoin is the blue line. You can see that when it's been down in this green zone, that has pretty much called the bottom for Bitcoin's price. And that's exactly where we currently are right now. Looking at the Poel multiple, same thing here. And the green is the bottom signal usually throughout a bear market, and that's currently where we're sitting at. Looking at the Bitcoin rainbow price chart indicator here. You can see that we're in the bottom of the blue area. And if we look here at the blue area, that is a fire sale. So this indicator here is telling you to buy it up as much as you can, as fast as you can. If we look at the pie cycle bottom here, you can see that this signal has also gone off. If we go back, you can see that this signal, the pie cycle bottom, has been called multiple times at the bottom of the bear market. The hash ribbon is another indicator that I like to look at here for a signal. Now this one, you can see that it has not yet signaled a buy like it has previously here. It signaled it here in August of last year before we hit new all-time highs and it signaled it back in December of 2020 before it hit new all-time highs. And you can see on and on and on any time it's signal a buy here, price has almost always gone up. So right now we're in the green. You can see here we had the green before eventually we got the buy signal. You can see the same thing happened here. So it might potentially be setting up to give us that buy signal. When it does, I will definitely be letting you guys know. Now just because these indicators are giving bottom signals does not mean that we're going into a bull run or that we're gonna just start running up to new all-time highs. It takes time. This is a long-term thing. The way the market currently is, it is not showing me that we're going into a bull market yet. So when will be the next bull market? My best prediction is in 2024. The main two things happening in 2024 is we have the next Bitcoin halving. And that's when the Fed has said that they will stop raising interest rates and that we will be at the 2% inflation rate, which is their goal. And they'll start cutting interest rates at that point. That of course would help the markets start soaring again. Mix that in with the Bitcoin halving. It's basically a ticking time bomb. And that's when I think in 2024, 2025, we will see new all-time highs.  Many people believe that you become rich during the bull run, but you actually become rich during the bear market. If you wanna find out my exact strategy on how I'm setting up my portfolio, exactly what I am buying, just watch this next video right here. If you haven't done so yet, make sure to smash that subscribe button, hit the like and drop a comment letting me know what your prediction is for the end of the year on Bitcoin's price. I will choose one winner and send you $100 in Bitcoin. I'll see you guys on the next one. As always, peace and love.


Everybody forced here up in a box of 20 22 select UFC hobby hybrid for John G I'll see a big numbered card here for you John. Thanks for the order Let's go good luck. Got silver concourse Peter Yan. That's some color coming up now concourse disco Holly Holm He read a concourse disco Holly Holm nice 92 of 99 still a couple packs left hubby box the gun side Nice a patty your rookie concourse disco and a premiere-level rookie disco as Daniel Rodriguez Pretty good box here And some more color. Yeah, definitely good box And on the back is nice a concourse blue disco Habib Nurmagomedov 39 of 49 Great color in there. Got the patty as well. Congrats John. We'll get these cards out to you


A dangerous anomaly, SCP 682, is in your area. You must evacuate immediately. SCP 682 takes the form of a giant lizard, which can adapt to any threat. This adaptation means that fighting SCP 682 is impossible, and you must evacuate now. The SCP Foundation will soon deploy assets to the area, which can re-contain SCP 682. This includes Mobile Task Force Tau-5, Samsara, Anomalous Task Force. The collateral damage from this combat will be extensive. It is recommended that you take what personal belongings you can with you. Thank you for watching this emergency message. Secure. Contain. Protect.


So hello everyone, welcome to the Jenkins Infrastructure Public Weekly meeting. We are at the 29th of March 2022. Today we have Mark White, Stefan Merle, Timi Acombe and Hervé Lemer, who just joined and I'm here. Announcements. So we have a weekly release which is not released yet because I'm the culprit. I merged the change this morning without thinking that he started release.ci and of course it wasn't able to start what it stopped. So I've triggered a manual build. I'm going to follow up to see if it fails, but nothing else should be merged so I broke it. So I'm responsible to ensure that it goes to full packaging. And I checked it just minutes ago, Damien, and it's 90 minutes into its two hour process. So I see nothing, it's in the build release phase so about 30 minutes from now it should apply the label or apply the tag, push, etc. So I'm not overly worried about it and if you want we could, given the late hour or the day, just plan that I'll run the release checklist after it's done and dot the i's and cross the t's. Okay, so let's see how it's behave. Another announcement, what's the number of the release I thought it was, 2041, correct? 341, thanks. There is a plugin advisory that should be published in a few minutes if it's not already the case, haven't seen any message, so it's currently running. Yeah, it's actually been published. So the plugin advisory is published, oops, I'm in the wrong location. No problem, advisory, okay. Okay, so directly on Jenkins, you're cool, what is the advisory? Security, so top right, yeah, there we go, advisories. Nice, thanks. Okay, are there other announcements? Let's see, we've got an LTS coming and the new is the Fonso is the release lead, right? I don't know that we need to announce that there but the release candidate, so the 2.332.1 LTS release candidate is available for testing. Okay, available for testing. And I've found no problems in the last week of testing I've been running under or three or four days of testing I've run under. Cool, do we have a timeline or yet or not? We do, it's on the calendar, just a minute, let me know. Okay, I haven't checked the calendar. Well, I should have had it on in mind just a moment, I can read it really quickly. It is the 6th of April, so April 6th. Okay, good to know, so one, two, three, four, five. Okay, so we still have a meeting before that LTS, so that will be the Wednesday after our next meeting, right? Right, correct. Okay, thanks Mark. Okay, for you if we proceed? Yes, actually the next item on the notes list is an announcement that needs discussion, so I'm thoroughly jazzed about this when Tim brings it. Yep, so that is something that Jan and I have been working on over the last few weeks called the design library. It's basically a rewrite of the UI samples plugin to showcase all the UI components and provide guidelines on how they should be used. But it doesn't really fit on Jenkins.io because it's dynamic, it renders the jelly components and everything. So I actually need to run in Jenkins instance. Everything that it needs at the moment is released, well it's getting released in the current weekly, but we'd like a place that we can link people to from documentation from Jenkins.io and play in the meeting list and whatnot just to send it out to people so that they can try it out and see it. The goal eventually hopefully that CI Jenkins.io would do that, but given it requires the latest weekly version that wouldn't be practical. I feel like we'll get a much better uptake and usage if we've got a service that we can send out. So there was two ideas, one which was just a temporary service called designlibrary.jngs.io which is just a Jenkins with nothing else on it really other than the design library. And then there was another one that Mark and Alex had which was to create a weekly.ci.jngs.io which just runs the latest weekly publicly so you can see what it looks like and I don't know whether it would run jobs or just have some example jobs or something, I don't know. But just to show what the current one clearly looks like. Yeah, Tim, I'm impressed, I installed it just this morning and what a nice piece of work that design library is. I think we do want to put weekly, we already have weekly running in one of our CI servers and whether it's design library and we accept it's temporary or we do something a little more permanent. I think I think it's healthy for the organization to consider, let's have something available that is publicly visible, secured offers, it uses the Jenkins LDAP and has weekly installed on it. This instance wouldn't need a lot of resources anyway since it runs only design library. Well, so I might ask for it to have at least one Windows agent and one Linux agent, just so that it could run some set of interesting jobs, but other than that I agree it's very light. And maybe it doesn't even need those, it just for me if it's got access to a Windows agent even if it's purely ephemeral. Tim, am I maybe I'm wrong there because if it were just design library, the design library certainly doesn't require agents does it at all. No, no, it doesn't. But if you want to have some jobs and weekly just as examples of some different types of jobs would be fine. I mean, that starts with you, which is, sorry, that's a nice idea. Since we already have infrasci that will be a public available instance hosted on Kubernetes with ephemeral agents either Cuban and or AWS machine as for now. Does it sounds good for you because that will be almost the same configuration of infrasci, except we install it on the public cluster instead of private. Yeah, I don't see any blockers on that. It's more for the naming weekly design library. Yeah, Stefan are they are you more prone to temporary instance only for the design library feature and then we dump it or to have something a bit more permanent that will be the weekly or preview or something. I think a permanent more permanent one would be way better because that's that will show how it's evaluating. Yeah, but that's almost nothing. No, it's just one VM. Yeah, we have two decadent for the CPU at least. So not a virtual machine. That won't be a virtual machine for sure. It just run on Kubernetes with many resources at all. 500 makes a memory and half CPU or something. One CPU to gigabyte if you go under that might be tricky because because of the sidecar and the way plugins are loaded. Going under is the cost difference won't be that much. The cost will come from the agents mostly. Yeah, and, and if we don't put much work on it right now it's purpose. It's initial purpose is just is just to be the host for design library right and then if we decide oh we want a sample job or two or three. Okay, we put some lightweight job on it. I'm thinking, what do you think about a preview that CI the Jenkins that you so it's not strictly tied to days and library or weekly, it could be used for release candidates of LTS as well in the future or whatever usage, but that may be too much. Yeah, I thought about that for release candidates release candidates track LTS line. Going backwards in time if we tried it to. Yeah, correct. So weekly or design library. And my mind, I've thought about preview and, and wondered people when they see that it's running weekly may may may misperceive that weekly is a preview because weekly is not a preview weekly is ready to use. It just happens to be released every week. Yeah, I'm sorry Mark but for me weekly is a G or preview. I'm sorry I cannot say weekly stable that as a user. We have it we update it every weekend. I can. It's not weekly work. Large production system. You like to leave them shortly. Investor. Okay, but yeah, I'm inclined. I vote for weekly as well. So it seems like four to one. That can be always changed that's not that much it's a configuration under DNS the rest is only configuration on him. So we can start tracking it as soon as it's opened. And as soon as we have the desk issue we jump on it. You've got it. You've got an issue. I've got more than one issue trust me. So jump on it it's open. Okay, so that's as soon as possible. And then team you can either work with us to add it. But yeah, the first the most is here we can take it you can start it that will be installing a new release on the public case. Yeah it depends on how long retail someone could pick it up. I probably won't touch it in the next couple of days but I can do it later on if it's if someone doesn't get a chance. Yeah, let's go that way. So for everyone, the first person that has free time and wants to work on that must absolutely think about allocating the issue to themselves so the other know someone started to work on it. And eventually commented just to be sure so we can work asynchronously sounds good for you. That sounds good. Okay. Are there any other questions that need to be discussed on that topic. Cool. Let's go. Thanks for the work team. The library is impressive. Okay, so what did we do this week. So we have a lot of long running tasks. So we only close the one. One task there has been a few in the desk close so thanks for everyone will closing these issues on on the fly. So every solved some issue with the account application and team. Thanks for helping there. So, so it looks like that that account application wasn't able to connect to the LDAP different error. So, I'm sorry, but this, the solution is to delete the pods. It is restarting the application that was very well. If anyone is able to be to compile the application on the machine, they are they are totally free and they can try fixing the issues. But honestly services just I tried to I tried to just do some minimal patching on it. It doesn't build on my machine. Like, it's using ancient greater with some ancient jelly plug in which doesn't exist anymore. I mean, it's using jelly as well. Who is using Julie today? Yeah, the bigger problem is the the jetty plug in that it uses and built into gradle. And so to get it working you need to pull it to an embedded jetty container and just rewrite the whole bunch of stuff. And I spent 15 minutes alone and then set screw this way I'm using a better solution. So yeah, so that's why I would restarting better to so as a reminder, we will want to have key clock or the tool that gave in pointed to us. But we need a tool to be able to manage the account on the LDAP both tools are our looks like okay. But in order to have these tools installed and used definitively, we need the migration to the private cluster to be done first. That's a strong requirement in terms of networks. So that's why we need to restart as a temporary measure for now. Looks good. So the current work we have rating the Jenkins IO migration to Azure. I'm taking on the order on the milestone right. So Stefan worked on that topic is driving the topic. So we were able to add a manage PostgreSQL database. Thanks team for the insight about the flexible instances. We weren't aware on that. So we now have a full terraform manager Azure with management of network and everything. So going in the correct direction. Now the next step Stefan is currently working on that since known today, installing the chart for ratings Jenkins CI that Jeremy play out and gave in worked on, which is a read available on our chart. So now we have to install it and why you're everything together. Once that part will have been done, we'll have to import the data from the old database and then switch to DNS. Is there any question on that topic? Okay. So that topic is a work in progress. So I'm migrating it to next week milestone. Yep. Okay. Next one apply to docker open source program, which is closely related to the current credential for VM agents. So last week we had rate limits. We need to ask the docker open source program if they can extend their current sponsoring they are doing for us on the Jenkins docker account. If we can extend it to one or two technical accounts that we could use in the infrastructure. The main idea is we would want to be able to use to increase the rate limit of a single account and ideally have an account that is only used for pulling images. So we can safely share even with read only token we could safely share this credential and not being burned by the API rate limit. So that task is on me. I have to contact them based on the information that Olivier gave us in the past few days. Which is one. Okay. On the area of the docker rate limits. So there is also pipeline library pull requests by Stefan under they that try to maps to credentials per Jenkins instance that we host one for pool and one for push. So we are currently creating the accounts creating the API token on each account so the password cannot be used and we can recycle the token we have to level of credential then a some already exists. And that library will keep using by the whole syntax that we currently use will keep using the push credential to not break the release capability. That library has been posed because of the weekly release and the security advisory of today. So we should continue working on that on the coming days. It doesn't include the modular yet the idea of for a given build on CIG and can say you spreading randomly between two three or more accounts. That's the first step now to be able to see how we could cover the cases and if the API rate limit come again we can start spreading many on CIG and can say. Any question on that topic. No. Okay. So that one, that one has to migrate email alias for the press. So for for this one we haven't heard from KK. I'll make the migration from my story if you want to continue. Oh, cool. Thanks a lot. So for the email alias for press we haven't heard back from KK Mark. Do you mind to contacting KK directly usually tend to response to you. Sure, I'll ask. Yeah. Otherwise, as we said last week, we are going to contact directly mail gun to see what is the procedure if they're still have an account or worst case if they can just give us the emails. I'm not sure how that would happen. But I don't think there's any in use. We don't, we don't. So what would these be useful. The question is what are the existing email in something at Jenkins IO that already exists weren't able to extract them from the GitHub history. And Tyler and Olivier weren't able to tell us which ones. So Tyler say we're any. That I don't know. There is the mix. The thing is that if we move the mix that will be the worst case we move it to whatever email system sounds like the next foundation as per the ticket. But yeah, we need to be sure that we need to have a catch them all then. So yeah, let's let's ask KK at least to be able to reach mail gun and see the list of email and then move away. You ask him but I doubt there's anything in use these days. I've seen grids being used for election campaigns before, but no, I'm not aware of mail gun at all in years. Yeah. And if Tyler isn't aware of the mail gun. That means it's really, really hard. And no one's sending emails to change the style so unless it's something for KK himself. I don't think it's a thing, but double check with him, but I wouldn't worry too much. I think it's perfectly okay if we set ourselves a time out if we don't get an answer in a week or two we just proceed. The risk seems very low. So is it okay last week we say this week has time out for contacting mail gun. But I propose we extend one week just to be sure if direct communication just that to be sure that we can close safely. Was case we go. Sounds good for you. Yes. Next topic. GCAWS on our image. So that one was a minor one. I don't think you had time for that, Stephen. I'm sorry. Don't be sorry. We don't have time. We don't have time. There were more important topics. Do you think you will be able to walk on it next week or do you think that might be too much given we have a rating and pipeline library. We'll be able but I'd like to because it's nice. Okay. Just don't don't over commit on. I'd like to. I will do my best. I don't. I'm sure you will. You already. Define credential at folder jobs level instead of Jenkins instance. So the goal is to have a way to use in France code to avoid having credential on top level of Jenkins instance. So current status. I'm able using my custom homemade Helm template. I'm able to convert a set of YAML definition into something that's generate valid job DSL with credential at folder or multi branch level. And it sounds like that if you create a config map on a Jenkins and chart deployment with the correct annotation, the system that search for the config maps dynamically, if you use the correct annotation will get it. So I was successfully. I just did it successfully. One hour ago. So I'm pretty confident that for our infrasci and release CI, we should be able to have a custom made and charts that use the official Jenkins and chart and apply the configuration directly for now. Because my template is not perfect, it doesn't cover GitHub organization scanning and some kind of plugins. Right now I propose that we start with this one. And after a few weeks of usage, we can start opening the topic for contribution on the official Jenkins and chart. Given that it involves job DSL and there were some job DSL dead pull request or routing pull requests since one year that I mentioned on the issue. Thanks team for adding at least a label and pushing back on that I will contact the maintainer. Because some of the credential needs to do DSL to manipulate the XML configuration. So that's a bit of a trash fire and it sounds like I understand that we need to update some things on some plugin to be able to provide an easy syntax for that. So let's start this one because it's blocking towards our requests. So right now I'm focusing a lot on that I should be successful tomorrow. So as if it's okay for everyone, I plan to do the first deployment on infrastructure during the day tomorrow, unless there is an important task to run on infrastructure. I'll send a message on IRC but that means that all the jobs will be failing because I will totally destroy infrastructure in the process. I cannot guarantee continuity on that service until it's fully done. So yeah, that will slow down our ability to deploy Terraform, Docker images. So that's why I prefer asking if there is something important to deliver tomorrow for you. Nothing that I think of. Yeah, nothing that I'm aware of. Okay. Okay. Now in fracost. So every, do you want to explain it or? Yeah, I can. Yeah. So can you open the issue? So get the infreMD on my screen too. So I'm trying to implement a fracost, which is a tool to report estimated cost when there are changes in Terraform repository. For now, it can estimate Azure AWS and Google Cloud. So they have a main method of estimating the cost from the Terraform plan. So we decide to implement this method only on Azure since AWS has sensitive secrets like SOFs or others. And joining their Slack community, I've noticed that we can also use an experimental feature, allowing us to estimate cost from the HCL file directly. So no access to the plan and no access to any secret or sensitive value. I've implemented it on AWS and I also want to add it on Azure too. So we can compare the discrepancy between the two methods. Seeing fracost engineer tell me that they weren't sure the result would be exactly the same. So it's experimental for now. But yeah, my pull request has been merged and we have to see on the next Azure on AWS pull request to see the result and the reports. The fracost is a SAS but can also be self-hosted if we want or need. And their documentation have example for a lot of CI-CD and their Jenkins example repository doesn't have any real example. So we will be able to propose them our integration as example later. Thanks very much. I just realized that we might have inverted AWS and Azure because we don't have any Terraform sensitive outputs on the AWS Terraform project. While since this morning we have on the Azure project, we have the output that exports the database. So the sensitive output are stored inside the plan. That means we cannot be totally sure that this data could not be exfiltrated to their SAS. So that's why we say maybe on some ends the HCL change. So we might have to change the pipeline library, but the impact is not that much because it's only the database for a rating that we just mentioned earlier. So the impact is really slow. That's why we selected Azure initially. Especially because it's empty right now. Exactly. And we will rotate the credential before going to production. And their Jenkins example. But thanks, that's really nice in fracost. So let's continue working on that. Let's see the first results. We might have some incoming Azure. Next topic unless there is a question. Cool. You also worked on Git setting colon pass on the Windows machines. So the status, you solved the issue in short term. Were you able to confirm with the people who opened the issue? Okay, but since James has approved your pipeline library fix last week, I assume that it should be okay. Could you just check in privates on the CloudBees channels? Because remember, there were only two person from CloudBees. So on the virtual machines agent we already have and there is a pull request on the containers. So the thing is that we discussed. So unless I miss something, I reckon you confirm. Now we have a task, a long running task that will be building our own Windows Docker images for the infrastructure for CIG and Kinsai instead of relying on the community images. So we will build on top of the community image and we will add our own settings because sometimes we want some settings like the Linux image currently, same for Windows. We will want to have some specific settings on our images that would impact the image if we contribute. So and we need to be able to build Windows Docker container on infrasci. Stefan did all the easy work about providing Windows machines with Docker. We have the agents that run on EC2 fmroll agents. So, Herve, if you're okay to take that task, you can start building the two GDK8 and 11 Docker images, but on our own repository. Yes. Is there any other question on that topic? On the long term, I want to propose an update manifest in Jenkins key repository for this image. So they can be kept up to date more frequently. That would be a huge help. I didn't understood the team, the reverse of the release number in the pipeline. I've asked you in a commit. I don't remember. I don't know if you remember it. Let me try to find the link. The 328.9 that I put there, right? Oh, it's on Docker inbound agent on Jenkins CI. I've put it in zero chat. So that one is Docker inbound agent builds on top of Docker agent. So it uses a release version of Docker agent. So if you go to the Docker agent release and GitHub Damian. Currently. No, no, not this one. Docker agent, not Docker inbound agent. So you'll see it's got 411, 413-1, but if you see the one below it's 4112-5. So that number there is if we ever need to build against a newer version of Docker agent from Docker inbound agent. That's version needs to be bumped. It's normally one, but occasionally we build against a newer version. Oh, the left the left hand side is remoting. And the right hand side is the image version. Yeah, so it's the last digit we've considered. Yeah. And it's going from 421. Okay. There's two components to the version number. One is the motion version. And two is the build version kind of. Okay, that's okay. It's like the package increase number when you read the package. When you type the version scheme to the application. Okay. Yeah, it's kind of manually managed because the kind of unrelated images. It can be managed by update CLI, but apart from that. Yeah. Okay. Another thing is that we are dealing with Windows container. And docker bake and docker buildings aren't able to use docker bake. And this is when I looked at how it was done. I saw there were two way of doing the image one from Linux with the docker and the other with completely different scripts. So, yeah. Yeah. I suspect the Windows ones don't. I'm getting bumped. Yeah, that's why I wanted to make a pair for this, but then I. It's probably harder to one. That will be so the updates CLI manifest there will be a nice contribution to keep all the images up to date at the same time. Yeah, just create like a property to file the route or something that both windows and Linux can read. Update CLI also manage. If you have two files, one for Windows and one for Linux that are different. It doesn't care. It can update both from the same source. So, sure. Okay. That's a good point. I assume the scale way cluster should be delayed. Yeah. We have to contact the scale way to ask them. Yes, exactly. An account. So. And we have the monitor build on our private instance. So that's something that came from Daniel. That's an idea of to be sure that we monitor on trusted CI when some of the most important builds are failing. So we already have something like this for the date center. We have the data dog monitor that check the last build time of the season generated by the date center. And if it's if it's more than one hour or two or I don't remember, then it will start sending alerts and that a certain threshold will start page page UTS. So that will be the same idea having an external regular process they will check a season file somewhere. Daniel said, okay, we should have a crown job on that instance will be the same for really see I though that will export a season file with only a strict subset of information. Why not using it object or notification because trusted should be a private instance that should not exfiltrate any data as much as possible. That's the reason so Daniel say that should be quite easy to implement since we're really doing it. If we can't we can still ask him to help us as had had it been considered another approach possibly just exporting the RSS somehow copy the RSS feed from from an inside the VPN to another location we could then monitor with an RSS reader. I do that with ci.jenkins.io and I admit I don't I don't think anything is being exfiltrated from the RSS feed. Right, as far as I know there's nothing sensitive in those except the existence of the job and whether past or failed. That could be a nice one. And the only one that report is an external system that monitor right, we have to have some, some web server that well, I'll reply to this one because I thanks for highlighting it. I think it's worth a reply to have a conversation with Daniel he may know a reason why RSS is a bad choice. Yep. Would you be able to to help us on that part Mark because I don't feel at ease with the RSS feed on Jenkins. Yes, yeah, at least I can I can talk about how I use it and and why that that has helped me and then, then we can decide is that is that an interesting technique or not. And if it is then if you are able to share what you did then we can take over that time sounds good for you. Okay, yes. Sign it to you and change the milestone then. And we will change a Sydney as soon as we have more answers. Thanks Mark. I think we have. So scale where I'm removing the milestone. Can close this week. Yeah, this week milestone. There were two other topics. The first one from our chair here. So, they bumped us about if we're able to evaluate the security requirements. We haven't had that time but yeah. I understand they won't have any bandwidth until the 14th. So, so we probably oh Tim and explanation this is one Tim that I launched an exercise didn't invite you to the invitation on on a session our chair is a company that does an AI based open as optimization of cloud resources, and they offered a, a free and hey we'll support your open source project effort to the Jenkins project that we started a conversation with them. I'm sorry that this is a new one for you I'm sure but what it was was a, an exercise is there a way to get somebody who could help, help us with finding cheaper ways to do what we're doing on Jenkins.io and they've got some techniques that they were interested in and the permissions they were requesting looked pretty simple and safe but we don't, we don't want to do anything with it until the security teams told us yes that's simple enough and safe enough. So, don't say the words too loud because my YouTube ads got stuck with infracost for cloud and Kubernetes for weeks and I got very annoying watching my YouTube videos constantly getting the same infracost case study bled at me all the time. Oh, sorry okay so. All right, I will, I will try to not use that word too frequently lest it suddenly get kicked in thanks. So, my proposal is that we start sending requirements to the security officer around the 13 14th, not because of arteria date but because I know that vadek is more than busy until the 12 included. Right. So, yeah, that makes that makes sense. Damian, I think you might have to take a slot on their availability. Yep. And if it's okay I will take care of synchronizing with vadek on that and sending them. Unless someone want to. Okay. One, two. Okay, go. Every on digital ocean. So it sounds like that we have for used half of the credits. Yeah. We currently consume about 1000 per month so we might need to contact them to see if they are okay to sponsoring us. Because we must absolutely prioritize writing a blog post and adding the logo on our website before asking them for donation. Actually that's a great, great excuse. And so I thought we had their logo already but if not that's an easy one. But so logo on the website because we it's a this is a great story to tell. Yeah, okay. So who is going to, to share the burden to write down a blog post. I can try but I'd like some help. How about how about Mark and their date together. Yeah. Thanks. I wasn't, I wasn't ready yet. We could ask Tim, but he's pretending that to hear. No, Tim, this is this, this is just your being to ignore that that was not that was a completely unfair shot. Yes, the city print. I heard. I heard that we were volunteering. Stephanie to. That's good Stephanie in French is the female name so it's okay not me. All right. We'll find a Stephanie for you. Thank you. Hello folks I think we have reached the list of topics we have other topics additionally just in case important things to know unavailability. No. Okay, so I hope everyone will continue to take care of themselves and that we can continue to take care of the infrastructure. Have a nice day. Have a nice week and see you next week. All right.


Remember a hallmark card when you carry enough to send the very best. Shakers of hallmark cards bring you an unusual true story. On the Hallmark Hall of Pain. Here's our distinguished host, Mr. Lionel Barrymore. Welcome to the Hallmark Hall of Pain. Tonight we pay tribute to a man whose name has been all but forgotten in the annals of American history and yet had it not been for a frontier missionary doctor named Marcus Whitman, the Oregon Territory might never have become a part of these United States. And so we bring you another true story about real people on the Hallmark Hall of Pain. Now here's Frank Goss from the Makers of Hallmark Cards. When you want to send a card to someone who is dear to you, here's a simple rule to follow. Look for the hallmark and crown on the back of each greeting you choose. Through the years this famous symbol has stood for quality at its best. Quality and craftsmanship in design, in words that say what you want to say, just the way you want to say it. And you can be sure of it, hallmark cards will tell your friends instantly. You'll carry enough to send the very best. Lionel Barrymore appears by arrangement with Metro Golden Mayor soon to release Dory Sherry's production Take the High Ground, starring Richard Whitmark, Carl Mulden, and Elaine Stewart. And now Mr. Barrymore brings you tonight's exciting story on the Hallmark Hall of Pain. Whitman, frontier doctor. The years 1836, the place the juncture of the Walla Walla and the Columbia Rivers, deep in the heart of the Northwestern wilderness. Him in Hogan, Macmedicine. Will you tell him to come out here? No, tell while he Macmedicine. Look here, Indian. You know me. Everybody know you Hudson Bay Company, man. You MacDonald. That's right, I'm MacDonald. And when I tell an Indian to do something, he does it. Now get in there and tell Whitman I want to see him. Quiet out there. Stop that infernal racket. Whitman. Might have known. Have a born depict with you, Whitman. Let's move away from the Hogan, MacDonald. There's a sick woman in there. I'll put it straight, man. We didn't mind you and those other missionaries coming into the territory from the States. That part of it was all right. We'd like to have a few settlers in these parts. And we didn't even mind your nonsense with teaching hymns to the Indians and tending to the railmen. I'm sure that's very Christian of you, MacDonald. But we do mind when you give them heathen savages, corn, and teach them how to grow it. That, my good doctor, is going too far and you'll not be doing it any more. I don't think I understand. No. I'll show you what I mean. Indian. What do you want? It's October, Indian. For a time. How many furs you've got to trade with a Hudson Bay company? No gut fur. No trap this year. No more trap. You hear that, Whitman? Why no more trap? Got hogan? Got cornfield? Fish and river? No more live like gypsy. Gypsy? Where have you learned gypsy what? Whitman's squad, teach me no word. Teach me read and write and pray to Lord our savior. You hear that, Whitman? I hear. And now if you'll pardon me, I'll get back to my horse. I've got two more sick calls to make before dark. I'm warning you, Whitman. We want you out of the territory. You and the rest of your friends. You're ruining the Indians, Whitman. You and your civilizing and that's bad for business. Mr. McDonald. What? Business be blasted, Mr. McDonald. I wish you wouldn't worry about it, dear. The snows are starting now and they can't possibly do anything about us until after the spring fall. My dear Narcissa, I may be a missionary, but I am not a man who leaves things to Providence. But, Marcus, what can you possibly do? One man against a tremendous company in a wilderness without laws or courts or redress of any kind. If I don't do something, no one will. Wait until spring, dear. I'm sure things will work out. I don't think you understand the situation fully, Narcissa. By spring, Oregon may be incorporated into Canada. Should that happen, the company would have a free hand with us. Oh, you mean the border thing? Yes, the border thing. The United States and Canada have established their border from the Atlantic Ocean to the Rocky Mountains. Beyond that, they're still in the discussion stage. But surely the United States will claim Oregon? After all, the only settlers here are Americans. No, no, the way things stand, they won't. They know nothing of this land back in Washington. I don't think there's one man in the entire District of Columbia who has ever even seen the Oregon Territory. But surely they've heard of it. Yes, yes, they've heard of it. Listen to what the learned statesman Daniel Webster has to say about Oregon. He says, Oregon is a vast, worthless area, a region of savages, wild beasts, deserts of shifting sands, cactus and prairie dogs. Moreover, what can we ever hope to do with a coast of 3,000 miles? 3,000 miles, gentlemen, rock bound, cheerless and not one harbor on it. Gentlemen, I ask you, what use have we for such a country? What use have we for such a country? I really don't see how he can say that. There are no deserts in Oregon, and that's for cactus. The point is that he is saying it, and they are believing it. And by spring they'll have thrown this great beautiful territory away, thrown it to Canada for the exclusive benefit of the private traders. And so, gentlemen, there you have it. Dr. Whitman, your generous offer to make the necessary journey to Washington is, of course, welcomed by us all. But I should like to point out that you can't cross the Rockies until late spring, and by then Congress will have passed their acts and stand adjourned. I plan to leave tomorrow morning. But Dr. Whitman. Tomorrow morning, Dr. Fortice. No man has ever crossed the country in winter. Why, in the mountains of snow is drifted 20 or 30 feet deep. The temperature is many degrees below zero, and there are savages, wolves, bears, rivers to cross, and blizzards. Dr.... Marcus, my friend, do not make this journey. It... No matter how you may be devoted to the Oregon Territory and your work in it, you'll be going down into the valley of death to attempt this thing. Marcus Whitman. Doctor of Medicine, man of God, and American. In later years, Horace Greeley wrote of him... Marcus Whitman once seen was a man not to be forgotten.  He carried himself awkwardly. He seemed built as a man for whom more stock had been furnished than was used systematically and gracefully. He was not quick in motion or speech, and there was no trace of the fanatic in a man, but he was a profound enthusiast. This, then, was the man who set off in October to span the continent in the dead of winter. The feat never before accomplished, and Marcus Whitman was doing this not for gold or for fame, but for the love of the land and the way of life. The Hallmark Hall of Fame. Another day, I picked up an old book from my library shelf and discovered this passage written on the flyleaf. He alone has lost the art to live who cannot win new friends. It seems it was written by a half-forgotten American author named Silas Mitchell almost a century ago. And yet the truth of these words is evident and timeless. For one of the great joys of day-by-day living and of traveling, too, is the joy of meeting people we like and keeping in touch with them through the years. Now, even though most of us can't visit our friends as often as we want to, there's one wonderful way to let them know they are in our thoughts. I mean by sending Hallmark cards on holidays or birthdays or whenever you want to say hello there, how are you today? At a fine store where Hallmark cards are sold, you will find special greetings for every occasion and for every friend, old or new. It takes so little time to select and address an appropriate Hallmark card. And you can be sure each one you mail will be received with joy and remembered long after. Just look for the Hallmark and crown on the back of the card you choose. It's the famous symbol that tells your friends you'll carry enough to send the very best. And now Lionel Barrymore brings you the second act of our true story of Marcus Whitman. He took with him one man. General A's a love joy. A reliable friend and an experienced traveler. He also took his dog and two extra pack horses. They left the mission on the 15th of October 1836. Struck to the east moving as fast as was humanly possible. They were racing the weather, racing for time and for their very lives. And Samoritans! Samoritans! Fifty miles in only eleven days. If you could recommend a guide, we'd be much obliged. Somebody hanging around. I think I ought to warn you, General. That's come in yesterday from east to here. They said the snow was already twenty feet deep from some of the canyons and drifting a whole lot deeper. We must go through. Dr. Whitman had an idea which we discussed on our way here. He thought of a new route to the states going by way of Ewingham and from there striking south between the ranges leaving the Great Salt Lake to our right and heading for Santa Fe. Say Santa Fe? That's right. Santa Fe, eh? Never heard nobody doing it though. Yes, but could it be done? How about it, Pedro? Well, I don't know. Could try. Will you guide us? Sure. But I want a lot of money. It's a long trip, I might not come back. It's dangerous. Yes, yes, we know that. But how much do you want? My feet, they hurt me when it snows. Lots of snow between here and Santa Fe. Please, Mr. Pedro, cuánto, cuánto. A thousand some miles soon. I want, uh, $15. I've met very severe weather. Incidentally, in winter, as you may have guessed, there's now the state of Utah. They passed the Great Salt Lake and turned south. General Lovejoy kept the journey in this part of the journey. On a trail toward Grand River we encountered a terrible snow storm that held us to seek shelter in a deep, dark canyon. Here were we entrapped for ten days. On endeavoring to leave, we met with winds of such celerity that the animals became blinded. Maddened. Our guide stopped us. What is it, Pedro? Where are we? I don't know. I never see this place before. Are we lost? I don't know, General. I think maybe we are. But we must keep on. Stay here all winter. And you're...  Uh, in a manner of speaking. I'm a Protestant clergyman. Well, then I think maybe you better say a little prayer for us. You'll never forget the sight. Dr. Whitman Neltoness known prayer. It was bitter cold. I am not a very religious man and I don't hold much faith in miracles, but as Marcus Whitman prayed, a very strange thing happened. One of the back animals turned and started their way from its companions. Hey, hey, come back here! Pedro, where is he going? Dr. Whitman. Dr. Whitman. What is it, Pedro? The mule. The mule. He knows our way out of here. What do we do? We follow him. Doctor, you... You make a pretty good prayer, huh? I think maybe you better teach me that prayer in case I ever get lost without you. Our forced camp had exhausted our supplies. Pushing ever southward through desolate canyons and deepening grits, we subsisted on bitter roots and bark, pine needles. Game there was none. Saved the wolves who followed our trail. We slaughtered one of the pack animals and ate it. The following week, near crazed with hunger, the guide and I secretly killed Dr. Whitman's faithful dog. It was a deed for which I shall ever be ashamed. We ate him secretly. And if the doctor suspected what we did, he never said a word. He endured his privations with great fortitude. He was a man with but a single gore, which he expressed immediately upon our arrival in Santa Fe. Have they had any news from Washington? Harry Clark says they've heard nothing for 12 weeks. From Santa Fe, they struck east toward Bentzfork in what is now known as Colorado. A cheerless, dreary plains journey. Day after day, they were trailed by great packs of silent grave wolves. Four days' journey out of Bentzfork, they met a mule train bound for a puzzle. They say there is a company of 50 packers leaving day after tomorrow for St. Louis from the fort. Wouldn't be another trip until spring. Day after tomorrow. Horses can make it. Take four days. We can do it any faster. We've got to travel with that train. Listen, Pedro, general, my horse is still good. I'll go it alone and have them wait for you. Marcus, you can't do it. You don't know the country. And those wolves, señor, they like to get you alone. Never mind that. Just you tell me the way. I had myself rode into Fort Bentzfork. The pack train had not yet departed. Dr. Whitman may have seen nothing. The man had never arrived at his destination. I spoke to Colonel Benton. He sent out his best scouts in the search. Myself, the guide, one of the scouts, followed the banks of the Arkansas River for 100 miles, knowing that if Whitman were alive, he would make for the river. Every night, our camp would be surrounded by hungry... When Marcus Whitman, he was lost in the mountains. And when they brought him in, although he was very weak in his fever, he insisted on joining the packer's train. And he traveled with him to St. Louis. And what about the treaty, sir? Has it been signed? You mean the treaty with Canada? Yes. Oh, been signed for months. Heck, doctor, they signed that treaty just about the time he was leaving Oregon. It can't be. It is, though. Seems pretty. Hadn't come all the way to St. Louis. Just find that out. But tell me, did they extend the border all the way? Does it reach the Pacific? Nope. The part they signed about runs only as far west as the Rockies. They'll get around and straighten up the rest of it next week. Hear that, General? Saddle up, man. We're going on to Washington. And risks me very much, doctor, but frankly, I don't see what I can do. Mr. Webster, there's one thing you can do for me.   But politics are not your function, and, moreover, I would advise you not to dabble. It happens that we have a strong ulterior purpose in the disposition of Oregon. And what is that? Off the record. We intend trading it to England in exchange for the banks of Labrador.  In Moscow. Quite so. See, I'm wasting your time and my own, Mr. Webster. I bid you good day, sir. A relatively small-owned population, and if a private citizen had the determination, he could take his problems to the White House. That's what Marcus Whitman did. It was a curious meeting. The President of the United States and the Reverend Dr. Marcus Whitman of the Oregon Territory. Dr. Whitman, how do you do, sir? I've heard of you from Secretary Webster. I have no doubt of that, Mr. President. And in view of his report, I'm rather surprised that you're granting me this audience. Not at all. Not at all. You know the President's in a funny spot. He has to keep in touch with the people, even those who are out of the country, and not in a position to vote for him. Well, incorporate us in the United States, and I'll personally promise you the vote of every missionary in Oregon. All 14 of us. Is, sir, the President's in a funny spot? Yeah. I like Daniel Webster.  But that speech he made about Oregon. You know where he got his information? No, sir. Got it from a man whose brother is owner of a large fur trading company. I know. Because the man told me the same thing. Lately, I've heard different though. I hear Oregon is something more than a desert. Desert? Well, there's no desert in the whole territory. There's no sand, excepting that which sparkles on the Pacific Ocean. Oregon is fertile, sir, fertile, and just begging for pioneer Americans to come and turn her soil. That may well be, sir. But what could be mispronouncements on the Oregon Territory? Public sentiment is pretty much against the place. I can't help you personally, but I can send you to a man who can. Well, I'd appreciate it, Mr. President. Yes, sir. I think you better go up to New York and see the editor of the New York Tribune. He'll help you. Names? Horace Greeley. Thank you, Mr. President. Whitman, this nation can never repay you for your brave effort to save the Oregon Territory for the United States.  I personally am going to take your story to the people of this country. Thank you, Mr. Greeley. Labradora. The moon took public opinion, formed it into a club, and dealt the skeptics a blow which they never forgot. And when the United States and Canada established their border for all time, the Oregon Territory became a part of America. And those magnificent, wonderfully beautiful states, they were the women of the day. Thanks to the will and courage and determination of the man of medicine, the man of God, and the man of the American people, Marcus Whitman. Old woman we're honoring next week on the Hallmark Hall of Fame. She was a woman of amazing courage who defied all opposition and marched right into American history. But first, Frank Goss wants to tell you about a smart little lady of six years. This morning I had a phone call from my little niece who celebrated her sixth birthday yesterday. I asked her to tell me all about her birthday party, and she said, well, the gains were nice and the cake was nice, but the presents were best of all. You know, Uncle Frank, some of them were as pretty on the outside as they were on the inside. Well, I couldn't help thinking just how important gift wrappings really are to little folks and to grown-ups too. Obviously, the papers and ribbons you use on a gift box are the first things to greet the eye, and they can show your care and thoughtfulness as surely as the gift you choose. That's why I think you'll enjoy selecting all your gift wrap items at a fine store where Hallmark cards are sold. You'll find that Hallmark gift wraps beautifully designed and crafted in colors as fresh as a rainbow. There are small prints for tiny boxes, big dramatic prints for the largest gifts of all, and styles for many different occasions. So next time you want to make a special gift, a thing of beauty to receive, look for the wrappings with the Hallmark and crown on the label. It's the symbol you like on your greeting cards when you carry enough to send the very best. And now here again is Lionel Barrymore. Frank, you're certainly right about the excitement on the youngster's face when he reaches out for a gift all wrapped up in pretty paper. And as the youngster grows up, you'll find that these added signs of thoughtfulness help make our daily lives a whole lot presenter and happier. Yes, knowing how to give graciously is more important than the contents or the price of the gift. Well, Frank, I thought today's story was an adventure and a colorful tale, didn't you? Yes. It made doubly exciting because it actually happened. Now, next week we have another true story of outstanding personal bravery. This time we're honoring a woman, Mary Ann Piccadike. I guarantee you will remember her story for a good and long time. Yes, next week the Hallmark Hall of Fame honors Mary Ann Piccadike, a woman of the ladies' aid in Galesburg, Illinois who set off with a trainload of supplies for our Civil War troops. She took one look at the suffering of the soldiers and remained as the first woman in the front lines. Amazing generals with their unflinching courage, energy, and boundless compassion. I hope you all be with us next week on the Hallmark Hall of Fame. Remember, you're also invited to the Hallmark Hall of Fame on television on Sundays, starring Miss Sarah Churchill. Until next week then, this is Lionel Barry Moore saying good night. That are sold only in stores that have been carefully selected to give you expert and friendly service. Remember a Hallmark card when you carry it up and send the very best. Our producer director is William Gay. Our script tonight was written by Wilbur James. Marcus Whitman was played by John Stevenson, featured in our cast tonight were Charlotte Lawrence, Alistair Duncan, Lawrence Dupkin, Ted DeCorsia, Harry Bartel, John Boehner, Tony Barrett, Holly Barron, her Butterfield. This is Frank Goss saying good night to you all until next week at the same time when we present another true story of an inspiring moment in the life of a famous person. Next week we honor Mary Ann Vickerdike on the Hallmark Hall of Fame. This is the CBS Radio Network. This is KMBC, Kansas City, Missouri.


So you want to sell on eBay you're thinking about opening the store You're not sure what to go for don't panic what we're here for it's never been easier than now to open a store There are a few factors to consider before going into this new so remember monthly running costs payment when you do First payment is pro rata plus the following month subscription in advance now with the pro rata You not only do you have to pay for the pro rata along with the first month payment in advance But you will get a pro rata amount of free allowance per the days that you're paying in that first month So my advice is when you do sign up make sure it's on either the last day of the month or the first day of the month in order to reduce the amount of costs it's going to incur okay, so let's crack on with this us edition of the Subscription shop packages and we'll start by going through the available packages for your store So there are five subscription levels to choose from and they've never made it easier than what they have now to get going on the platform So you have the starter package the basic package the premium package the anchor package and the enterprise package So for the ease of going through the packages and what they cover I'm going to choose the cheaper of the two options for the packages as you have two styles of Subscribing you either have the monthly plan or the yearly plan for the US site Which is not something we have on the UK site or the Australia site and many of the others so we'll go with the Yearly plan, but you're paying obviously this amount is how much is costing you per month But you're paying on a monthly basis. Let's begin. So with the starter package you are looking at a monthly cost of four dollars and ninety five cents excluding taxes and For this package it is the easiest way to get on and gives you a great package For what you get as well So there's no rule. There's no reason not to go for the starter package if you're looking at selling on a regular basis so you basically just need to have an equivalent of 15 fixed price listings per month which would cover your four dollars ninety five and That's calculated at the thirty five cents per listing It will cost if you didn't have even starter package. So let's have a look. So for the starter package, you get 250 fixed price listings you get 250 auction listings and Any additional costs for additional listing fees are charged at 30 cents an insertion you'll also get a final valuation fee from between three and 15 percent Then you move on to the basic package, which is 21 dollars and ninety five cents excluding taxes Now for this one you would need to have an equivalent of 63 fixed price listings Before you'd need to look at upgrading to the basic package at that point you on that package would receive 1000 fixed price listings, which is a great package 250 auction listings Any additional Insertion fees would cost 25 cents each and your final valuation fees on this package are two point between two point five and 15 percent Now if you see that you're growing larger than this and it's becoming more of a part-time thrifting job You could be looking at moving on to the premium package at a cost of $59.99 Excluded taxes for this one you just need to have an equivalent of 172 fixed price listings per month for it to be worth moving up to the premium package For this you would get 10,000 fixed price listings 500 auction listings any additional insertion fee costs would run at 15 cents each and You find a valuation fees are between two point five and fifteen percent moving on to the anchor store Which is running at a cost of two hundred and ninety nine dollars and ninety five cents excluding taxes You would need to have an equivalent of 857 fixed price listings Before you'd need to look at upgrading to the anchor store Which point you would then be able to have twenty five thousand fixed price listings per month one thousand auction listings per month and Then just an additional insertion fee cost per listing above this of just ten cents each And again, you find a valuation fees are the same again 2.5 between 2.5 and 15 percent now moving on to the highest package Now I think you'd only be looking at this if you were investing big and you had a massive storage of stock and Were probably not even looking on YouTube for advice to be fair, but That would be the enterprise store at a cost of two thousand nine hundred and ninety five dollars and ninety five cents Excluding taxes per month and you need to have an Least eight thousand five hundred and seventy two fixed Listings per month Before it's worth going to an enterprise store You would then also receive 100,000 fixed price listings 2,500 auction listings and any additional insertion fees costs would run at ten cents per listing final valuation fees of course run between 2.5 and 15 percent Now with regards to the anchor store and the enterprise store The difference between those two Other than the costs would simply be on the enterprise store You do have the option if you excessively Reaching that point of a hundred thousand listings a month and you need more You can purchase as a one-off payment 10,000 fixed price listings Additionally for two hundred and fifty dollars in a month and if you needed fifty thousand fixed price listings more That would cost you an additional 1,000 So There you have it that are is all the packages available in the US store platform Obviously you would need to consider Many other factors above and beyond this Obviously you need to be making sure that your turnover and what you're making profit-wise is going to be enough to cover these costs for whichever package you may go for and Additionally is making sure that you can continue that Throughout the year and come out the other side in profit as best as you can speculate So with that said This is all the information I have for you on this if you do have any more questions though by all means drop a comment below or Obviously ping me a message through the email address on the description Happy to help if you have any thoughts or inquiries or any suggestions Pass them along they all come in handy for everyone on the within the community and on the platform Okay guys, so keep it real