-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding support for linux-ppc64le in CI #487
Comments
I am unsure if we should invest more time in the CI of this repo since new development will happen in the training-operator repo. |
@terrytangyuan |
v1 has been migrated but v2 is still under discussion. |
@terrytangyuan |
kubeflow/training-operator#1479 tl;dr there is some desire to do it, but also some desire to keep the repos separate so that it's simpler for users to deploy. I think it's worth adding the CI for this repo. |
Feel free to submit PRs if you'd like to help set this up. |
@adilhusain-s, we already enabled ppc64le CI for the training operator in kubeflow/training-operator#1692, right? @terrytangyuan that will mean that if kubeflow/training-operator#1479 is fixed, it should also maintain ppc64le support, right? I think we should still submit PRs here for these reasons:
(note: please find the ppc64le umbrella issue here: kubeflow/community#781) |
Yes |
@alculquicondor @terrytangyuan |
This seems working now. Thank you! We also need to push latest tag. Would you like to send a PR as well? |
@terrytangyuan if we push the git tag 'v0.4.0', there'll be docker image released with '0.4.0' and 'latest' tags. could you specified the requirements? docker meta action |
Please ignore my comment. Apparently latest tags have different meanings in different projects. :-) |
Hi there,
I want to add support for linux-ppc64le in CI (github action) to release binaries/docker images.
the roadmap.md file mention that CICD needs to be implemented to release the docker image.
is this roadmap.md file UpToDate?
if yes, then what github action do we want to use to implement the release process?
I suggest using the goreleaser github action.
I also want to understand how we're currently releasing the docker image for mpi-operator because I couldn't find any github workflow that does this.
let's discuss this in the comments.
The text was updated successfully, but these errors were encountered: