Software companies are establishing new data centers to enhance software performance with lower response times as well as meet security requirements for storing local user data. ByteDance also has a strong need to deploy its services to new data centers worldwide quickly and with minimal error. Unfortunately, this process can also be time-consuming and error-prone, e.g., services often have dependencies on one another, requiring a strict deployment execution order. Moreover, the high similarity between resources in the new and the old data centers enables minimal modifications and maximizes the reuse of existing infrastructure configurations while providing the ability of global resource management. Additionally, manual migration across data centers often requires multiple confirmation check-points, which can significantly slow down the process. Therefore, to accelerate the new data center bring-ups, we adopt the idea of Infrastructure as code (IaC) which is a practice to automatically configure system dependencies and to provision local and remote instances [41]. In this work, we propose ByteRollout, an automatic intent-based software resource deployment system that is able to take customized infrastructure configurations as input and actuate deployments accordingly. We also assess ByteRollout in the following events of new data centers creations driven by site reliability engineering (SRE) teams. The evaluation results demonstrate that ByteRollout significantly accelerates the data center bring-up process, saving months of human effort and reducing costs by millions of USD simultaneously. The results also highlight that the Infrastructure as Code practice can be leveraged in the context of data center setups, offering benefits such as reduced process time and minimized errors throughout the deployment.

Continuous Integration (CI) and Continuous Deployment (CD) are widely used practices in modern software engineering. Unfortunately, it is also an expensive and complicated practice - setting up a CI/CD pipeline can be time-consuming and error-prone. CI/CD pipelines at ByteDance can be set up and modified through the user interface by dragging each atom onto the screen to maximize its customizability. However, these operations increase the difficulty of reuse and version tracking. In this work, we design PIPELINEASCODE as a CI/CD workflow management system using configuration files to provide high portability and traceability. PIPELINEASCODE is seamlessly integrated with the CI/CD system at ByteDance which is named as “ByteCycle”. We also assess PIPELINEASCODE in two dimensions to determine its strengths by addressing two key questions: what types of pipelines developers prefer to manage using PIPELINEASCODE, and how pipelines evolve after the adoption of PIPELINEASCODE. The evaluation results show that pipelines managed by PIPELINEASCODE generally have a higher build frequency, fewer steps, a higher change frequency, a lower success rate and a longer build duration. After the adoption of PIPELINEASCODE, pipelines tend to have fewer steps, a higher build frequency, a longer build duration, a higher success rate and a higher change frequency. The results show that PIPELINEASCODE is capable of improving the reliability and flexibility of CI/CD pipelines and thus encourages users to build and deploy more frequently.