Shulou(Shulou.com)06/01 Report--

This article will explain in detail what is the infrastructure of the Azure-based project run by Microsoft and Jenkins. The editor thinks it is very practical, so I share it with you for reference. I hope you can get something after reading this article.

Jenkins announced that it will work with Microsoft to run its own project infrastructure based on Azure. These include, but are not limited to, Jenkins developer infrastructure, such as the company's developer wiki, problem tracking management software, databases, and static content. Migrating to Azure provides more flexibility for your workload while providing additional resources for many of Jenkins's services.

The company's current infrastructure consists of a large number of physical and virtual computers, with its core computers hosted in OSUOSL and the rest of its systems distributed in AWS, Rackspace, and physical data centers. InfoQ interviewed Jenkins community leader R. Tyler Croy about the significance of the partnership to Jenkins.

The organic growth of the project has gradually become the norm, and the infrastructure of Jenkins has grown significantly in all aspects. According to Croy, integration into a cloud platform can bring huge benefits to the company in different ways. Does such integration require a major redesign of the way the entire infrastructure service works? Croy said they were "re-evaluating the distribution / download center and infrastructure designs (such as Jenkins on Jenkins) that provide build / test services for kernel and plug-in developers," adding:

Migration can bring a lot of benefits. A large number of services can achieve larger scale by default, provide hosted / scalable database backend for various database-side services, and define the actual infrastructure topology by writing code. After all, everything can be used through API. By using off-the-shelf services (such as CDN, Azure Container Services, SQL Server), we can also omit parts of our infrastructure and reduce the operational burden we have to bear on our own.

Moving to the cloud can also better deal with unpredictable traffic. For Jenkins, the amount of traffic depends on the specific service. Services such as developer infrastructure (wikis, problem tracking management software, other services) grow in a predictable manner as the size of the community grows, but the workloads of services such as distributing networks or building / publishing infrastructure are more resilient, says Croy. The same flexibility exists in the demand for computing and network throughput. The recent release of Jenkins 2 has led to a surge in the number of distribution network requests.

Security also needs to be considered in the process of moving the load to the cloud. Jenkins reported a possible security incident last month. The reason for this event is that there are too many services running on the same component in the current infrastructure.

Croy further added to this problem: "due to the lack of project infrastructure resources, Jenkins needs to run too many services on the same server at the same time. It is helpful for us to split the different functions of our infrastructure through Azure, using a minimum number of (appropriately sized) instances, each providing a service, and we can layer multiple virtual networks, which helps isolate and prevent any potential follow-up problems. "

This is the end of the article on "what is the infrastructure of the Azure-based project run by Microsoft and Jenkins". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.