当前位置：网站首页>How powerful is the Zadig build? Practice together

How powerful is the Zadig build? Practice together

2022-06-28 22:25:00 【InfoQ】

With Jenkins、GitLab Why build with Zadig ？ What is unique about it ？

Actually Zadig The construction is mainly under the trend of micro service architecture and cloud native technology , It was born after a large number of enterprise practices , It is an efficient cloud native build engine based on the container runtime environment .

This article does not go into details about the general construction process , Mainly aimed at Zadig Introduce and practice the differentiated functions of the architecture , Let everyone know and experience one by one through practice . It includes

Build in parallel 、 Build template 、 Multi service sharing construction 、 utilize Serverless Resource construction, etc .

Build in parallel

A workflow builds multiple services in parallel , It is more convenient to develop under the microservice architecture , The efficiency of business verification has been greatly improved

Concurrency of the same task in the same workflow

Zadig The workflow of the system can trigger the deployment and update of multiple services at the same time . Execute the workflow only once , It can trigger multiple services to be executed at the same time

structure

Deploy

test

distribution

technological process , The build and release processes of different services are independent of each other , As shown in the figure below .

Concurrency of different tasks in the same workflow

Zadig The same workflow task supports concurrent execution , Select... In the workflow

Run concurrently

, You can enable the concurrency of workflow tasks . When multiple developers trigger the workflow deployment to update different services , The generated multiple workflow tasks will be executed concurrently , The latter need not wait , Maximize collaboration efficiency .

If the triggered workflow task does not contain the deployment phase , Then even if the same service is updated using the workflow , Multiple tasks of the same workflow can also be executed concurrently .
null

Currently, multiple different tasks in the same workflow support the following concurrency rules ：

It is worth noting that Zadig The number of concurrent builds depends on the upper limit of system resources , Need administrator in

System settings

Set a reasonable... According to your own situation

Task concurrency quota

Build template

Depending on the project 、 Different technology stack features , Develop several sets of build templates , A set of templates can support hundreds of microservices , Operation and maintenance specifications are easier to implement , The operation and maintenance cost is reduced several times

Create a new build template

Sequential access

project

Template library

structure

Enter the build template management page .

Click on

+

Button -> Fill in the template name -> Fill in the template configuration and save .

Constructing environment 、 Build variables and build scripts , May refer to

Building configuration

, Code information does not need to be configured in the build template , When you create a build for a service using a build template, you can customize the configuration .

Combined with build variables
$REPONAME_<index>
It can skillfully complete the configuration of the construction template , For example, the source code and compilation configuration of the service are displayed in the A Warehouse ,Dockerfile The file in B Warehouse , The scripts in the build configuration can be organized as follows , When using templates , You can configure the corresponding code base in sequence .

#!/bin/bash
set -ex

cd $WORKSPACE/$REPONAME_0/service/
cp $WORKSPACE/$REPONAME_1/dockerfiles/$SERVICE.Dockerfile .
make build
docker build -t $IMAGE -f $SERVICE.Dockerfile .
docker push $IMAGE

Use build templates

Select... When creating a build

Use templates

-> Fill in the build name and select the build template -> Select the service and configure the code information as required and save it .

Multi service sharing construction

Multiple services in the same project can share a set of build scripts , It's not easy to make mistakes. , It is also more conducive to shared maintenance

How to configure shared builds

With

multi-service-demo

For example , The project includes 3 individual Golang service service1/service2/service3, The directory structure related to construction is described as follows ：

├── Dockerfile #  Definition  3  A service person  Dockerfile
├── Makefile #  Definition  3  Compilation of services 
├── src # 3  The source code of a service 
 ├── service1
 ├── service2
 └── service3

establish Zadig structure ,

Service selection

Select multiple services in , Configure the build environment on demand 、 Code information 、 General build scripts, etc , The system provides variables to realize the sharing of construction , The build script in this example is as follows ：

cd zadig/examples/multi-service-demo
make build-$SERVICE
docker build -t $IMAGE -f Dockerfile --build-arg service=$SERVICE .
docker push $IMAGE

How to use shared build

Specify multiple services when creating a build configuration , Or modify the build after the build is created , stay
Service selection
Select multiple services in .

You can also configure the build for the service , Select and reuse existing build configurations as needed to realize build sharing .

utilize Serverless Resource construction

Configure for build separately Serverless
Elastic resources ,
Deal with scenarios where daily builds are frequent , Spend as much as you need , Avoid waste