From Jenkins to BuildBot — just our experience (Тимофей Туренко, LVEE-2019) — различия между версиями
Материал из 0x1.tv
StasFomin (обсуждение | вклад) |
StasFomin (обсуждение | вклад) |
||
;{{SpeakerInfo}}: {{Speaker|Тимофей Туренко}}
<blockquote>
For big projects with complex test environment continuous integration tools selecting is not trivial. Despite Jenkins is very popular and ``easy to start'' solution it has a number of disadvantages: hard to fully implement ``everything is code'' approach, plugins mess, high resource consumption, security issues, mess of task definition languages. For MariaDB Maxscale project the alternative solution — BuildBot was chosen. The talk describes our success and failures of transition to BuildBot.
</blockquote>
{{VideoSection}}
{{vimeoembed|366001240|800|450}}
<!-- {{youtubelink|}} -->
{{SlidesSection}}
[[File:From Jenkins to BuildBot — just our experience (Тимофей Туренко, LVEE-2019).pdf|left|page=-|300px]]
{{----}}
== Thesis == |
Версия 15:16, 28 октября 2019
- Докладчик
- Тимофей Туренко
For big projects with complex test environment continuous integration tools selecting is not trivial. Despite Jenkins is very popular and ``easy to start solution it has a number of disadvantages: hard to fully implement ``everything is code approach, plugins mess, high resource consumption, security issues, mess of task definition languages. For MariaDB Maxscale project the alternative solution — BuildBot was chosen. The talk describes our success and failures of transition to BuildBot.
Содержание
Видео
Презентация
Thesis
Примечания и ссылки
- [ Talks page]