text stringlengths 0 2.29k |
|---|
[2018.16 --> 2022.20] But changelog would be the first one to use the services support in Dagger. |
[2022.20 --> 2034.94] What that means is that we will be spinning up a PostgreSQL container that we need for our tests inside Dagger, inside the Dagger engine, because it now has a runtime. |
[2035.36 --> 2036.86] And what are the ramifications of that? |
[2037.24 --> 2039.28] Well, you spin up containers in code. |
[2039.70 --> 2041.14] Just as you write your code, right? |
[2041.18 --> 2043.86] Like you can say, spin me up a PostgreSQL container. |
[2044.04 --> 2047.44] And when it's spun up, connect it to this other container where the test will run. |
[2048.02 --> 2048.90] You can have the waiting. |
[2048.90 --> 2055.22] I mean, we used to do NC, Netcat, for heaven's sake, to wait for the PostgreSQL container to be available. |
[2055.84 --> 2056.92] There's like services support. |
[2057.04 --> 2059.16] There's like ugly YAML, all sorts of weird things. |
[2059.18 --> 2060.96] Let's not knock on Netcat, Gerhard. |
[2061.06 --> 2061.58] Come on. |
[2061.86 --> 2062.50] Sweet tool. |
[2062.70 --> 2063.42] No, it's amazing. |
[2063.56 --> 2064.06] I love it. |
[2064.28 --> 2065.02] It is old school. |
[2065.12 --> 2065.60] It's amazing. |
[2065.88 --> 2070.66] But what's not amazing is that you have to, you're forced to combine scripting and YAML. |
[2070.74 --> 2071.16] To wait. |
[2071.30 --> 2073.72] Yeah, you're waiting for a service to be ready for you. |
[2073.76 --> 2074.84] In a weird way, exactly. |
[2074.94 --> 2075.92] Rather than doing it in code. |
[2076.02 --> 2077.50] Why wouldn't you do all these things in code? |
[2077.50 --> 2079.94] Because now we can start orchestrating containers. |
[2080.54 --> 2082.90] But orchestrating for the purpose of CICD. |
[2083.12 --> 2084.16] Let's be clear about that. |
[2084.54 --> 2086.96] So we're going to be like a poster child for Dagger, aren't we? |
[2087.02 --> 2089.10] I mean, these people have to love us. |
[2089.30 --> 2091.28] We're like using all the bleeding. |
[2091.64 --> 2092.44] I mean, by these people. |
[2092.46 --> 2092.94] I love you. |
[2093.14 --> 2093.46] You people. |
[2093.46 --> 2093.92] I'm Dagger. |
[2094.36 --> 2095.14] I know you are. |
[2095.14 --> 2095.28] I love you. |
[2095.46 --> 2097.38] I love you. |
[2097.38 --> 2100.96] That's cool, man. |
[2101.06 --> 2105.02] I love that we're a testbed for cool new things. |
[2105.20 --> 2108.90] And we're definitely right there on the edge. |
[2109.42 --> 2111.08] I wonder how much bleeding we're going to do. |
[2111.26 --> 2112.32] We are defining it. |
[2112.42 --> 2113.22] Well, we'll find out. |
[2113.32 --> 2115.54] And by the way, you have the right person to fix it. |
[2115.72 --> 2116.42] It doesn't work. |
[2117.30 --> 2117.58] Right? |
[2117.66 --> 2118.54] Isn't that the whole point? |
[2118.98 --> 2119.34] Yes. |
[2119.78 --> 2120.24] All right. |
[2120.60 --> 2120.90] Cool. |
[2121.36 --> 2122.14] Exciting times. |
[2122.14 --> 2126.62] I've always wanted to have one string in my code base in which I could update the version of Elixir. |
[2126.84 --> 2127.34] It's there. |
[2127.60 --> 2128.46] And then docs, too. |
[2128.58 --> 2129.16] That's so cool. |
[2129.30 --> 2132.38] Like, if you update it and like updating docs is a cool thing. |
[2132.52 --> 2133.50] Like, still docs suck. |
[2133.74 --> 2134.52] Especially a readme. |
[2134.62 --> 2137.90] Like, when you go to the readme, it's like, I've gone there recently with other things I'm working on. |
[2137.96 --> 2142.32] It's like, it's referencing the old release, for example, in the readme. |
[2142.32 --> 2147.04] It says in the installation instructions, which you go to immediately, but it's referencing an old release. |
[2147.12 --> 2149.68] But if you go to the releases, there's like two new ones, for example. |
[2149.86 --> 2152.12] But the documentation is out of date. |
[2152.34 --> 2153.54] It could always be updated. |
[2154.14 --> 2154.56] Not anymore. |
[2155.20 --> 2164.94] So, because we do basically, you know, master branch-based deploying, is every push to master a release effectively? |
[2165.32 --> 2165.56] Yeah. |
[2166.32 --> 2167.58] That has not changed in years. |
[2167.84 --> 2169.32] Since I've been around, that hasn't changed. |
[2169.68 --> 2169.96] Right. |
[2169.96 --> 2172.60] What about on PRs and branches? |
[2172.90 --> 2173.48] How does that work? |
[2173.70 --> 2174.64] We don't deploy. |
[2175.38 --> 2177.10] So, we now run tests, by the way. |
[2177.20 --> 2178.78] We didn't use the run tests in Pulvericus. |
[2178.94 --> 2179.42] Oh, damn it. |
[2179.48 --> 2180.88] I don't know how I like overlooked that thing. |
[2180.88 --> 2182.20] We just closed them out. |
[2182.30 --> 2182.46] Yeah. |
[2182.88 --> 2183.38] Yeah, yeah, yeah. |
[2183.38 --> 2184.52] So, that was like one thing. |
[2184.66 --> 2186.94] That was actually one of the first things, pull request 436. |
[2188.00 --> 2197.02] 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. |
[2197.02 --> 2203.68] And we do that by basically leveraging the built-in Docker engine in GitHub Actions, which is a bit slow. |
[2203.92 --> 2205.14] And, you know, it doesn't have any caching. |
[2205.66 --> 2215.00] But it means that we are running all the pipelines, including building our runtime image, but not publishing it because there aren't credentials to do that with every pull request. |
[2215.00 --> 2218.78] So, while we don't deploy on every pull request, we could. |
[2219.36 --> 2221.64] Which would give us, like, deployment previews, effectively. |
[2221.92 --> 2222.86] We absolutely could. |
[2223.46 --> 2223.92] That's it. |
[2224.38 --> 2225.08] That's it, yeah. |
[2225.78 --> 2230.04] And the nice thing would be, I think I'm very keen to try and do that in Dagger. |
[2230.90 --> 2233.66] The reason why I'm keen to do that is because of the services support. |
[2233.66 --> 2237.26] I'm pretty sure when they were designed, no one thought about this. |
[2237.66 --> 2241.14] But we can have longer running environments. |
[2241.62 --> 2247.46] So, basically, if a CI, there's like one action which won't stop until you're okay with it. |
[2247.80 --> 2249.26] So, how do we figure out routing? |
[2249.44 --> 2249.76] I don't know. |
[2249.84 --> 2251.60] I'm really keen to explore that. |
[2252.06 --> 2259.32] We could run a very lightweight version of the changelog in the context of the CI CD, in the context of the pull request. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.