self-hosted/woodpecker
1
0
Fork 0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2024-11-30 08:06:52 +02:00
Code Issues Releases Activity

added Tag to docs

Browse Source
This commit is contained in:
Brad Rydzewski 2015-10-27 13:21:01 -07:00
parent bd59e67e3d
commit 460c62c704
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/build/env.md vendored
View File

@ -10,6 +10,7 @@ Drone injects the following namespaced environment variables into every build:
* `DRONE_BUILD_NUMBER` - build number for the current build
* `DRONE_PULL_REQUEST` - pull request number fo the current build
* `DRONE_JOB_NUMBER` - job number for the current build
* `DRONE_TAG` - tag name for the current build
Drone also injects `CI_` prefixed variables for compatibility with other systems:
@ -23,6 +24,7 @@ Drone also injects `CI_` prefixed variables for compatibility with other systems
* `CI_JOB_NUMBER` - job number for the current build
* `CI_BUILD_DIR` - working directory for the current build
* `CI_BUILD_URL` - url for the current build
* `CI_TAG` - tag name for the current build
## Injecting
@ -32,6 +34,7 @@ A subset of variables may be injected directly into the Yaml at runtime using th
* `$$COMMIT` git sha for the current build, `--short` format
* `$$BRANCH` git branch for the current build
* `$$REPO` repository full name (in `owner/name` format)
* `$$TAG` tag name
This is useful when you need to dynamically configure your plugin based on the current build. For example, we can alter an artifact name to include the branch:

6
docs/build/services.md vendored
View File

@ -22,9 +22,11 @@ compose:
- POSTGRES_PASSWORD=mysecretpassword
```
## Service linking
## Service networking
Service containers share the same network as the build container (using `--net=<container>`). This means that you can access your service container using `localhost` or `127.0.0.1`.
Service containers are available at the `localhost` or `127.0.0.1` address.
Drone deviates from the default Docker compose networking model to mirror a traditional development environment, where services are typically accessed at `localhost` or `127.0.0.1`. To achieve this, we create a per-build network where all containers share the same network.
## Service options