# \[pre-RFC\] Managed Jenkins infrastructure for TVM

**URL:** <https://discuss.tvm.apache.org/t/pre-rfc-managed-jenkins-infrastructure-for-tvm/11692>\
**Category:** RFC\
**Created:** [December 13, 2021, 11:25pm UTC](https://discuss.tvm.apache.org/t/pre-rfc-managed-jenkins-infrastructure-for-tvm/11692 "2021-12-13T23:25:09Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![driazati](https://discuss.tvm.apache.org/user_avatar/discuss.tvm.apache.org/driazati/32/3303_2.png) [@driazati](https://discuss.tvm.apache.org/u/driazati)\
**Post date:** [December 13, 2021, 11:43pm UTC](https://discuss.tvm.apache.org/t/pre-rfc-managed-jenkins-infrastructure-for-tvm/11692/3 "2021-12-13T23:43:06Z")

</div>

This will be a great improvement to opening up the CI and making it easier to maintain / scale!

> [@areusch](#):
>
> ### Launch Process
> 
> TVM CI is less heavily used over weekends, so the launch process will take place on a weekend. When the launch commences, Jenkins will be configured to stop scanning PRs and we will wait for builds to complete. Once completed, the following steps will take place:

What about a slow roll out to reduce the potential of any disruption? i.e. We could at any time spin up the new Jenkins (and maybe put it at ci-beta.tlcpack.ai) and have GitHub trigger jobs for main/PRs on both instances. If possible the new Jenkins could skip reporting status back to GitHub at first until we’re sure it has some measure of reliability. After some validation period of running both in parallel, we could disable the old one and swap the new one over to ci.tlcpack.ai.

---

_[View the full topic](https://discuss.tvm.apache.org/t/pre-rfc-managed-jenkins-infrastructure-for-tvm/11692)._
