Releases: woodpecker-ci/woodpecker
Global configuration
This release features 5 PRs from @imduffy15 easing the configuration burden of Woodpecker.
- #115 Upgrading dependencies. Carries some risk, so if you see issues (we clearly don't) let us know
- #116 Allow the agent to connect to a secure grpc endpoint: now you can put your server behind a proxy and TLS, the agent will validate the TLS cert
- #118 Add support for a global env from a server flag: this is a big one. If you add the same vars to all your pipelines, this will help you out: https://woodpecker.laszlo.cloud/environment-variables/#global-environment-variables
#119 Add whitelist for syncable owners: if you are annoyed that your private repos show up in your company Woodpecker instance: https://woodpecker.laszlo.cloud/server-setup/#filtering-repositories
#120 Add global registry from docker config file on woodpecker server: another big one. If you need a private registry in all your repos, use a global configuration: https://woodpecker.laszlo.cloud/pipeline/#global-registry-setting
Thanks again @imduffy15 🙏 👏
Grab the images here:
laszlocloud/woodpecker-agent:v0.10.0
laszlocloud/woodpecker-server:v0.10.0
Bugfix release
Fixing #103
Technical release
This release contains technical changes and updates to libraries which carry security fixes.
Use the images from Docker Hub
laszlocloud/woodpecker-agent:v0.9.0
laszlocloud/woodpecker-server:v0.9.0
Source and target branch variables for PRs
This release introduces two new env vars: DRONE_SOURCE_BRANCH and DRONE_TARGET_BRANCH. This solves #77
The release also contains a large technical change, we moved to Go modules to version dependencies. This makes the project future compatible. #4
Use the images from Docker Hub
laszlocloud/woodpecker-agent:v0.8.106
laszlocloud/woodpecker-server:v0.8.106
Cancel pending builds
Bugfix release
Bugfix release
Link to line
New feature in this release: line numbers are clickable on the log output and you can link to errors directly. laszlocph/woodpecker-ui#1
#49 A bug was fixed where new repos could not be activated since v.0.8.97
Multi-pipeline builds: waiting state in queue; Bitbucket fix
-
With multi-pipeline introduced, the pending queue state got ambiguous. #48 meant to fix it by splitting it into waiting (on deps) and pending queue states.
-
Bitbucket has a deprecated API endpoint. #34 is fixing that
Use the images from Docker Hub
laszlocloud/drone-oss-08-agent:0.8.101
laszlocloud/drone-oss-08-server:0.8.101
Job build times exposed as metric
With #41 you can chart build times based on branch/repo/status, etc.
Use the images from Docker Hub
laszlocloud/drone-oss-08-agent:0.8.100
laszlocloud/drone-oss-08-server:0.8.100