| Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung |
| en:modul:m324_aws:topics:02 [2025/11/05 13:53] – dgaravaldi | en:modul:m324_aws:topics:02 [2025/11/05 13:55] (aktuell) – dgaravaldi |
|---|
| |
| Let's walk through the most interesting parts of Jenkins: | Let's walk through the most interesting parts of Jenkins: |
| * ''Language-agnostic'': Jenkins has a lot of plugins, which support most programming languages and frameworks. Moreover, since it can use any shell command and any software, it is suitable for every automation process imaginable (agnostic: not specific to a particular programming language aligned (ausgerichtet)). | * ''Language-agnostic'': Jenkins has a lot of plugins, which support most programming languages and frameworks. Moreover, since it can use any shell command and any software, it is suitable for every automation process imaginable. |
| * ''Extensible by plugins'': Jenkins has a great community and a lot of available plugins (over a thousand). It also allows you to write your own plugins in order to customize Jenkins for your needs. | * ''Extensible by plugins'': Jenkins has a great community and a lot of available plugins (over a thousand). It also allows you to write your own plugins in order to customize Jenkins for your needs. |
| * ''Supports most Source Control Management (SCM) tools'': Jenkins integrates with virtually every source code management or build tool that exists. | * ''Supports most Source Control Management (SCM) tools'': Jenkins integrates with virtually every source code management or build tool that exists. |
| * ''Simplicity'': The installation and configuration process is simple. There is no need to configure any additional software or the database. It can be configured completely through a GUI, XML, or Groovy scripts. | * ''Simplicity'': The installation and configuration process is simple. There is no need to configure any additional software or the database. It can be configured completely through a GUI, XML, or Groovy scripts. |
| * ''Code-oriented'': Jenkins pipelines are defined as code. Also, Jenkins itself can be configured using YAML/XML files or Groovy scripts. That allows you to keep the configuration in the source code repository and helps in the automation of the Jenkins configuration. | * ''Code-oriented'': Jenkins pipelines are defined as code. Also, Jenkins itself can be configured using YAML/XML files or Groovy scripts. That allows you to keep the configuration in the source code repository and helps in the automation of the Jenkins configuration. |
| | |
| |
| |
| ---- | ---- |
| | //agnostic: not specific to a particular programming language aligned (ausgerichtet)// |
| | |
| Based on the book: | Based on the book: |
| "Continuous Delivery with Docker and Jenkins, 3rd Edition - Third Edition By Leszko" | "Continuous Delivery with Docker and Jenkins, 3rd Edition - Third Edition By Leszko" |