From b3828c10e22aba310fb51b05bf17915cefff7a3b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Pra=C5=BCak?= Date: Fri, 25 Oct 2019 11:42:54 +0200 Subject: [PATCH] Update README.md --- README.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index db2b99a1..1ec0a887 100644 --- a/README.md +++ b/README.md @@ -26,15 +26,14 @@ The main reason why we decided to implement the **Jenkins Operator** is the fact We want to make Jenkins more robust, suitable for dynamic and multi-tenant environments. Some of the problems we want to solve: -- volumes handling (AWS EBS volume attach/detach issue when using PVC) - [installing plugins with incompatible versions or security vulnerabilities](https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/customization/#install-plugins) - [better configuration as code](https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/customization/) -- lack of end to end tests -- handle graceful shutdown properly - [security and hardening out of the box](https://jenkinsci.github.io/kubernetes-operator/docs/security/) -- orphaned jobs with no jnlp connection - [make errors more visible for end users](https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/diagnostics/) - [backup and restore for jobs history](https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configure-backup-and-restore/) +- orphaned jobs with no JNLP connection +- handle graceful shutdown properly +- proper end to end tests for Jenkins lifecycle ## Documentation