mirror of
https://github.com/woodpecker-ci/woodpecker.git
synced 2024-12-30 12:20:33 +00:00
Add version notes to docs (#1592)
This commit is contained in:
parent
0940223472
commit
c05b51fb54
9 changed files with 55 additions and 5 deletions
|
@ -86,3 +86,8 @@ pipeline:
|
||||||
```
|
```
|
||||||
|
|
||||||
See [plugin docs](./20-usage/51-plugins/10-plugins.md).
|
See [plugin docs](./20-usage/51-plugins/10-plugins.md).
|
||||||
|
|
||||||
|
## Continue reading
|
||||||
|
|
||||||
|
- [Create a Woodpecker pipeline for your repository](./20-usage/10-intro.md)
|
||||||
|
- [Setup your own Woodpecker instance](./30-administration/00-setup.md)
|
||||||
|
|
|
@ -11,6 +11,12 @@ A Woodpecker deployment consists of two parts:
|
||||||
>
|
>
|
||||||
> You can add more agents to increase the number of parallel steps or set the agent's `WOODPECKER_MAX_WORKFLOWS=1` environment variable to increase the number of parallel workflows for that agent.
|
> You can add more agents to increase the number of parallel steps or set the agent's `WOODPECKER_MAX_WORKFLOWS=1` environment variable to increase the number of parallel workflows for that agent.
|
||||||
|
|
||||||
|
## Which version of Woodpecker should I use?
|
||||||
|
|
||||||
|
Woodpecker is having two different kinds of releases: **stable** and **next**.
|
||||||
|
|
||||||
|
To find out more about the differences between the two releases, please read the [FAQ](/faq).
|
||||||
|
|
||||||
## Installation
|
## Installation
|
||||||
|
|
||||||
You can install Woodpecker on multiple ways:
|
You can install Woodpecker on multiple ways:
|
||||||
|
|
|
@ -1,5 +1,11 @@
|
||||||
# Downloads
|
# Downloads
|
||||||
|
|
||||||
|
## Which version of Woodpecker should I use?
|
||||||
|
|
||||||
|
Woodpecker is having two different kinds of releases: **stable** and **next**.
|
||||||
|
|
||||||
|
To find out more about the differences between the two releases, please read the [FAQ](/faq).
|
||||||
|
|
||||||
## Binaries & DEB, RPM
|
## Binaries & DEB, RPM
|
||||||
|
|
||||||
[Latest release](https://github.com/woodpecker-ci/woodpecker/releases/latest)
|
[Latest release](https://github.com/woodpecker-ci/woodpecker/releases/latest)
|
||||||
|
|
|
@ -2,7 +2,7 @@
|
||||||
|
|
||||||
Some versions need some changes to the server configuration or the pipeline configuration files.
|
Some versions need some changes to the server configuration or the pipeline configuration files.
|
||||||
|
|
||||||
## 1.0.0
|
## 1.0.0 (next)
|
||||||
|
|
||||||
- The signature used to verify extensions calls (like those used for the [config-extension](./30-administration/100-external-configuration-api.md)) done by the Woodpecker server switched from using a shared-secret HMac to an ed25519 key-pair. Read more about it at the [config-extensions](./30-administration/100-external-configuration-api.md) documentation.
|
- The signature used to verify extensions calls (like those used for the [config-extension](./30-administration/100-external-configuration-api.md)) done by the Woodpecker server switched from using a shared-secret HMac to an ed25519 key-pair. Read more about it at the [config-extensions](./30-administration/100-external-configuration-api.md) documentation.
|
||||||
- Refactored support of old agent filter labels and expression. Learn how to use the new [filter](./20-usage/20-pipeline-syntax.md#labels)
|
- Refactored support of old agent filter labels and expression. Learn how to use the new [filter](./20-usage/20-pipeline-syntax.md#labels)
|
||||||
|
|
|
@ -26,7 +26,7 @@ module.exports = {
|
||||||
items: [
|
items: [
|
||||||
{
|
{
|
||||||
type: 'doc',
|
type: 'doc',
|
||||||
docId: 'usage/intro',
|
docId: 'intro',
|
||||||
activeBaseRegex: 'docs/(?!migrations|awesome)',
|
activeBaseRegex: 'docs/(?!migrations|awesome)',
|
||||||
position: 'left',
|
position: 'left',
|
||||||
label: 'Docs',
|
label: 'Docs',
|
||||||
|
@ -76,6 +76,10 @@ module.exports = {
|
||||||
{
|
{
|
||||||
title: 'Docs',
|
title: 'Docs',
|
||||||
items: [
|
items: [
|
||||||
|
{
|
||||||
|
label: 'Introduction',
|
||||||
|
to: '/docs/intro',
|
||||||
|
},
|
||||||
{
|
{
|
||||||
label: 'Usage',
|
label: 'Usage',
|
||||||
to: '/docs/usage/intro',
|
to: '/docs/usage/intro',
|
||||||
|
|
|
@ -11,6 +11,18 @@ Apart from Woodpecker staying free and OpenSource forever, the growing community
|
||||||
|
|
||||||
The Drone CI license was changed after the 0.8 release from Apache 2 to a proprietary license. Woodpecker is based on this latest freely available version.
|
The Drone CI license was changed after the 0.8 release from Apache 2 to a proprietary license. Woodpecker is based on this latest freely available version.
|
||||||
|
|
||||||
|
## Which version of Woodpecker should I use?
|
||||||
|
|
||||||
|
Woodpecker is having two different kinds of releases: **stable** and **next**.
|
||||||
|
|
||||||
|
The **stable** releases (currently version 0.15) is a long-term supported (LTS) stable version. The stable releases are only getting bugfixes.
|
||||||
|
|
||||||
|
The **next** release contains all bugfixes and features from `master`. Normally it should be pretty stable, but as its frequently updated, it might contain some bugs from time to time.
|
||||||
|
|
||||||
|
If you want all (new) features of Woodpecker and are willing to accept some possible bugs from time to time, you should use the next release otherwise use the stable release.
|
||||||
|
|
||||||
|
You can find download links for the different releases in the [download section](/docs/downloads).
|
||||||
|
|
||||||
## How to debug clone issues:
|
## How to debug clone issues:
|
||||||
|
|
||||||
(And what to do with an error message like `fatal: could not read Username for 'https://<url>': No such device or address`)
|
(And what to do with an error message like `fatal: could not read Username for 'https://<url>': No such device or address`)
|
||||||
|
@ -45,7 +57,7 @@ pipeline:
|
||||||
Get the container id using `docker ps` and copy the id from the first column. Enter the container with: `docker exec -it 1234asdf bash` (replace `1234asdf` with the docker id). Then try to clone the git repository with the commands from the failing pipeline:
|
Get the container id using `docker ps` and copy the id from the first column. Enter the container with: `docker exec -it 1234asdf bash` (replace `1234asdf` with the docker id). Then try to clone the git repository with the commands from the failing pipeline:
|
||||||
```bash
|
```bash
|
||||||
$ git init
|
$ git init
|
||||||
$ git remote add origin https://git.example.com/username/repo.git
|
$ git remote add origin https://git.example.com/username/repo.git
|
||||||
$ git fetch --no-tags origin +refs/heads/branch:
|
$ git fetch --no-tags origin +refs/heads/branch:
|
||||||
```
|
```
|
||||||
(replace the url AND the branch with the correct values, use your username and password as log in values)
|
(replace the url AND the branch with the correct values, use your username and password as log in values)
|
||||||
|
|
|
@ -27,7 +27,7 @@ pipeline:
|
||||||
|
|
||||||
- Define any Docker image as context
|
- Define any Docker image as context
|
||||||
- either use your own and install the needed tools in custom Docker images, or
|
- either use your own and install the needed tools in custom Docker images, or
|
||||||
- search [Docker Hub](https://hub.docker.com/search?type=image) for images that are already tailored for your needs)
|
- search [Docker Hub](https://hub.docker.com/search?type=image) for images that are already tailored for your needs)
|
||||||
- List the commands that should be executed in your container, in order to build or test your application
|
- List the commands that should be executed in your container, in order to build or test your application
|
||||||
|
|
||||||
```diff
|
```diff
|
||||||
|
@ -85,3 +85,8 @@ pipeline:
|
||||||
```
|
```
|
||||||
|
|
||||||
See [plugin docs](./20-usage/51-plugins/10-plugins.md).
|
See [plugin docs](./20-usage/51-plugins/10-plugins.md).
|
||||||
|
|
||||||
|
## Continue reading
|
||||||
|
|
||||||
|
- [Create a Woodpecker pipeline for your repository](./20-usage/10-intro.md)
|
||||||
|
- [Setup your own Woodpecker instance](./30-administration/00-setup.md)
|
||||||
|
|
|
@ -10,6 +10,12 @@ A Woodpecker deployment consists of two parts:
|
||||||
>
|
>
|
||||||
> You can add more agents to increase the number of parallel builds or set the agent's `WOODPECKER_MAX_PROCS=1` environment variable to increase the number of parallel builds for that agent.
|
> You can add more agents to increase the number of parallel builds or set the agent's `WOODPECKER_MAX_PROCS=1` environment variable to increase the number of parallel builds for that agent.
|
||||||
|
|
||||||
|
## Which version of Woodpecker should I use?
|
||||||
|
|
||||||
|
Woodpecker is having two different kinds of releases: **stable** and **next**.
|
||||||
|
|
||||||
|
To find out more about the differences between the two releases, please read the [FAQ](/faq).
|
||||||
|
|
||||||
## Installation
|
## Installation
|
||||||
|
|
||||||
You can install Woodpecker on multiple ways:
|
You can install Woodpecker on multiple ways:
|
||||||
|
|
|
@ -1,5 +1,11 @@
|
||||||
# Downloads
|
# Downloads
|
||||||
|
|
||||||
|
## Which version of Woodpecker should I use?
|
||||||
|
|
||||||
|
Woodpecker is having two different kinds of releases: **stable** and **next**.
|
||||||
|
|
||||||
|
To find out more about the differences between the two releases, please read the [FAQ](/faq).
|
||||||
|
|
||||||
## Binaries & DEB, RPM
|
## Binaries & DEB, RPM
|
||||||
|
|
||||||
[Latest release](https://github.com/woodpecker-ci/woodpecker/releases/latest)
|
[Latest release](https://github.com/woodpecker-ci/woodpecker/releases/latest)
|
||||||
|
|
Loading…
Reference in a new issue