-
Notifications
You must be signed in to change notification settings - Fork 396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add multisite support for setup tasks #1005
Add multisite support for setup tasks #1005
Conversation
phing/tasks/properties.xml
Outdated
<available file="${blt.config-dirs.sites}"/> | ||
<then> | ||
<!-- Build the site list from *.yml files in the blt/sites directory. --> | ||
<exec dir="${blt.config-dirs.sites}" command="ls *.yml | tr -d '\n' | sed s/\.yml/,/g" outputProperty="multisite.names"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we may need a more blt-specific pattern, since this could pick up unrelated yml files. Perhaps project.site.yml.
Thanks for breaking this into something smaller. I think that the last step before merging is to ensure that there's some type of test coverage. Perhaps we can add a default project.site.yml to a directory during BLT's .travis.yml execution and assert that it has been parsed and generated the expected settings files. |
👍 |
@grasmash - I've put some additional testing in place here. I wasn't entirely sure how to go about testing that site properties are being correctly parsed, but take a look at |
Addresses aspects of #799.
Changes proposed: