-
Notifications
You must be signed in to change notification settings - Fork 229
Move information about Zinc and running individual tests to main website #33
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
Conversation
This is useful and I often forget how to do it. I learned some new tricks when @squito gave @jinxing64 some tips on how to do this, so I thought it was worth adding this to the website.
|
I didn't copy this from the wiki because it had been added earlier to the docs at http://spark.apache.org/docs/latest/building-spark.html#running-tests That doesn't mean it's the best place for this piece of info. If you'd like to add this then just also make a PR to remove similar info in the release-specific docs (perhaps with a pointer to this new info) |
|
Ah thanks for the pointer to that -- I hadn't seen that page. It looks like the Building Spark page has some stuff that's really only for developers (mainly the Zinc info and how to run individual tests). What do you think about me moving all of that (so the Zinc info in addition to the individual tests info) to the developers page, and then adding a link on the building spark page to the developer page for more info on running tests? If I do that, do you think I should move all of the "testing" info to the developer page? I'm inclined to think no because I can imagine non-developers wanting to run all of the tests (e.g., to verify a release), but figured you'd have better visibility into this, so wanted to check. |
|
Feel free to move whatever you think should be moved. When I merged the wiki into the main site it was a rough cut at fitting bits together that weren't necessarily in the best place, so more editing is certainly welcome. I can help review and merge this and/or the complementary change to the main docs whenever you're ready. |
|
@kayousterhout are you interested in updating the main project docs too? we can commit both changes. |
|
Yup sorry for the delay on this -- was out on vacation. I'll do both today. |
This commit moves developer-specific information from the release- specific documentation in this repo to the developer tools page on the main Spark website. This commit relies on this PR on the Spark website: apache/spark-website#33.
|
Ok I updated this to add the Zinc stuff, and also added a corresponding PR in the main Spark repo. We should merge this one first so the links I added in the Spark release-specific docs work. |
|
@kayousterhout this is merged now though it won't auto-close because I rebased/squashed |
|
Cool thanks for the help with this Sean |
This commit moves developer-specific information from the release- specific documentation in this repo to the developer tools page on the main Spark website. This commit relies on this PR on the Spark website: apache/spark-website#33. srowen Author: Kay Ousterhout <[email protected]> Closes apache#17018 from kayousterhout/SPARK-19684.
This moves the information about how to run individual tests and use Zinc to the developer tools page, from the release-specific docs. I've found the developer tools page is more Google-able, this info is useful primarily for developers, and it doesn't change significantly between releases. There's a companion PR in the main Spark repo to remove this from the release-specific docs: apache/spark#17018