Skip to content

Latest commit

 

History

History
 
 

.jenkins

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 

Jenkins continuous integration test

Usage

Jenkins will automatically trigger a new build/test under https://ci.pytorch.org/jenkins/job/horizon-builds/job/horizon-xenial-cuda9-cudnn7-py3-build-test/ and https://ci.pytorch.org/jenkins/job/horizon-builds/job/horizon-xenial-py3-build-test/ whenever a pull request is opened or updated, and display the results on the pull request. If you need to re-run the test due to infrastructure issues or non-code-related changes, you can manually trigger a re-test by commenting on the pull request "@pytorchbot retest this please" (this should usually not be necessary).

Implementation details

After Jenkins has patched the appropriate version of the Horizon repo on a Docker image, it calls build.sh via https://github.com/pytorch/ossci-job-dsl/blob/master/src/jobs/horizon.groovy to build/install Horizon and run tests. build.sh should be self-sufficient given the repo code, and not require any internet access to build and run the tests. All the requirements should have been installed in our Docker image requirements - though that may need to be updated in the future.)

If you need to download other packages or dependencies, consider adding them to the Docker image instead, in the ../docker/jenkins/Dockerfile used by ../docker/jenkins/build.sh.