-
operating procedure:
Using Subversion | Plugin Developer Handbook | WordPress Developer Resources
-
Reference materials:
Plugin Readmes | Plugin Developer Handbook | WordPress Developer Resources
The Plugins directory and readme.txt files – Make WordPress Plugins
This is deployment job for WordPress Plugin from public Git repository to SubVersion on WordPress.org.
- Tagging revision on Git is done before deploy into WordPress.org
- Tag name of revision on source Git repository to deploy is the same as version number of plugin’s main PHP file on tagged revision of source Git repository
- Deploying old version than latest version
- Deploying Assets (Even if Git repository includes assets, this project will deploy the revision content as it is under trunk and tags of SubVersion repository on WordPress.org.)
The process executes rsync from Git working tree to SubVersion working tree with .rsync-filter
.
rsync will read default .rsync-filter file.
If .rsync-filter
file is exist on the root of Git working tree, rsync will read it. The most primitive how to write it is to list up files and directories you want to exclude. For more details, following contents will be helpful.
This image is depend on futureys/ansible-workspace-deploy-wordpress-plugin. It will be easier to understand if you look at the Docker Compose files in the GitHub code.
https://github.com/yukihiko-shinoda/dockerfile-deploy-wordpress-plugin
Clone or download project files from GitHub.
git clone https://github.com/yukihiko-shinoda/dockerfile-deploy-wordpress-plugin.git
If you prefer, there is template to set environment variables, Copy .env.dist to .env, then open by editor and edit variable definitions.
ref: Environment variables in Compose | Docker Documentation
By running SubVersion container for mock in local. Enter following command:
docker-compose -f docker-compose.yml -f docker-compose.staging.yml up -d && docker logs -f deploy
When process succeed to finish, check result by checking out from mock:
svn checkout svn://(your-docker-host-name)/project-in-svn
cd project-in-svn
svn log HEAD:1
Once you have checked that it works as expected, shutdown containers once.
docker-compose -f docker-compose.yml -f docker-compose.staging.yml down
docker-compose -f docker-compose.yml up
Check on WordPress.org that it has been deployed successfully.
WordPress Plugins | WordPress.org
After checking that the deployment was succeed, shutdown the container.
docker-compose -f docker-compose.yml down
The source Git repository URL for public repository.
Only either of GIT_REPOSITORY_URL
or GIT_PATH_CHECKED_OUT
can define.
The source GIT_PATH_CHECKED_OUT.
This is intended to mount the directory where checked out the private repository.
Only either of GIT_REPOSITORY_URL
or GIT_PATH_CHECKED_OUT
can define.
The destination SubVersion repository URL.
Ex: https://plugins.svn.wordpress.org/????
User name of SubVersion on WordPress.org.
Your account for SVN will be the same username (not the email) of the account you used when you submitted the plugin. This is the user ID you use for the WordPress forums as well.
User password of SubVersion on WordPress.org.
If you need to reset your password, go to login.wordpress.org
The tag name of revision on source Git repository to deploy. This string also has to be the same as the version number of plugin’s main PHP file on tagged revision of source Git repository.
By default, this image hide logs about steps using secret for example when commit.
When debug, you can check log by setting this true
.