[WIP] Start GHA workflow to publish to release channel #56
Conversation
Creates a new custom workflow that runs after conda-build finishes if it is on the `main` branch. The idea being this will copy the packages from `rapidsai-nightly` to `rapidsai`. This does not happen for other branches than `main` (so `branch-YY.MM` would be excluded and only publish to the nightly channel). This would help automate the final step to get XGBoost packages onto the `rapidsai` channel.
| # Copy over packages | ||
| VERSION=2.0.3 | ||
| conda server copy --to-owner rapidsai rapidsai-nightly/libxgboost/$VERSION | ||
| conda server copy --to-owner rapidsai rapidsai-nightly/py-xgboost/$VERSION | ||
| conda server copy --to-owner rapidsai rapidsai-nightly/r-xgboost/$VERSION | ||
| conda server copy --to-owner rapidsai rapidsai-nightly/xgboost/$VERSION |
There was a problem hiding this comment.
This is a stub that would need to be filled out more correctly to handle the copying
For example it could query conda build --output or we could use conda search to pick up the most recent packages and copy those
|
Another option related to this one we might consider is to disable uploads and switch to GHA artifact retention like we used during testing ( #3 ). Started that approach in PR ( #58 ) Then we could use this new workflow to handle whether packages are uploaded from GHA artifact retention to |
|
@raydouglass @hcho3 maybe this could be an approach to smooth out the release process hiccup identified earlier |
Creates a new custom workflow that runs after conda-build finishes if it is on the
mainbranch. The idea being this will copy the packages fromrapidsai-nightlytorapidsai. This does not happen for other branches thanmain(sobranch-YY.MMwould be excluded and only publish to the nightly channel). This would help automate the final step to get XGBoost packages onto therapidsaichannel.