Versions Compared

Old Version 139

changes.mady.by.user Naveen Swamy

Saved on

compared with

New Version 140

changes.mady.by.user Anton Chernov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Nightly Tests - (Currently not public, coming soon!)
    There are currently 4 different jobs that are run as a part of the nightly tests. these must pass as follows - 
    1. Go to the nightly job here - http://jenkins.mxnet-ci.amazon-ml.com/view/Nightly%20Tests/
    2. For each of the jobs, click on configure and change the branch that it runs on from the previous release to the name of the current release branch. (If you do not have access to configure jobs, please contact mabreu@amzn)
    3. Currently, we run these nightly jobs: Nightly Test for Binaries, Nightly Tests for source, Incubator MXNet, Backward Compatibility checker (currently restricted).
    4. Once each job is updated, click on the 'Release_Run-All-Nightly' and click on build now. 
    5. This job might take upto 4-5 hours to build so plan in advance (smile)
    6. After success, click on each job to make sure it ran on the correct commit #. 
    7. In case of a failure of any job, check the console logs, the newly added PRs and try and resolve issues or contact the relevant person for a fix. 
  2. Jenkins CI Tests
    1. The release branch must pass the tests on the CI for example, here - http://jenkins.mxnet-ci.amazon-ml.com/job/incubator-mxnet/job/v1.1.0/
  3. RAT Check - make sure the RAT check passes , for now run it manually as indicated here - https://github.com/apache/incubator-mxnet/tree/master/tests/nightly/apache_rat_license_check(it's already part of the verification pipeline as a stage, no special actions needed)

 

 

Step 1.7. Tag release candidate (To be done by a committer)

...