-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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 contribute page about CI #9906
Conversation
a0cd355
to
c589e2c
Compare
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.
This is awesome, thanks! I think adding a few details about building TVM once you're in the docker container would be helpful (left details inline). Looking forward to this going in!
************* | ||
|
||
.. |top_of_the_Jenkinsfile| replace:: top of the ``Jenkinsfile`` | ||
.. _top_of_the_Jenkinsfile: https://github.com/apache/tvm/blob/7481a297740f073b193a3f09b3e27f056e8c7f2e/Jenkinsfile#L48-L54 |
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.
I think it would be simpler here to reproduce a snippet of the Jenkins file, rather than link to a specific git hash.
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.
I didn't want to run the risk of this being out of date with no context, if the Jenkinsfile changes at some point this way there is at least an obvious trail (i.e. the linked commit is too old) rather than a code snippet which is much harder to track down and see when/why it changed
Co-authored-by: driazati <driazati@users.noreply.github.com>
This adds some docs with a description of the TVM CI and some usage instructions to both make contributing more friendly and educate existing developers about how CI runs. Bikeshedding on content is welcome Note: The TODOs are blocked on some other PRs and will be done before landing
Thanks for the feedback everyone, feel free to send a PR or message David for further follow up work. |
* Add contribute page about CI This adds some docs with a description of the TVM CI and some usage instructions to both make contributing more friendly and educate existing developers about how CI runs. Bikeshedding on content is welcome Note: The TODOs are blocked on some other PRs and will be done before landing * docker instructions * Comments * Rebase Co-authored-by: driazati <driazati@users.noreply.github.com>
* Add contribute page about CI This adds some docs with a description of the TVM CI and some usage instructions to both make contributing more friendly and educate existing developers about how CI runs. Bikeshedding on content is welcome Note: The TODOs are blocked on some other PRs and will be done before landing * docker instructions * Comments * Rebase Co-authored-by: driazati <driazati@users.noreply.github.com>
* Add contribute page about CI This adds some docs with a description of the TVM CI and some usage instructions to both make contributing more friendly and educate existing developers about how CI runs. Bikeshedding on content is welcome Note: The TODOs are blocked on some other PRs and will be done before landing * docker instructions * Comments * Rebase Co-authored-by: driazati <driazati@users.noreply.github.com>
This adds some docs with a description of the TVM CI and some usage instructions to both make contributing more friendly and educate existing developers about how CI runs. Bikeshedding on content is welcome
cc @areusch @konturn