text stringlengths 0 1.8k |
|---|
[1970.70 --> 1972.36] beast jenkins in pivotal |
[1972.36 --> 1973.20] cloud foundry in the |
[1973.20 --> 1974.66] platform yeah that was |
[1974.66 --> 1975.74] like many many years ago |
[1975.74 --> 1978.72] and i'm wondering today |
[1978.72 --> 1981.22] how would you run jenkins |
[1981.22 --> 1982.18] in production what would |
[1982.18 --> 1983.44] you choose we use |
[1983.44 --> 1984.30] massively jenkins |
[1984.30 --> 1986.32] at elastic we use it in |
[1986.32 --> 1988.00] conjunction with kubernetes |
[1988.00 --> 1990.54] for our modern jenkins |
[1990.54 --> 1992.58] platform i'm a bit |
[1992.58 --> 1994.10] further away from this but |
[1994.10 --> 1995.12] i think it is very |
[1995.12 --> 1996.46] important to leverage the |
[1996.46 --> 1998.44] flexibility of docker |
[1998.44 --> 2000.46] containers to let |
[2000.46 --> 2002.00] development team customize |
[2002.00 --> 2003.00] their build environment |
[2003.00 --> 2003.82] the way they need |
[2003.82 --> 2006.48] the way to offer the |
[2006.48 --> 2007.72] capability for dev teams |
[2007.72 --> 2008.86] to customize their build |
[2008.86 --> 2009.92] environment with docker |
[2009.92 --> 2011.64] combined with the |
[2011.64 --> 2013.94] orchestration needed by a |
[2013.94 --> 2015.04] ci platform and the |
[2015.04 --> 2016.26] scalability needed by a |
[2016.26 --> 2017.86] ci platform let me |
[2017.86 --> 2019.00] believe that you should |
[2019.00 --> 2020.24] leverage kubernetes for |
[2020.24 --> 2020.92] this would you agree |
[2020.92 --> 2022.28] oleg yes and no because |
[2022.28 --> 2023.88] you better deploy your ci |
[2023.88 --> 2025.22] system which would be |
[2025.22 --> 2026.16] similar to your target |
[2026.16 --> 2027.70] environment especially if |
[2027.70 --> 2028.68] you want to do integration |
[2028.68 --> 2030.60] tests and based on that a |
[2030.60 --> 2032.14] lot of depends so if you |
[2032.14 --> 2033.36] develop deploy cloud |
[2033.36 --> 2034.80] native applications then |
[2034.80 --> 2036.14] yeah most likely you will |
[2036.14 --> 2037.84] have to run jenkins and |
[2037.84 --> 2039.34] kubernetes but it's not |
[2039.34 --> 2041.02] necessarily a case what i |
[2041.02 --> 2042.30] would like to say that if |
[2042.30 --> 2043.12] you talk about modern |
[2043.12 --> 2044.42] jenkins management so |
[2044.42 --> 2045.46] everyone heard about |
[2045.46 --> 2046.86] jenkins plugin hell and |
[2046.86 --> 2048.18] other things and it's |
[2048.18 --> 2049.96] totally a case but these |
[2049.96 --> 2051.30] days you can fully manage |
[2051.30 --> 2052.16] jenkins using |
[2052.16 --> 2054.34] configurations code and you |
[2054.34 --> 2056.24] create basically a ci cd |
[2056.24 --> 2057.72] pipeline for your |
[2057.72 --> 2058.64] automation system |
[2058.64 --> 2059.80] configuration as well you |
[2059.80 --> 2060.62] really have to be just |
[2060.62 --> 2062.04] jenkins because it can be |
[2062.04 --> 2063.46] infrastructure as code yes |
[2063.46 --> 2064.38] i would definitely |
[2064.38 --> 2065.66] recommend packaging jenkins |
[2065.66 --> 2067.20] into containers and there |
[2067.20 --> 2068.38] are tools for that there are |
[2068.38 --> 2069.44] helm charts so the |
[2069.44 --> 2071.10] operators provided by the |
[2071.10 --> 2073.20] jenkins community but on |
[2073.20 --> 2074.66] the lower level you should |
[2074.66 --> 2076.36] always know what you run and |
[2076.36 --> 2077.66] you should be able to |
[2077.66 --> 2079.32] deploy staging and to |
[2079.32 --> 2080.84] verify your instance okay |
[2080.84 --> 2081.76] whatever is your target |
[2081.76 --> 2083.16] environment here something |
[2083.16 --> 2084.86] else on the way to build |
[2084.86 --> 2085.88] your continuous delivery |
[2085.88 --> 2087.56] pipelines and related to |
[2087.56 --> 2088.84] jenkins it's a bit broader |
[2088.84 --> 2090.90] it's a topic you discussed |
[2090.90 --> 2092.18] last time when you met with |
[2092.18 --> 2093.22] the dagger people is it |
[2093.22 --> 2095.62] important to be able to run |
[2095.62 --> 2097.54] your ci pipeline to test it |
[2097.54 --> 2099.28] to develop it on your local |
[2099.28 --> 2101.22] computer there are two |
[2101.22 --> 2102.60] initiatives that struck me |
[2102.60 --> 2104.26] on this one was broad |
[2104.26 --> 2105.66] johnson with his atomist |
[2105.66 --> 2108.00] company on one other is |
[2108.00 --> 2109.78] dagger who said it's very |
[2109.78 --> 2110.98] important to be able to test |
[2110.98 --> 2112.34] locally on the development |
[2112.34 --> 2114.44] cycle of the pipeline i think |
[2114.44 --> 2115.82] it's when you design your |
[2115.82 --> 2117.16] pipeline it's important to |
[2117.16 --> 2118.76] have as much as possible |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.