-
Notifications
You must be signed in to change notification settings - Fork 126
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
Test baseurl presence and fix breaks #66
Conversation
R: @davorbonaci |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): Jenkins built the site at commit id 3828435 with Jekyll and staged it here. Happy reviewing. Note that any previous site has been deleted. This staged site will be automatically deleted after its TTL expires. Push any commit to the pull request branch or re-trigger the build to get it staged again. |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): Jenkins built the site at commit id dc17e3a with Jekyll and staged it here. Happy reviewing. Note that any previous site has been deleted. This staged site will be automatically deleted after its TTL expires. Push any commit to the pull request branch or re-trigger the build to get it staged again. |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): Jenkins built the site at commit id 106e357 with Jekyll and staged it here. Happy reviewing. Note that any previous site has been deleted. This staged site will be automatically deleted after its TTL expires. Push any commit to the pull request branch or re-trigger the build to get it staged again. |
efc92c8
to
e3eb891
Compare
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): Jenkins built the site at commit id efc92c8 with Jekyll and staged it here. Happy reviewing. Note that any previous site has been deleted. This staged site will be automatically deleted after its TTL expires. Push any commit to the pull request branch or re-trigger the build to get it staged again. |
LGTM. Merged. |
Refer to this link for build results (access rights to CI server needed): Jenkins built the site at commit id e3eb891 with Jekyll and staged it here. Happy reviewing. Note that any previous site has been deleted. This staged site will be automatically deleted after its TTL expires. Push any commit to the pull request branch or re-trigger the build to get it staged again. |
* _config_test.yml was supposed to generate into the `.testcontent` directory, per the original PR apache#66, but didn't. I fixed this. * Fixed README.md to not say that `rake test` will regenerate content, and rephrased it a bit. * Added proper `git remote` address for the website in contribution guide for committers.
* _config_test.yml was supposed to generate into the `.testcontent` directory, per the original PR #66, but didn't. I fixed this. * Fixed README.md to not say that `rake test` will regenerate content, and rephrased it a bit. * Added proper `git remote` address for the website in contribution guide for committers.
* _config_test.yml was supposed to generate into the `.testcontent` directory, per the original PR apache/beam-site#66, but didn't. I fixed this. * Fixed README.md to not say that `rake test` will regenerate content, and rephrased it a bit. * Added proper `git remote` address for the website in contribution guide for committers.
* _config_test.yml was supposed to generate into the `.testcontent` directory, per the original PR apache/beam-site#66, but didn't. I fixed this. * Fixed README.md to not say that `rake test` will regenerate content, and rephrased it a bit. * Added proper `git remote` address for the website in contribution guide for committers.
* _config_test.yml was supposed to generate into the `.testcontent` directory, per the original PR apache/beam-site#66, but didn't. I fixed this. * Fixed README.md to not say that `rake test` will regenerate content, and rephrased it a bit. * Added proper `git remote` address for the website in contribution guide for committers.
Two commits:
The tests use a separate config to set test-specific properties. The
site.url
configuration specifically does not appear settable from the Jekyll CLI. Unfortunately this means that there is one property shared between config and test (.testcontent
)Also adds
content
and.testcontent
to the excludes list so that the builds of each do not include the other.