mirror of
https://github.com/woodpecker-ci/woodpecker.git
synced 2025-01-15 12:05:26 +00:00
chore: rewrite intro
This commit is contained in:
parent
355ebcd508
commit
fee25583b0
1 changed files with 14 additions and 15 deletions
|
@ -1,26 +1,25 @@
|
||||||
# Welcome to Woodpecker
|
# Welcome to Woodpecker
|
||||||
|
|
||||||
Woodpecker is a CI/CD tool. It is designed to be lightweight, simple to use and fast. Before we dive into the details, let's have a look at some of the basics.
|
Woodpecker is a CI/CD tool. It is designed to be lightweight (< 200 MB memory consumption), simple to use and fast and can be used with many different Git providers and backends (docker, kubernetes, local).
|
||||||
|
|
||||||
## Have you ever heard of CI/CD or pipelines?
|
## The "CI/CD" concept
|
||||||
|
|
||||||
Don't worry if you haven't. We'll guide you through the basics. CI/CD stands for Continuous Integration and Continuous Deployment. It's basically like a conveyor belt that moves your code from development to production doing all kinds of
|
CI/CD stands for "Continuous Integration” and “Continuous Deployment.”
|
||||||
checks, tests and routines along the way. A typical pipeline might include the following steps:
|
It is a streamlined process that moves your code from development to production while performing various checks, tests, and routines along the way.
|
||||||
|
A standard CI/CD pipeline typically includes steps such as:
|
||||||
|
|
||||||
1. Running tests
|
1. Running tests
|
||||||
2. Building your application
|
2. Building the application
|
||||||
3. Deploying your application
|
3. Deploying the application
|
||||||
|
|
||||||
[Have a deeper look into the idea of CI/CD](https://www.redhat.com/en/topics/devops/what-is-ci-cd)
|
RedHat has written an [article which explains the concept in more detail](https://www.redhat.com/en/topics/devops/what-is-ci-cd).
|
||||||
|
|
||||||
## Do you know containers?
|
## Containers at the core
|
||||||
|
|
||||||
If you are already using containers in your daily workflow, you'll for sure love Woodpecker. If not yet, you'll be amazed how easy it is to get started with [containers](https://opencontainers.org/).
|
In contrast to other CI/CD applications, Woodpecker solely focuses on using containers for executing workflows.
|
||||||
|
If you are already using containers in your daily workflow, you'll for sure love Woodpecker.
|
||||||
|
|
||||||
## Already have access to a Woodpecker instance?
|
## Convinced? Get started by deploying your own Woodpecker instance
|
||||||
|
|
||||||
Then you might want to jump directly into it and [start creating your first pipelines](../20-usage/10-intro.md).
|
Woodpecker is [pretty lightweight](../30-administration/00-getting-started.md#hardware-requirements) and can even run on a Raspberry Pi without much impact.
|
||||||
|
To set up your own Woodpecker instance, follow the [deployment guide](../30-administration/00-getting-started.md).
|
||||||
## Want to start from scratch and deploy your own Woodpecker instance?
|
|
||||||
|
|
||||||
Woodpecker is [pretty lightweight](../30-administration/00-getting-started.md#hardware-requirements) and will even run on your Raspberry Pi. You can follow the [deployment guide](../30-administration/00-getting-started.md) to set up your own Woodpecker instance.
|
|
||||||
|
|
Loading…
Reference in a new issue