-
Notifications
You must be signed in to change notification settings - Fork 707
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
Add documentation about the CI system #6925
base: master
Are you sure you want to change the base?
Conversation
|
||
### Releases | ||
|
||
When a release is made on GitHub the workflow that builds wheels runs, just as |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the release process also cover the image upload in Docker or GCP AR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the other stuff that isn't related to building python wheels isn't included. The docker image is as far as I can tell just a tool for making an environment in which the tfx
wheels can be built. Is that right?
If so, I'd caution against becoming overreliant on docker images for building wheels. I've seen cases (notably other TF-adjacent packages) which can only be built inside certain docker images, which makes library development very cumbersome; pip install -e .
becomes impossible if the only way to build the project is inside a container.
Co-authored-by: William Black <125844868+smokestacklightnin@users.noreply.github.com>
Co-authored-by: William Black <125844868+smokestacklightnin@users.noreply.github.com>
This PR adds a bit of documentation to
CONTRIBUTING.md
about what the CI system does. There's a description of the events which trigger workflows, and the needs the workflows fulfill.