CI: Backport the CI to the 11.8.x branch #275
Description
- Strip the steps building
cuda.core; let's buildcuda.bindingsonly - By the time the test CI is ready, we test
cuda.bindings(11.8.x) built in this branch +cuda.corebuilt in the main branch (since we do not need to back portcuda.corechanges)
Activity
leofang commentedon Dec 8, 2024
I think perhaps back porting is overkill. Looking at the current CI trigger conditions:
cuda-python/.github/workflows/ci-gh.yml
Lines 7 to 11 in 0ca509e
Another thing is we'll need to use a different CTK version based on the target branch. GHA should have a way for us to detect it inside the workflow or action.
[-]Backport the CI to the `11.8.x` branch[/-][+]CI: Backport the CI to the `11.8.x` branch[/+]leofang commentedon Dec 26, 2024
I looked through the pending tasks, and it doesn't seem we need to make a 11.8.6 release (i.e. there's no bug fixes that need to be backported to v11), @vzhurba01 WDYT? If so, I suggest to deprioritize this task to P2.
leofang commentedon Dec 26, 2024
Perhaps we should backport the CUDA wheel support... #62