Linux 软件免费装

在这里免费安装WordPress以及其他软件

Banner图

Shift8 Deployment Manager for Woodpecker CI

开发者 shift8
更新时间 2026年11月12日 23:19
捐献地址: 去捐款
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv3
版权网址: 版权信息

标签

push deployment woodpecker ci shift8

下载

1.1.0

详情介绍:

Shift8 Deployment Manager for Woodpecker CI lets an administrator push a staging site to production by starting a manual Woodpecker pipeline from Shift8 → Woodpecker, either immediately or at a scheduled date and time. An activity log records the WordPress user, the date/time, and how each deployment ended. "Woodpecker CI" is the name of a third-party open source project. This plugin is an independent integration made by Shift8 and is not affiliated with, endorsed by or sponsored by the Woodpecker CI project. The plugin only triggers and observes the pipeline; the deployment itself is performed by your Woodpecker workflow. The API token stays on the server, is never stored in the database and is never sent to the browser. End users cannot cancel a running deployment.

安装:

  1. Upload the plugin to /wp-content/plugins/shift8-deployment-manager-for-woodpecker-ci and activate it (on the staging site).
  2. Define the API token in wp-config.php. It is required and is the only way to set it:
define( 'SHIFT8_WOODPECKER_TOKEN', '...' );
  1. Open Shift8 → Woodpecker → Settings and enter the Woodpecker URL, repository ID, branch and (optionally) workflow. These can also be defined in wp-config.php as SHIFT8_WOODPECKER_URL, SHIFT8_WOODPECKER_REPO_ID, SHIFT8_WOODPECKER_BRANCH and SHIFT8_WOODPECKER_WORKFLOW, which override the saved values.
  2. On the Deployment tab click "Test Woodpecker Connection".
  3. Make sure the Woodpecker workflow accepts the manual event.
  4. For scheduled deployments use a system cron to run wp-cron.php every minute and add define( 'DISABLE_WP_CRON', true );.

常见问题:

Does the plugin deploy anything itself?

No. It asks Woodpecker to start a pipeline. Everything else is up to your pipeline.

How does scheduling work?

Woodpecker cannot delay a pipeline, so the schedule is kept in WordPress (WP-Cron) and the pipeline is started when the time arrives, in the site timezone. One schedule can be pending at a time; a schedule that is more than 30 minutes late is skipped and logged instead of running.

Who can deploy?

Users with the manage_options capability by default, filterable with shift8_woodpecker_deploy_capability. Settings always require manage_options.

Where do I see the result of a deployment?

In the activity log on the Deployment tab: a "Started deployment" line and, when the pipeline stops, a "Deployment finished" line with the final status. It is recorded when the page next checks the pipeline, so it may appear at your next visit if nobody was watching.

Does the plugin need a system cron?

Only for scheduled deployments, which rely on WP-Cron. A system cron running wp-cron.php every minute with DISABLE_WP_CRON set makes schedules reliable.

Does it work on the production site too?

Install it on staging only. A staging-to-production database copy carries the plugin's saved settings, schedule and log with it.

更新日志:

1.1.0 1.0.0