text stringlengths 0 1.8k |
|---|
[186.86 --> 195.90] It gave me an opportunity to dig into Dagger and the tool and the way that we use it more than I had thus far. |
[196.48 --> 198.34] I'm relatively new to Dagger. |
[198.34 --> 202.80] So this was part of my learning about how our system actually works. |
[203.76 --> 215.60] And it was fun to kind of begin to grok how we use Q, how we use BuildKit, and how the layers and different file system states work together in those contexts. |
[216.10 --> 225.90] And it was also fun to work with you and Guillaume and try to figure out how to replicate what you've done in CircleCI inside of Dagger. |
[225.90 --> 234.86] Like you said, in part so that we could actually transition it over to GitHub Actions or wherever else you wanted to run it. |
[235.04 --> 235.16] Right. |
[235.24 --> 235.68] I got you. |
[236.36 --> 237.38] What about you, Guillaume? |
[237.70 --> 240.68] For me, it was really fun working with you. |
[240.68 --> 246.24] One of the things, maybe some of headaches, because I didn't know CircleCI. |
[247.00 --> 250.98] And it's quite interesting to, because as I was helping you, I know Dagger. |
[251.40 --> 252.38] I don't know this technology. |
[252.60 --> 255.68] So to help you port it, I had to learn a lot of things, mix. |
[255.82 --> 256.62] I didn't get it. |
[256.78 --> 259.52] And we encountered a lot of issues along the way. |
[259.52 --> 265.32] And in order to tweak them, to fix them, you need to properly understand what you're doing. |
[265.52 --> 269.92] Because your config at the moment, the SQLCI one, is quite a big one. |
[270.30 --> 273.24] And in order to port it, we need to understand it properly. |
[273.56 --> 274.50] But it was a lot of fun. |
[275.08 --> 276.60] That is actually my key takeaway as well. |
[276.76 --> 278.52] You know, I wasn't expecting to learn as much. |
[278.76 --> 281.02] I was hoping, but I wasn't expecting it. |
[281.54 --> 284.20] And then, you know, with you two, it was great. |
[284.20 --> 285.60] We went on such a journey. |
[286.28 --> 293.26] And I think what helped is that we didn't have a lot of time, but we had long gaps between us working together. |
[293.66 --> 298.04] So maybe it was like a couple of days, and then we got again for like half an hour or an hour or an hour. |
[298.84 --> 300.44] Joel, you're in Colorado. |
[301.00 --> 303.10] And Guillaume is in Paris, so he's like an hour ahead of me. |
[303.34 --> 306.80] I think that really helped, because we, in a way, we found a pace. |
[307.26 --> 309.14] And then we just bounced ideas off one another. |
[309.44 --> 311.70] And we bridged that gap really nicely, I think. |
[311.70 --> 322.90] Yeah, I think that's one of the things that I got out of this, too, is just where we are now and what's possible with Dagger today and some of the difficulties that we currently have. |
[323.22 --> 331.20] Interesting interactions between Q and BuildKit and how we're interpreting that Q and applying it to BuildKit states. |
[331.78 --> 338.90] And then kind of what we're doing with this new release, just what I'm seeing as being possible in that context. |
[338.90 --> 342.96] And just how much more intuitive and powerful it's going to be. |
[344.16 --> 351.22] So that was part of what was fun for me, was learning what our current state is while learning where we're headed. |
[352.12 --> 356.94] And seeing where that delta is actually going to be an immense improvement in the tool. |
[357.90 --> 360.12] So what does the new pipeline look like? |
[360.36 --> 363.64] We get and compile the dependencies, and we do this in parallel. |
[363.64 --> 365.32] So we do test and we do prod. |
[365.82 --> 367.46] The tests, we need to compile them. |
[367.68 --> 369.08] Then we use a cache. |
[369.38 --> 371.14] And this is something to do with the volumes, right? |
[371.18 --> 372.98] Like to copy all the layers. |
[373.30 --> 377.18] We don't need to go into too much detail, but it's BuildKit and Q working together. |
[377.58 --> 378.56] And then we run the tests. |
[379.04 --> 381.44] Before we can run the tests, we need to start the test database. |
[381.86 --> 382.74] It's an ephemeral one. |
[382.78 --> 387.72] It's just a container, PostgreSQL, because the tests are integration tests, some of them. |
[388.00 --> 388.94] So they need a database. |
[388.94 --> 392.22] And then we stop the database when the tests finish running. |
[392.44 --> 394.68] Now in parallel, we resolve the assets. |
[394.96 --> 398.10] These are like the CSS, JavaScript, all that in development. |
[398.84 --> 400.96] It's like a step towards production. |
[401.20 --> 402.28] Then we digest them. |
[402.86 --> 405.32] And that is one of the inputs to the production image. |
[406.10 --> 410.58] On the right-hand side, we have to compile the dependencies for production. |
[410.94 --> 412.40] We have the same caching mechanism. |
[412.72 --> 417.90] And this is like, it's a necessary step based on the current version of Dagger, |
[417.90 --> 420.40] which, by the way, this is something which will improve. |
[421.66 --> 423.22] And how do I know that? |
[423.30 --> 424.72] Well, Joel's been telling me all about it. |
[424.74 --> 426.82] And he's been very excited, right, to work on that. |
[426.90 --> 429.06] And maybe you want to mention a little bit about that. |
[430.50 --> 430.68] Yeah. |
[430.86 --> 436.48] So we're basically improving the DX, the developer experience, |
[436.86 --> 444.92] around the low-level interactions that Dagger has with BuildKit. |
[444.92 --> 450.28] So we're basically changing the API to BuildKit. |
[450.48 --> 456.62] Right now we have kind of an implicit, kind of spread all over the place API to BuildKit |
[456.62 --> 459.60] instead of our Q packages. |
[460.80 --> 464.50] And the changes that we're in the process of building out |
[464.50 --> 467.10] actually make that API much more explicit. |
[467.10 --> 468.00] Right. |
[468.00 --> 472.92] Kind of form like a low-level representation of the BuildKit API within Q, |
[473.64 --> 477.28] which then can be used by our packages or other packages |
[477.28 --> 481.12] to interact with BuildKit, |
[481.38 --> 487.46] the various file system states and actions on those file systems as well. |
[487.46 --> 490.84] So, yeah, I think this is going to get a lot better. |
[491.68 --> 493.58] We'll be able to actually use some of the features |
[493.58 --> 497.26] that we weren't able to use this time around of BuildKit, |
[497.38 --> 500.32] like mounting volumes in a much cleaner way. |
[501.00 --> 501.16] Okay. |
[501.66 --> 502.86] And then when that is done, |
[503.16 --> 506.76] the last step is to obviously assemble the image and push it to Docker Hub. |
[506.94 --> 509.38] The one step which we don't have here and we would want |
[509.38 --> 514.94] is to Git commit the digest of the image that was deployed |
[514.94 --> 517.20] so that we can do like a proper GitOps way |
[517.20 --> 520.36] so that rather than our production pulling latest, |
[521.14 --> 522.92] and, you know, there's like a couple of issues around that, |
[523.02 --> 526.04] I won't go into them, but we know we have to improve that. |
[526.52 --> 529.38] We would like Dagger in this case to make that Git commit. |
[529.68 --> 532.40] And I say Dagger, but now that I realize it could just be GitHub Actions. |
[532.40 --> 533.58] And why do I say that? |
[534.16 --> 535.38] Part of this pull request, |
[535.72 --> 536.96] we did the integration with GitHub Actions |
[536.96 --> 538.00] and we'll get to that in a minute. |
[538.00 --> 540.98] But first of all, I would like to show |
[540.98 --> 543.92] what the new pipeline looks like and what makes it better. |
[544.24 --> 548.78] So what are these green items here, Guillaume? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.