text stringlengths 0 2.29k |
|---|
**Jerod Santo:** And then opens up PR and then we can just merge? |
**Gerhard Lazu:** That's it, Jerod. That's it. That's it. |
**Jerod Santo:** Okay. |
**Gerhard Lazu:** See, it's stuff like this that gets me really excited. \[laughs\] |
**Jerod Santo:** You're getting me. |
**Gerhard Lazu:** Yeah. |
**Jerod Santo:** Okay. So that's cool. How does that play into the other thing which happened recently, thanks to Chris -- and by the way, by the time this episode goes out, we will have shipped an episode of the Changelog with Brigit Murtaugh from the Dev Containers spec, from the VS Code team, talking all about this,... |
**Gerhard Lazu:** Yeah. It all builds on top of it. This is brilliant. |
**Adam Stacoviak:** This is brilliant... \[laughs\] |
**Gerhard Lazu:** It is. And it's not me, it's the combination of people that came together, right? I wasn't expecting Chris to come along. |
**Jerod Santo:** Nobody was. |
**Gerhard Lazu:** That was great, it was amazing. So based on that - that was pull request 437 in our code base - I did a follow-up, 449, which basically changes the reference in the Dev Container with our runtime image, that is now pulled from GHCR. And because we're running GitHub Codespaces, that will be very fast. ... |
**Jerod Santo:** So that works currently? |
**Gerhard Lazu:** That's how it works currently. If you go and open the file - come on, let's check it out. |
**Jerod Santo:** Because I just did it last week in preparation for that conversation with Brigit, and one thing I noticed is pulling from Docker Hub, just the entire -- the first running Codespaces experience. I mean, it's probably five to seven minutes, you know... |
**Gerhard Lazu:** That has improved. The pull request that I mentioned, 449 - it no longer builds it; it references the already built runtime image. If you check out in the Dev Containers directory, if you look at the Docker Compose file, line five, now it has the image reference. So the runtime image is no longer buil... |
**Jerod Santo:** I'll try that again. |
**Gerhard Lazu:** There you go. Let me know how it works. But if not, we'll work on it some more. And all this stuff, all these things, we can start templating. Once we get it in the pipeline, there will be a single place where we declare those versions. As soon as the image builds successfully, and because we go throu... |
**Adam Stacoviak:** Who else is doing it like this? How state of the art is this? |
**Gerhard Lazu:** I don't know. I would say it's pretty cutting edge... Because we are redefining the CI/CD with Dagger. We really are. I mean, the CI/CD as code - forget like any weird languages... And some of the stuff that we have coming - I can't talk about all the things... But I'm like six months ahead, and I'm s... |
For example, last Friday - it was just a few days ago - we shipped services support. It's an experimental feature. If you're listening to this, you're not supposed to use it, so please don't, because it may be broken in a number of ways we don't know... But Changelog will be the first one to use the services support in... |
**Jerod Santo:** And what are the ramifications of that? |
**Gerhard Lazu:** \[33:57\] Well, you spin up containers in code. Just as you write your code, you can say, "Spin me up a PostgreSQL container", and when it's spun up, connect it to this other container where the test will run. You can have the waiting -- I mean, we used to do nc, netcat, for heaven's sake, to wait for... |
**Jerod Santo:** Let's not knock on netcat, Gerhard. Come on. Sweet tool. |
**Gerhard Lazu:** No, it's amazing. I love it. It is old school. It's amazing. But what's not amazing is that you have to -- you're forced to combine scripting and YAML. |
**Jerod Santo:** To wait. Yeah, you're waiting for a service to be ready for you. |
**Gerhard Lazu:** In a weird way. Exactly. Rather than doing it in code. Why wouldn't you do all these things in code? Because now we can start orchestrating containers. But orchestrating for the purpose of CI/CD. Let's be clear about that. |
**Jerod Santo:** So we're going to be like a poster child for Dagger, aren't we? I mean, these people have to love us. We're using all the bleeding -- I mean, by these people, I mean you people. |
**Gerhard Lazu:** I love you. I'm Dagger. |
**Jerod Santo:** I know you are. \[laughter\] That's cool, man. I love that we're a testbed for cool new things. And we're definitely right there on the edge... I wonder how much bleeding we're gonna do. Well, we are defining it. Well, we'll find out... And by the way, you have the right person to fix it, who does the ... |
**Jerod Santo:** Yes. Alright, cool. Exciting times. I've always wanted to have one string in my codebase, in which I could update the version of Elixir. |
**Gerhard Lazu:** It's there. |
**Adam Stacoviak:** And then docs, too. That's so cool. Updating docs is a cool thing. Still docs suck; especially a readme. Like, when you go to the readme, it's like -- I've gone there recently with other things I'm working on... It's referencing the old release< for example, in the readme. It says in the installa... |
**Jerod Santo:** It could always be outdated. |
**Gerhard Lazu:** Not anymore. |
**Jerod Santo:** So is every -- so because we do basically master branch base deploying, is every push to master a release, effectively? |
**Gerhard Lazu:** Yeah. That hasn't changed in years. Since I've been around, that hasn't changed. |
**Jerod Santo:** Right. What about on PRs and branches? How does that work? |
**Gerhard Lazu:** We don't deploy. So we now run tests, by the way... We didn't use to run tests in pull requests. Oh, dang it, I don't know how I overlooked that thing... |
**Jerod Santo:** We just close them all, yeah. \[laughs\] |
**Gerhard Lazu:** Yeah, yeah, yeah. So that was actually one of the first things, pull request 436. So since pull request 436, which by the way, happened in the same Kaizen, since Kaizen 8... We are now running tests for every pull request. And we do that by basically leveraging the built-in Docker engine in GitHub Act... |
**Jerod Santo:** Which would give us deployment previews, effectively. |
**Gerhard Lazu:** We absolutely could. That's it. That's it, yup. And the nice thing would be - I think I'm very keen to try and do that in Dagger. The reason why I'm keen to do that is because of the services support. I'm pretty sure when they were designed no one thought about this, but we can have longer-running env... |
We could run a very lightweight version of the Changelog in the context of the CI/CD, in the context of the pull request. Because it doesn't have to serve a lot of traffic, it doesn't need to be anything big... The CI/CD is already there. You have a VM where you're running the actual code for your tests. So why wouldn'... |
**Jerod Santo:** You're blowing my mind, Gerhard. I'm not even -- |
**Gerhard Lazu:** \[38:00\] That's a crazy idea, right? No one has thought about that before. \[laughs\] |
**Jerod Santo:** Alright... |
**Gerhard Lazu:** See, I told you - six months from now. It's the future. |
**Jerod Santo:** Okay. Well, that's exciting. |
**Gerhard Lazu:** So when a pull request opens, basically, the GitHub runner that runs all the various checks, one of them, we basically keep it running for longer; or we don't even use GitHub runners at that point. So one of the things which we run - we spin up a Changelog, a preview one - we still need to figure out ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.