Shift8 Deployment Manager for Woodpecker CI lets an administrator push a staging site to production by starting a manual Woodpecker pipeline from Shift8 \u2192 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.<\/p>\n\n
\"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.<\/p>\n\n
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.<\/p>\n\n
This plugin connects to one external service: the Woodpecker CI server whose address you enter in the settings (or define in When it is used:<\/p>\n\n Every request carries your Woodpecker API token as a bearer token in the Authorization header. The token is read only from Woodpecker is a project of the Woodpecker CI community: https:\/\/woodpecker-ci.org. This plugin is an independent integration and is not affiliated with or endorsed by that project. Terms and privacy for your server are those of whoever hosts it.<\/p>\n\n\n Define the API token in define( 'SHIFT8_WOODPECKER_TOKEN', '...' );<\/p><\/li>\n Open Shift8 \u2192 Woodpecker \u2192 Settings and enter the Woodpecker URL, repository ID, branch and (optionally) workflow. These can also be defined in No. It asks Woodpecker to start a pipeline. Everything else is up to your pipeline.<\/p><\/dd>\n 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.<\/p><\/dd>\n Users with the 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.<\/p><\/dd>\n Only for scheduled deployments, which rely on WP-Cron. A system cron running Install it on staging only. A staging-to-production database copy carries the plugin's saved settings, schedule and log with it.<\/p><\/dd>\n\n<\/dl>\n\n\nwp-config.php<\/code>). Woodpecker is open source and normally self-hosted, so the server is your own or one your organisation operates. Nothing is sent anywhere else, and the plugin does not contact Shift8 or any third party.<\/p>\n\n\n
\/api\/user<\/code>, \/api\/repos\/{id}<\/code> and the repository's workflow list.<\/li>\n\/api\/repos\/{id}\/pipelines<\/code> containing the configured branch, the optional workflow name, an empty variables object and a short message (by default \"WordPress production deployment by {display name of the WordPress user}\").<\/li>\n\/api\/repos\/{id}\/pipelines\/{number}<\/code> to read its status.<\/li>\n<\/ul>\n\nwp-config.php<\/code> and is never shown in the browser or stored in the database.<\/p>\n\n\n
\/wp-content\/plugins\/shift8-deployment-manager-for-woodpecker-ci<\/code> and activate it (on the staging site).<\/li>\nwp-config.php<\/code>. It is required and is the only way to set it:<\/p>\n\nwp-config.php<\/code> as SHIFT8_WOODPECKER_URL<\/code>, SHIFT8_WOODPECKER_REPO_ID<\/code>, SHIFT8_WOODPECKER_BRANCH<\/code> and SHIFT8_WOODPECKER_WORKFLOW<\/code>, which override the saved values.<\/p><\/li>\nmanual<\/code> event.<\/li>\nwp-cron.php<\/code> every minute and add define( 'DISABLE_WP_CRON', true );<\/code>.<\/li>\n<\/ol>\n\n\n\n
Does the plugin deploy anything itself?<\/h3><\/dt>\n
How does scheduling work?<\/h3><\/dt>\n
Who can deploy?<\/h3><\/dt>\n
manage_options<\/code> capability by default, filterable with shift8_woodpecker_deploy_capability<\/code>. Settings always require manage_options<\/code>.<\/p><\/dd>\nWhere do I see the result of a deployment?<\/h3><\/dt>\n
Does the plugin need a system cron?<\/h3><\/dt>\n
wp-cron.php<\/code> every minute with DISABLE_WP_CRON<\/code> set makes schedules reliable.<\/p><\/dd>\nDoes it work on the production site too?<\/h3><\/dt>\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n