Datasets:
willtheorangeguy
/
2021-Ship-It-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.8k
[1030.06 --> 1034.32] And we're transitioning to the name plan or DAG potentially.
[1034.52 --> 1034.74] Right.
[1035.10 --> 1035.84] Oh, that's a good one.
[1036.00 --> 1036.48] DAG this.
[1037.64 --> 1038.34] DAG this.
[1039.20 --> 1040.70] It asked me to enter my username.
[1040.82 --> 1042.34] This will be stored encrypted, by the way,
[1042.34 --> 1044.82] because it's, no, this will be stored as text.
[1045.26 --> 1045.94] Nothing secret.
[1046.08 --> 1046.56] It's Gerhard.
[1046.64 --> 1047.42] You already guessed it.
[1047.78 --> 1050.26] And then it asks me for my Docker Hub password
[1050.26 --> 1051.96] so that it can push the image.
[1052.48 --> 1056.24] These are stored encrypted using SOPs locally.
[1056.44 --> 1058.28] And then there's like a couple of things here.
[1058.36 --> 1059.18] We'll skip over them.
[1059.26 --> 1060.44] And then we provide the inputs.
[1060.96 --> 1063.98] Those inputs are important because that's what the environment
[1063.98 --> 1067.36] or the plan or the DAG, as Joel mentioned, calls it.
[1067.80 --> 1070.30] So we have the app, which is basically the whole source code.
[1070.30 --> 1072.80] There's a couple of things that we need from the environment,
[1072.94 --> 1074.16] like the git shah, git author.
[1074.48 --> 1074.68] Hmm.
[1075.08 --> 1076.70] I don't think I fixed those.
[1076.78 --> 1077.62] I need to fix them.
[1078.34 --> 1078.66] Okay.
[1078.96 --> 1079.20] Okay.
[1079.24 --> 1080.72] This is something which still needs to improve.
[1080.78 --> 1082.46] I just realized going through this now.
[1082.54 --> 1082.70] See?
[1083.04 --> 1083.40] So good.
[1083.48 --> 1084.38] We're doing these things.
[1084.98 --> 1085.70] So helpful.
[1086.38 --> 1086.80] Cool.
[1087.04 --> 1089.16] So then the Docker host, which is the remote one,
[1089.18 --> 1090.30] it knows how to connect to it.
[1090.34 --> 1094.18] And then it runs the same command that you've seen in GitHub Actions.
[1095.14 --> 1095.46] Docker.
[1095.84 --> 1096.04] Sorry.
[1096.52 --> 1096.80] Docker.
[1097.52 --> 1098.78] That's like a Freudian slip.
[1099.22 --> 1099.58] Dagger.
[1099.58 --> 1101.28] Dagger up.
[1101.64 --> 1103.54] Log level debug environment CI.
[1104.54 --> 1105.78] And that's exactly the same thing.
[1106.36 --> 1108.88] The other part of this is obviously the CI queue.
[1109.36 --> 1112.84] And this is like all the code that's actually like declares the pipeline.
[1113.12 --> 1115.02] And what is this CI.queue?
[1115.10 --> 1116.14] How would you describe it?
[1116.14 --> 1121.96] It's basically the description of those various stages that we were describing earlier.
[1121.96 --> 1124.86] So there's the app image.
[1124.96 --> 1130.08] You have the test container or the test DB container definition prior to that.
[1130.74 --> 1132.86] And then let's see.
[1132.96 --> 1133.96] This is some of the...
[1133.96 --> 1144.86] So depths is basically kind of helping copy the actual application, which is all the changelog.com source code into a container.
[1144.86 --> 1145.78] Mm-hmm.
[1145.78 --> 1157.46] And then we have some just queue variable or queue fields in essence that help us store some information about how we want to be mounting these dependency caches and build caches.
[1157.82 --> 1158.42] Yep.
[1158.42 --> 1161.16] So we also do the same thing for node modules.
[1161.16 --> 1175.38] And then this depths compile, hashtag depths compile, is we're using that basically as a way to describe a kind of structure that we're then going to apply in a few other places.
[1175.80 --> 1185.16] So you can see depths compile test actually uses that definition and specializes it with args mix and test.
[1185.16 --> 1191.30] And we do the same thing with dev and prod, if I remember correctly.
[1191.46 --> 1193.08] Depths compile dev is right down here.
[1193.20 --> 1194.20] So the only difference, you're right.
[1194.28 --> 1201.26] The mix env is the same definition of depths compile with like, you know, something changed, actually added, right?
[1201.30 --> 1202.62] Because it depends stuff to it.
[1203.46 --> 1203.70] Okay.
[1203.84 --> 1204.74] And what is queue?
[1205.12 --> 1208.02] So queue is a configuration language.
[1208.52 --> 1213.14] It aims to be a better JSON, a better YAML.
[1213.14 --> 1216.78] It stands for configure, unify, and execute.
[1217.32 --> 1217.48] Yeah.
[1217.74 --> 1222.90] And basically, I think Joe will be able to continue after that.
[1223.58 --> 1223.96] Yeah.
[1224.30 --> 1227.46] So like Guillaume said, it's a configuration language.
[1228.02 --> 1236.66] And one of the things that I think is really lovely about queue is schema definition, data validation.
[1236.66 --> 1244.76] And it basically allows you to create configurations that have types.
[1245.24 --> 1248.80] So they can be type checked, preferably before you get to prod.
[1249.28 --> 1249.66] Yeah.
[1250.88 --> 1252.50] And that actually is true.
[1252.62 --> 1253.46] It's how it works.
[1253.46 --> 1259.16] I personally love that it is not whitespace dependent like YAML is.
[1259.32 --> 1264.76] I've been bit so many times by that with Helm and other various tools.
[1264.90 --> 1266.08] Ansible comes to mind too.
[1267.20 --> 1268.92] There's lovely things about those tools.
[1269.12 --> 1275.20] And I've found myself bitten by that bug and a number of them.
[1275.20 --> 1277.74] That's why YAML vaccine resonated with you, right?
[1277.74 --> 1281.92] When I mentioned it, that's exactly what I meant because you had the bug multiple times.
[1282.06 --> 1283.10] And damn it, it's not fun.
[1283.68 --> 1283.98] Yeah.
[1284.24 --> 1284.62] Yeah.
[1284.62 --> 1292.12] I've had production deploys fail because an engineer added an environment variable and used tabs instead of spaces in a Helm chart.
[1292.48 --> 1297.16] I prefer not having those sorts of problems that are avoidable.
[1297.56 --> 1301.14] And queue is a really powerful tool for doing that.
[1301.14 --> 1318.70] Just to kind of dig into the schema definition stuff a little bit deeper because I think it's useful to understand, you could basically define the shape of a particular configuration, including constraints on different fields.
[1318.70 --> 1323.06] So if you want a good example of this might be like a Kubernetes deployment.
[1323.58 --> 1329.72] So you can have a Kubernetes deployment with your API version, your kind deployment.
[1329.72 --> 1339.48] And then you can, for instance, say, set the CPU field and actually set a constraint on that.
[1339.56 --> 1342.54] You can set an upper bounds and a lower bound, et cetera.
[1342.54 --> 1354.16] And then when any configuration from a developer or an SRE comes into that, if it doesn't match that specification, then the compile of the queue will fail.