From 387760ccbfab027b234ec8e8f757201c622a790d Mon Sep 17 00:00:00 2001 From: Nulo <86896666+catdevnull@users.noreply.github.com> Date: Fri, 17 Sep 2021 17:08:13 -0300 Subject: [PATCH] Improve plugin docs (#313) * docs: improve plugin docs * drone do not use ssl Co-authored-by: Anbraten Co-authored-by: Nulo Co-authored-by: Anbraten Co-authored-by: 6543 <6543@obermui.de> --- docs/docs/20-usage/51-plugins/10-plugins.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/docs/20-usage/51-plugins/10-plugins.md b/docs/docs/20-usage/51-plugins/10-plugins.md index a0ecdd6593..16a19c1c56 100644 --- a/docs/docs/20-usage/51-plugins/10-plugins.md +++ b/docs/docs/20-usage/51-plugins/10-plugins.md @@ -1,6 +1,8 @@ # Plugins -Plugins are Docker containers that perform pre-defined tasks and are configured as steps in your pipeline. Plugins can be used to deploy code, publish artifacts, send notification, and more. +Plugins are pipeline steps that perform pre-defined tasks and are configured as steps in your pipeline. Plugins can be used to deploy code, publish artifacts, send notification, and more. + +They are automatically pulled from [plugins.drone.io](http://plugins.drone.io). Example pipeline using the Docker and Slack plugins: @@ -24,7 +26,7 @@ pipeline: ## Plugin Isolation -Plugins are executed in Docker containers and are isolated from the other steps in your build pipeline. Plugins do share the build workspace, mounted as a volume, and therefore have access to your source tree. +Plugins are just pipeline steps. They share the build workspace, mounted as a volume, and therefore have access to your source tree. ## Creating a plugin