text
stringlengths
0
1.8k
[2813.58 --> 2814.62] You can verify them.
[2814.62 --> 2817.38] And finally, I end up with my
[2817.38 --> 2819.10] pipelines itself, just having
[2819.10 --> 2820.92] several lines of code, which is
[2820.92 --> 2822.46] basically configuration, not the
[2822.46 --> 2823.72] pipeline definition itself.
[2824.32 --> 2825.56] And all the pipeline exists
[2825.56 --> 2827.60] separately as a separate deliverable,
[2827.76 --> 2829.42] which is verified, which is
[2829.42 --> 2830.82] tested against vendors,
[2830.98 --> 2833.66] configurations, and which can be
[2833.66 --> 2834.68] reduced quickly.
[2834.84 --> 2836.60] Should I decide how to implement
[2836.60 --> 2837.64] a different pipeline?
[2837.94 --> 2839.52] For example, should I decide
[2839.52 --> 2841.88] how I deploy the system or even
[2841.88 --> 2843.02] how I build the system?
[2843.02 --> 2844.60] And do you have an example that
[2844.60 --> 2845.72] you can share with us for us to
[2845.72 --> 2847.28] see what it looks like, the end
[2847.28 --> 2848.38] result of that process?
[2848.78 --> 2850.06] So one of the examples you can
[2850.06 --> 2851.42] take a look at is Jenkins
[2851.42 --> 2852.90] Infra slash pipeline library.
[2853.50 --> 2855.18] So this is Jenkins pipeline library
[2855.18 --> 2856.92] we use for building Jenkins
[2856.92 --> 2857.36] components.
[2857.92 --> 2859.72] We have something like 1800
[2859.72 --> 2862.24] plugins available in our
[2862.24 --> 2862.86] update centers.
[2863.38 --> 2864.98] And basically we have two standard
[2864.98 --> 2866.14] flows right now, Maven and
[2866.14 --> 2866.64] Gradle.
[2866.98 --> 2868.46] So for these flows, we offer
[2868.46 --> 2869.28] pipeline library.
[2869.46 --> 2871.04] It is very complex inside.
[2871.22 --> 2872.34] So for example, there is common
[2872.34 --> 2873.66] once they build plugin and has
[2873.66 --> 2875.70] something like 300 lines in the
[2875.70 --> 2876.40] pipeline library.
[2876.94 --> 2879.32] But for end users like our
[2879.32 --> 2881.00] Jenkins plugin developers and
[2881.00 --> 2882.88] maintainers, they just get this
[2882.88 --> 2884.96] build plugin step where they pass
[2884.96 --> 2886.42] several options, like whether they
[2886.42 --> 2888.16] want to build on Linux, Windows,
[2888.34 --> 2889.86] which Jenkins core versions they
[2889.86 --> 2890.78] want to test against.
[2891.10 --> 2891.60] And that's it.
[2891.72 --> 2893.32] So it's basically one or two lines.
[2893.52 --> 2894.20] You can take a look.
[2894.34 --> 2895.56] I will share the link later.
[2895.92 --> 2898.54] It's all open source and all CIE is
[2898.54 --> 2899.28] also accessible.
[2899.72 --> 2900.12] Take a look.
[2900.12 --> 2900.54] I will.
[2900.66 --> 2900.78] Yeah.
[2900.82 --> 2901.42] Thank you for that.
[2901.52 --> 2903.56] And there is a test automation for
[2903.56 --> 2905.06] both unit tests and integration
[2905.06 --> 2905.80] tests there.
[2905.90 --> 2906.20] Thank you.
[2906.28 --> 2907.50] I'll definitely check that out.
[2907.56 --> 2908.78] And I'll also include it in the
[2908.78 --> 2909.20] show notes.
[2909.44 --> 2909.64] Cyril?
[2909.86 --> 2911.54] Listening to you, it reminds me
[2911.54 --> 2913.14] something that I saw when I was
[2913.14 --> 2914.70] working on continuous delivery,
[2914.90 --> 2916.76] continuous integration, when I was
[2916.76 --> 2918.18] product manager at CloudBees two
[2918.18 --> 2920.66] years ago, is the importance of
[2920.66 --> 2923.40] standardization of the processes.
[2923.40 --> 2926.60] We should manage the CI process, CI
[2926.60 --> 2928.32] pipelines, CI, CD pipelines of
[2928.32 --> 2930.86] applications of microservices as
[2930.86 --> 2932.56] a kettle, not as pets.
[2933.10 --> 2935.68] I see the same question on
[2935.68 --> 2937.86] observability, where the observability
[2937.86 --> 2939.74] of your different applications on
[2939.74 --> 2941.36] microservices in your organization
[2941.36 --> 2944.02] should also be managed as a kettle
[2944.02 --> 2945.24] rather than as pets.
[2945.76 --> 2947.62] And I think this is a very important
[2947.62 --> 2950.54] thing for your operations to remain
[2950.54 --> 2951.06] sustainable.
[2951.06 --> 2953.26] Speaking about important things,
[2953.60 --> 2955.76] Dan Lawrence was saying this.
[2956.90 --> 2959.22] Your build system should be at least
[2959.22 --> 2960.82] as secure as your production
[2960.82 --> 2961.40] environment.
[2961.60 --> 2962.64] What do you think about that, Cyril?
[2962.74 --> 2964.58] What I think about is, yes, we have
[2964.58 --> 2967.02] seen it last year with supply chain
[2967.02 --> 2968.58] attacks that have been visible.
[2968.86 --> 2970.70] It's also something for which we are
[2970.70 --> 2973.22] thinking about on the open telemetry
[2973.22 --> 2975.00] instrumentation of the continuous
[2975.00 --> 2977.34] delivery pipeline, where we see the
[2977.34 --> 2980.30] importance of capturing audit trails