Download the PHP package terminus-plugin-project/terminus-upstream-testing-plugin without Composer
On this page you can find all versions of the php package terminus-plugin-project/terminus-upstream-testing-plugin. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download terminus-plugin-project/terminus-upstream-testing-plugin
More information about terminus-plugin-project/terminus-upstream-testing-plugin
Files in terminus-plugin-project/terminus-upstream-testing-plugin
Package terminus-upstream-testing-plugin
Short Description Pantheon plugin to deploy upstream branch / features to specified branches before committing to master environment.
License MIT
Homepage https://github.com/terminus-plugin-project/terminus-upstream-testing-plugin
Informations about the package terminus-upstream-testing-plugin
Terminus Upstream Testing
Option | Description |
---|---|
--repo | Repository to use and pull code from. When omitted this will use the sites upstream |
--branch | Branch from the repository to use. |
--env | Environment to use for testing |
--copy | Environment to copy database and files from |
--teardown | Tear down the environment before applying any changes |
--rebuild | Rebuild the database and files |
--username | Change user 1's username |
--password | Change user 1's password |
--notify | Run a script after the process has been completed |
--skipautocommit | Skip files that were not autocommitted |
Slack Integration
Integration with Slack using incoming webhooks
Option | Description |
---|---|
--slack_url | Slack URL to post to |
--slack_channel | Slack Channel to post message to. Should be prefixed with # |
--slack_message | Message to post to slack. Following variables are available {env} {site_id} {site_name} {url} |
--slack_username | Username to push through as slack message |
--slack_icon | Icon to use for slack message |
Examples
Default Running
The following will apply all updates from the master branch of the site's upstream to the upstream multi-dev
Separate Upstream
If the --repo
argument is omitted the plugin with default to the site's upstream git repository. Otherwise a git
url could be used to pull from a completely different repo.
Specifying the environment to copy database and files
The --copy
argument will allow you to specify the environment to bring the database and files from. This environment
must already be initialized. Otherwise, the live/test/dev environments will be used respectively
Upstream Branch
To specify a particular branch that code would live in the --branch
argument could be used. That branch will need to exist
within the upstream or --repo
repository.
Rebuild
To rebuild or copy the database and files from a particular environment use the --rebuild
flag as it will dictate
that you want to completely pull new content. In conjunction with --copy
these could be helpful in automation if
wanting to specify the environment that data should be rebuilt from.
Reset User 1 Username and Password
The following will reset the username and password of the user 1 account. This is helpful if you would like a standard account username and password for any other sort of automated testing like behat. Each argument may be used independently and do not need to be combined.
Reset Username
Reset Password
Slack Notification
There is an ability to have a slack message sent to a particular channel to notify when an environment has been updated. This is particularly useful if and when you are using this plugin for any sort of Continuous Integration work.
Installation
For help installing, see Manage Plugins
Install Notes
Occasionally you may get this issue:
The way to solve this will be to go to your terminus project and run composer update
. If you globally require it you
will need to go directly into terminus it's self as the lock file within the terminus may contain an older version of guzzle/psr7.
OS X & Linux Fix
The following will only work assuming the following:
- terminus was installed with composer and not with the phar
- the terminus executable file is located within vendor/bin folder
Help
Run terminus list site:upstream:test
for a complete list of available commands. Use terminus help <command>
to get help on one command.