You must install the "GitHub" extension and the "Windows SDK" extension to use this template; this is usually done from Administration > Extensions.
This Inedo-developed template provides you with quick access to recommended settings for an application using CI/CD with WordPress. To select a different settings template, go to Advanced Settings.
| Setting | Description | |
|---|---|---|
| GitHub Repository | A secure resource named "GitHub" must be configured at the application or system level to connects to a repository hosted on GitHub.com or a GitHub Enterprise instance. | Secure Resources |
| Notification Email Address | $NotifyUserEmail = 91f2be32.inedo.com@amer.teams.ms | Variables |
| Release Pipeline | The "Release" pipeline is used to get source by configured branch, build and test artifacts, deploy to a series of targets on-demand or automatically once approvals are received, and create a tag in the repository. | Pipelines |
| Variable Prompts | A release template named "Default" must be created to prompt for additional configuration such as a $Branch when creating BuildMaster builds or releases. | Release Templates |
| Build script | The "Build" OtterScript script is used to get source code by branch from GitHub and create artifacts. | Scripts |
| ManuallyDeploy script | The "ManuallyDeploy" OtterScript script is used to instruct a user to deploy artifacts to the Environment configured in the pipeline. | Scripts |
| Repackage script | The "Repackage" OtterScript script is used to repackage the theme or plugin artifact for proper semantic versioning. | Scripts |
| Tag script | The "Tag" OtterScript script is used to add a tag to the commit. | Scripts |
| Build Trigger | A build trigger named "GitHub" must be created to automatically trigger a build in the application when a commit gets pushed to a GitHub repository. | Triggers |
| Issue Source | This issue source will be used to synchronize issues associated with the release, either from GitHub or another source. | Issues |