Commit dc5c4a62 authored by Paul McCarthy's avatar Paul McCarthy 🚵
Browse files

DOC: Notes on adding new CUDA version

parent f770a808
......@@ -325,9 +325,12 @@ platform names are:
- `linux-64`
- `macos-64`
- `noarch`
- `linux-64-cuda` (skips all CUDA builds)
- `linux-64-cuda-9.2`
- `linux-64-cuda-10.2`
- `linux-64-cuda-11.0`
- `linux-64-cuda-11.1`
- `linux-64-cuda-11.3`
## Configuration
......@@ -572,10 +575,28 @@ to control / customise the behaviour of the FSL CI rules.
| `CI_RULES_BRANCH` | Both | No | Install CI rules from a branch other than `master`. |
Valid values for the `FSLCONDA_SKIP_PLATFORM` variable are:
- `linux-64`
- `macos-64`
- `noarch`
- `linux-64-cuda-9.2`
- `linux-64-cuda-10.2`
- `linux-64-cuda-11.0`
## Adding support for a new CUDA version
Just follow these simple steps:
1. Create a `Dockerfile` for the new CUDA version in the `docker`
sub-directory.
2. Add a `build-docker-image-linux-64-cuda-X.Y` job to the
`rules/fsl-ci-management-rules.yml` file.
3. Add a `build-linux-64-cuda-X.Y-conda-package` job to the
`rules/fsl-ci-build-rules.yml` file.
4. Add a `deploy-linux-64-cuda-X.Y-conda-package` job to the
`rules/fsl-ci-deploy-rules.yml` file.
5. Update the `$FSLCONDA_SKIP_PLATFORM` clause in the
`.fsl-ci-conda-build-job-base` job template in the
`rules/fsl-ci-build-rules.yml` file.
6. Update the `$FSLCONDA_SKIP_PLATFORM` clause in the `.deploy-conda-package`
job template in the `rules/fsl-ci-deploy-rules.yml` file.
7. Update the `CUDA_VERSIONS` list in `fsl_ci/platform.py`.
8. Update the `cuda` list in the `fsl-release.yml` file, used to
generate FSL release manifests, in the fsl/conda/manifest> project.
9. Update the `test-environment:linux-64_cudaX.Y` and
`test-manifest:linux-64_cudaX.Y` jobs in the `manifest-gitlab-ci.yml` file,
in the fsl/conda/manifest-rules> project.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment