[incubator-mxnet] branch KellenSunderland-patch-1-1 created (now f9e7243)

[ke...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kellen pushed a change to branch KellenSunderland-patch-1-1
in repository https://gitbox.apache.org/repos/asf/incubator-mxnet.git.


      at f9e7243  Fix formatting and typos in CD README.md

This branch includes the following new commits:

     new f9e7243  Fix formatting and typos in CD README.md

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.

[incubator-mxnet] 01/01: Fix formatting and typos in CD README.md

[ke...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kellen pushed a commit to branch KellenSunderland-patch-1-1
in repository https://gitbox.apache.org/repos/asf/incubator-mxnet.git

commit f9e7243cb4e33a6bedd7e6399a3a02e44c60dd4a
Author: Kellen Sunderland <ke...@gmail.com>
AuthorDate: Fri Nov 1 12:50:49 2019 -0700

    Fix formatting and typos in CD README.md
---
 cd/README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/cd/README.md b/cd/README.md
index a8e3fb7..a3dc038 100644
--- a/cd/README.md
+++ b/cd/README.md
@@ -46,12 +46,12 @@ Currently, 10 variants are supported:
 
 ### CD Pipeline Job
 
-The [CD pipeline job](Jenkinsfile_cd_pipeline) take three parameters:
+The [CD pipeline job](Jenkinsfile_cd_pipeline) take two parameters:
 
  * **RELEASE_BUILD**: Flags the run as a *release build*. The underlying jobs can then use this environment variable to disambiguate between nightly and release builds. Defaults to *false*.
  * **MXNET_VARIANTS**: A comma separated list of variants to build. Defaults to *all* variants.
 
-This job defines and executes the CD pipeline. For example, first publish the MXNet library, then, in parallel, execute the python and maven releases. Every step of the pipeline executes a trigger for a release job](Jenkinsfile_release_job).
+This job defines and executes the CD pipeline. For example, first publish the MXNet library, then, in parallel, execute the python and maven releases. Every step of the pipeline executes a trigger for a [release job](Jenkinsfile_release_job).
 
 ### Release Job
 
@@ -195,4 +195,4 @@ def test(mxnet_variant) {
 
 Examples:
 
-Both the [statically linked libmxnet](mxnet_lib/static/Jenkins_pipeline.groovy) and [dynamically linked libmxnet](mxnet_lib/dynamic/Jenkins_pipeline.groovy) pipelines have long running compilation and testing stages that **do not** require specialized/expensive hardware (e.g. GPUs). Therefore, as mush as possible, it is important to run each stage in on its own node, and design the pipeline to spend the least amount of time possible on expensive hardware. E.g. for GPU builds, only run GP [...]
\ No newline at end of file
+Both the [statically linked libmxnet](mxnet_lib/static/Jenkins_pipeline.groovy) and [dynamically linked libmxnet](mxnet_lib/dynamic/Jenkins_pipeline.groovy) pipelines have long running compilation and testing stages that **do not** require specialized/expensive hardware (e.g. GPUs). Therefore, as much as possible, it is important to run each stage in on its own node, and design the pipeline to spend the least amount of time possible on expensive hardware. E.g. for GPU builds, only run GP [...]