aaronmarkham commented on a change in pull request #13914: Static build instruction for MXNet in general URL: https://github.com/apache/incubator-mxnet/pull/13914#discussion_r248899088
########## File path: ci/publish/README.md ########## @@ -0,0 +1,33 @@ +# MXNet Publish Settings + +This folder contains the configuration of restricted node on Jenkins for the publish. It also contains a folder called `scala` that contains everything required for scala publish. In this `README`, we would bring a brief walkthrough of the Jenkins configuration as well as the usages of the scala deployment files. + +## Jenkins +Currently, Jenkins contains three build stages, namely `Build Packages`, `Test Packages` and `Deploy Packages`. During the `build package` stages, all dependencies will be built and a Scala package would be created. In the second stage, the package created from the previous stage would move to this stage to specifically run the tests. In the final stage, the packages passed the test would be deployed by the instances. + +The job is scheduled to be triggered every 24 hours on a [restricted instance](http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/restricted-publish-artifacts). + +Currently, we are supporting tests in the following systems: + +- Ubuntu 16.04 +- Ubuntu 18.04 +- Cent OS 7 + +All packages are currently built in `Ubuntu 14.04`. All Dockerfile used for publishing are available in `ci/docker/` with prefix `Dockerfile.publish`. + +Apart from that, the script used to create the environment and publish are available under `ci/docker/install`: + +- `ubuntu_publish.sh` install all required dependencies for Ubuntu 14.04 for publishing +- `ubuntu_base.sh` install minimum dependencies required to run the published packages + +## Scala publish Review comment: ```suggestion ## Scala Publishing ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
