text stringlengths 0 1.8k |
|---|
[2300.62 --> 2302.24] all of them should be just one |
[2302.24 --> 2304.60] deliverable for the end system and |
[2304.60 --> 2306.28] this deliverable should be tested |
[2306.28 --> 2308.74] you know it's on icd pipelines so there |
[2308.74 --> 2311.00] is much less opportunity for mistakes |
[2311.00 --> 2312.90] and end user pipelines |
[2312.90 --> 2315.08] from the perspective of code like |
[2315.08 --> 2317.70] config as code do you mean just |
[2317.70 --> 2320.16] config like yaml or some other format |
[2320.16 --> 2321.76] what it does that code look like |
[2321.76 --> 2323.62] yes so if you talk specifically about |
[2323.62 --> 2325.20] jenkins pipeline yes historically it |
[2325.20 --> 2327.34] uses groovy dsl so it's groovy like |
[2327.34 --> 2329.98] language to some security and context |
[2329.98 --> 2332.18] requirements for failover but it looks |
[2332.18 --> 2333.94] like groovy and there are multiple ways |
[2333.94 --> 2334.62] to define it |
[2334.62 --> 2337.08] so firstly it can be a scripted pipeline |
[2337.08 --> 2338.92] which is basically just root with a cell |
[2338.92 --> 2341.04] it can be declarative pipeline which |
[2341.04 --> 2343.54] gets us closer to obviously declarative |
[2343.54 --> 2345.80] syntax but you can also deploy them as |
[2345.80 --> 2348.30] yaml these days okay so it's your choice |
[2348.30 --> 2350.44] how you actually implement them and |
[2350.44 --> 2351.84] jenkins is a tool supports possible |
[2351.84 --> 2354.24] and would you configure jenkins using |
[2354.24 --> 2357.08] the kubernetes api or would you target |
[2357.08 --> 2359.66] the jenkins master know directly how that |
[2359.66 --> 2362.36] works in my case i would rather use jenkins |
[2362.36 --> 2365.40] for engine management because if you put |
[2365.40 --> 2367.66] it in kubernetes and it will be still a |
[2367.66 --> 2369.20] question how you actually retrieve |
[2369.20 --> 2371.98] these configurations into jenkins and |
[2371.98 --> 2373.50] ultimately it doesn't matter because |
[2373.50 --> 2376.24] still a system in the same repository it |
[2376.24 --> 2378.26] doesn't matter how exactly it's deployed |
[2378.26 --> 2378.54] yeah |
[2378.54 --> 2380.16] you better get inside jenkins just gives |
[2380.16 --> 2382.02] you more flexibility because if needed |
[2382.02 --> 2383.86] you can change on the flight without |
[2383.86 --> 2385.50] redeploying significant parts of your |
[2385.50 --> 2385.82] system |
[2385.82 --> 2399.24] hey shippers this episode is brought to |
[2399.24 --> 2401.70] you by our friends at equinix metal if |
[2401.70 --> 2403.08] you want the choice and control of |
[2403.08 --> 2404.82] hardware with low overhead and the |
[2404.82 --> 2406.90] developer experience of the cloud check |
[2406.90 --> 2409.00] out equinix metal deploying minutes |
[2409.00 --> 2411.44] across 18 global locations from silicon |
[2411.44 --> 2414.42] valley to sydney visit metal.equinix.com |
[2414.42 --> 2416.58] slash just add metal and receive a hundred |
[2416.58 --> 2418.50] dollars in credit to play with again |
[2418.50 --> 2421.68] metal.equinix.com slash just add metal |
[2421.68 --> 2424.74] and by our friends at fire hydrant fire |
[2424.74 --> 2426.52] hydrant is the reliability platform for |
[2426.52 --> 2428.98] teams of all sizes with fire hydrant teams |
[2428.98 --> 2431.02] achieve reliability at scale by enabling |
[2431.02 --> 2433.50] speed and consistency from your service |
[2433.50 --> 2436.18] deployment to an unexpected outage here's |
[2436.18 --> 2437.30] the thing when your team learns from an |
[2437.30 --> 2439.18] incident you can codify those learnings into |
[2439.18 --> 2441.46] repeatable automated runbooks and these |
[2441.46 --> 2443.34] runbooks can create a slack incident channel |
[2443.34 --> 2445.42] notify particular team members create |
[2445.42 --> 2448.10] tickets schedule a zoom meeting execute a |
[2448.10 --> 2450.32] script or send a web hook here's how it |
[2450.32 --> 2452.44] works your app goes down an alert gets |
[2452.44 --> 2454.22] sent to a specific slack channel which can |
[2454.22 --> 2456.34] then be turned into an incident that will |
[2456.34 --> 2458.36] trigger a workflow you've created already in |
[2458.36 --> 2460.94] a runbook a pinned message inside slack |
[2460.94 --> 2463.24] will show all the details the jira or |
[2463.24 --> 2465.78] clubhouse ticket the zoom meeting and all |
[2465.78 --> 2467.76] of this is contained in your dedicated |
[2467.76 --> 2469.90] incident channel that everyone on the team |
[2469.90 --> 2471.78] pays attention to now you're spending less |
[2471.78 --> 2473.28] time thinking about what to do next and |
[2473.28 --> 2474.80] you're getting to work actually resolving |
[2474.80 --> 2477.22] the issue faster what would normally be |
[2477.22 --> 2479.08] manual tickets across the entire spectrum |
[2479.08 --> 2481.18] of responding to an incident can now be |
[2481.18 --> 2483.50] automated in every single way with fire |
[2483.50 --> 2485.54] hydrant and here's the best part you can |
[2485.54 --> 2488.10] try it free for 14 days you get access to |
[2488.10 --> 2489.94] every single feature no credit card |
[2489.94 --> 2491.74] required at all that way you can prove to |
[2491.74 --> 2493.86] yourself and your team that this works for |
[2493.86 --> 2499.30] you get started at firehydrant.io again firehydrant.io |
[2499.30 --> 2519.40] so like i would like us to come back to the |
[2519.40 --> 2521.42] conversation that we started having and we put a |
[2521.42 --> 2524.96] pin in it around separating the ci from the cd |
[2524.96 --> 2528.52] concern in your system right which gets code out |
[2528.52 --> 2530.88] into production what do you think about that do |
[2530.88 --> 2532.74] you think you should separate them or you |
[2532.74 --> 2535.44] shouldn't and why i would say that generally |
[2535.44 --> 2538.48] you should you should okay yes it might be |
[2538.48 --> 2541.36] still the same service per se in terms of |
[2541.36 --> 2544.92] deployment but logically ci and cd pipelines |
[2544.92 --> 2547.84] are significantly different so there are |
[2547.84 --> 2549.64] different requirements there are different |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.