Merge pull request circleci#1929 from circleci/rohara/updates

Test splitting is now available in Workflows

Author: michelle-luna

jekyll/_cci2/faq.md

@@ -16,11 +16,11 @@ order: 1
 
 - **Cloud** - CircleCI manages the setup, infrastructure, security and maintenance of your services. You get instant access to new feature releases and automatic upgrades, alleviating the need for manual work on an internal system.
 
-- **Server** - You install and manage CircleCI, through a service like AWS, behind a firewall that your team sets up and maintains according to your datacenter policy. You have full administrative control for complete customization and manage  upgrades as new versions are released.
+- **Server** - You install and manage CircleCI, through a service like AWS, behind a firewall that your team sets up and maintains according to your datacenter policy. You have full administrative control for complete customization and manage upgrades as new versions are released.
 
 ## Why did you change the name from CircleCI Enterprise? 
 
-The term Enterprise was used to refer to the behind-the-firewall option. However, this nomenclature was confusing for  customers and for CircleCI employees. 
+The term Enterprise was used to refer to the behind-the-firewall option. However, this nomenclature was confusing for customers and for CircleCI employees. 
 
 CircleCI is one product that can be accessed through our cloud service, installed behind your firewall, or in a hybrid approach, depending on your needs.
 
@@ -168,7 +168,7 @@ Not yet, but we are working on that functionality.
 Not yet, but we are working on that functionality.
 
 ### Can I use `store_test_results` with Workflows?
-You can use `store_test_results` in order to populate your builds' Test Summary section with your test results information, however [timing-based test-splitting]({{ site.baseurl }}/2.0/parallelism-faster-jobs/#splitting-patterns) will not work. This is next up on our roadmap to fix. Test timings data is available for 2.0 but not with Workflows.
+You can use `store_test_results` in order to populate your builds' Test Summary section with your test results information and for [timing-based test-splitting]({{ site.baseurl }}/2.0/parallelism-faster-jobs/#splitting-patterns). Test timings data is available for 2.0 with Workflows, using data from a job with the same name going back 50 builds.
 
 ### Can I use Workflows with CircleCI 1.0?
 
@@ -195,7 +195,7 @@ No.
 We do not support fork PR’s yet.
 
 ### Can workflows be scheduled to run at a specific time of day?
-Yes, for the CircleCI hosted application. For example, to run a workflow at 4 PM use `"0 16 * * *"` as the value for the `cron:` key. Times are interpreted in the UTC time zone. Next on the roadmap is to enable scheduled workflows in an  installable CircleCI release.
+Yes, for the CircleCI hosted application. For example, to run a workflow at 4 PM use `"0 16 * * *"` as the value for the `cron:` key. Times are interpreted in the UTC time zone. Next on the roadmap is to enable scheduled workflows in an installable CircleCI release.
 
 ### What time zone is used for schedules?
 Coordinated Universal Time (UTC) is the time zone in which schedules are interpreted.

jekyll/_cci2/parallelism-faster-jobs.md

@@ -69,8 +69,6 @@ When the items are filepaths, the `filesize` option will weight the split by fil
 
 The `timings` split type uses historical timing data to weight the split. CircleCI automatically makes timing data from previous successful runs available inside your container in a default location so the CLI tool can discover them (`$CIRCLE_INTERNAL_TASK_DATA/circle-test-results`). Make sure you are using the [`store_test_results` key]({{ site.baseurl }}/2.0/configuration-reference/#store_test_results) to save your test timing data, otherwise there will not be any historical timing data available.
 
-***Note:** timing-based test splitting is not currently compatible with Workflows.*
-
 When splitting by `timings`, the tool will assume it’s splitting filenames. If you’re splitting classnames, you’ll need to specify that with the `--timings-type` flag, as in the following examples:
 
 `circleci tests glob "**/*.go" | circleci tests split --split-by=timings --timings-type=filename`